• Integrations

Integrating your site with Epicentr: catalog, prices, orders

An Epicentr integration is an XML file built from your catalog that Epicentr Marketplace picks up by link, plus order exchange through its API. The catalog has to speak the marketplace's language: the leaf category and the attributes are set by codes from Epicentr's reference lists. We have not yet integrated a single store with Epicentr, so this is an offer to build it for your task. We rely on the marketplace's documentation and on our work with Rozetka feeds. The first step is a free check of how many of your items already fit the marketplace's codes and limits.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
How products get onto the marketplace
XML by link or an XLSX file
after a free audit
Price
Guarantee

days after project sign-off

XML by link or an XLSX file
How products get onto the marketplace

Epicentr help center, checked 12 September 2026

once a day at 24:00 UTC; on request every 12, 4 or 1 hour
Auto-update by link
none yet — this is a development offer
Our Epicentr integrations

the case below is a store with Rozetka connected

Timeline

working days; 10–22 with orders in a CRM

Warranty

calendar days for completed work

Who it's for

Situations where this service delivers results

Scenario 1 of 4

Your catalog already goes to Rozetka or Prom, and now you need Epicentr

Epicentr will not read a Rozetka feed as is: it expects the category as a code from its own reference list, and attributes as an “attribute code, value code” pair. The existing feed becomes the data source from which we build a separate file. Rozetka is connected in stores from our cases; we have not done such work with Epicentr yet.

We'll review your situation in a free audit
Cases

Tasks and results in numbers — all metrics measured by us

an online store of an official garden equipment and spare parts dealer — related work with Rozetka

Task
Sell Husqvarna equipment and spare parts: chainsaws, lawn mowers, trimmers, accessories. The store needed a catalog with deeply nested categories, filters by power and engine type, model comparison, up-to-date stock and prices from the accounting system, payment and delivery services.
Solution
A store on OpenCart 3.x (revolution theme, HTTP/2) with a spare-parts catalog up to 4 levels deep. 8 payment methods are connected — LiqPay, Monobank instalments (3 payments), payment by IBAN, bank transfer with VAT, cash on delivery, Visa, Mastercard, PrivatBank — and 4 delivery options: Nova Poshta, Meest Express, Rozetka Delivery, pickup. Analytics: Google Tag Manager and Google Analytics (gtag), the Rozetka marketplace, a Google Reviews module. Organization, Store, Place, GeoCoordinates and WebSite/SearchAction markup; two language versions, uk/ru, with x-default; robots.txt explicitly declares the sitemap address.
Result
As of 31.07.2026 the store is live (HTTP 200, HTTPS); catalog: 55,321 product pages in the sitemap (18 sub-sitemaps of 3,000 URLs + 1,321 in the 19th) and 3,868 categories — 59,189 URLs in total; at this volume the first server response takes 840 ms and the full HTML load 997 ms; 6 JSON-LD types, including Store + Place + GeoCoordinates (local SEO) and WebSite/SearchAction (sitelinks searchbox); 8 payment methods and 4 delivery options.
What's included

Complete list of work and what you get as a result

  • Mapping of your categories to Epicentr leaf category codes, so each item lands in its own branch from the first import
  • Attribute map: your fields are converted into attribute and value codes from the marketplace's reference list
  • XML generator in Epicentr's format: name and description in Ukrainian, a Russian version if you want one, descriptions with allowed tags only, dimensions in millimetres and grams
  • A pre-submission check: a name over 150 characters, a description over 1500, an SKU over 64 (over 25 if you upload some products via XLSX), an item without a Ukrainian name — all of this goes into the report and never reaches moderation
  • SKU as the exchange key: the offer id in the file equals the SKU in the seller account, otherwise price auto-update will not find its product
  • An auto-update link for prices and availability with an interval suited to your assortment, from once a day to hourly
  • Batch updates of prices and availability via the API, if Epicentr opens this method to your account: the specification describes it, the help center does not
  • Orders pulled via the API into your website admin or your CRM: items, buyer, delivery, comments — the manager works in one window
  • Statuses flow back: confirmation, cancellation with a reason, waybill number — nothing is re-entered by hand in the Epicentr seller account
  • Exchange log: what was sent, which item the marketplace skipped and why — a failure is visible the same day
  • 30-day warranty on completed work (calendar days)
When this service isn't right

What's not included — so there are no surprises at delivery

  • Seller registration, the contract with Epicentr and the terms of cooperation
  • Card moderation and the marketplace's decisions on category or brand
  • Registering new brands in Epicentr's system
  • Writing descriptions, translation and photography to meet content requirements
  • Advertising inside the marketplace and handling reviews
Process steps

Transparent stages with approval at every step

Total duration:7–22 days

  1. Reference lists and category mapping

    2–5 working days

    We take the category tree and attribute sets from the seller account, and if the reference-list methods of the beta API are open to your account, we pull them from there automatically. We build a table: your branch — Epicentr leaf category code — the attributes required for it and their allowed values.

  2. XML generator

    2–4 working days

    Name and description in Ukrainian, category codes, parameters with attribute and value codes, dimensions, and availability as one of three values: in stock, to order, out of stock. The file is built by a background job and served at a permanent link.

  3. First upload in a small batch

    1–3 working days

    Epicentr has no test environment, only the live seller account. So first we upload a few dozen items, see what became a draft or did not pass, fix the rules — and only then upload the rest.

  4. Prices and availability

    1–3 working days

    An auto-update link in the seller account and a request for a more frequent interval via the marketplace manager; if the method is open, batch updates through the API with a check of each request's result.

  5. Orders, if needed

    3–6 working days

    New orders are pulled into your CRM or admin panel; confirmations, cancellations with a reason and waybill numbers go back. We found no event subscription method in the specification, so orders are fetched by scheduled polling.

  6. Handover

    1 working day

    Instructions for the manager, access to the exchange log, and a review of the first week of operation together with you.

Checking your catalog against Epicentr's codes and limits

Epicentr accepts products in its own codes and with its own field length limits. The review shows how many of your items already fit them, before you pay for any development.

What we measure

  • Ukrainian name and descriptionEpicentr's help center requires both fields in Ukrainian. Of the 21 public feeds of Ukrainian stores we examined on 8 September 2026, only 5 had separate Ukrainian fields. These are other stores' feeds built for Prom and Rozetka, not for Epicentr, but they give a picture of the market.
  • Field lengthName up to 150 characters, description up to 1500, SKU up to 25 characters in the XLSX template and up to 64 in XML. We count how many items exceed these limits and whether they can be shortened by a rule, without editing each one by hand.
  • Attributes as separate fieldsEpicentr expects parameters with attribute codes from its own reference list. When we measured the same 21 feeds on 5 September 2026, 15 had not a single param tag: a catalog like that has to be broken down first and only then exported.
  • SKU as the identifierWhether it is unique, whether it fits the limit — up to 25 characters in the XLSX template and up to 64 in XML — and whether it will match the SKU field in the seller account. This decides whether auto-update finds your product.
  • What is already in the seller accountIf some products have already been added by hand or imported from Prom, we look at their SKUs and statuses so the exchange doesn't create duplicates or wipe what has been filled in.
  • API accessThe token is generated by the “Company administrator” role, and the API tab, according to the specification, is opened by the category manager. The price update method also requires separate permission. We check what exactly is open to your account.

What you get

  • A report: how many items pass the required fields and length limits, how many don't, and why.
  • A draft mapping of your main categories to Epicentr leaf category codes.
  • An answer on which API methods are available to your particular account.
  • An estimate of the work by stage, split into essential and nice-to-have.

Timeline: 2–3 working days

Why is it free

Because most of the work here is data, and its scope only shows on your catalog. Besides, we have not worked with Epicentr yet, and naming a figure blindly would be dishonest.

What's next

After the review we give you a cost estimate by stage and a list of items whose data needs fixing. If it turns out that Epicentr's built-in XLSX import is enough for you, we will say so in our first email.

Short form: your contact and site URL

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points
  • 01

    Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • 02

    Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • 03

    Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • 04

    Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • 05

    Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • 06

    Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • 07

    Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • 08

    We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • 01

    Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • 02

    Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • 03

    Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • 04

    Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • 05

    Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • 06

    Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • 07

    Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • 08

    We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

Did not find your case?

Describe how it works on your side — we will tell you whether “Epicentr marketplace integration” fits and what it means in your situation. No brief and no call: one question, one answer.

What affects the price

Why two seemingly identical tasks are priced differently

  • State of the attributesParameters stored as separate fields are mapped to attribute codes with a table in a day or two. Attributes buried in the description text have to be extracted first, and that is what eats up most of the timeline.
  • Number of leaf categoriesEach of your branches maps onto an Epicentr leaf category with its own attribute set. A dozen categories is a day's work; several hundred is a separate document that will need maintaining whenever the marketplace changes its tree.
  • Catalog languageIf Ukrainian names and descriptions already exist, the generator simply takes them. If not, they have to be written or translated — that is content work, estimated separately from development.
  • OrdersLeaving order processing in the seller account removes a whole stage. Pulling orders into a CRM with statuses and waybill numbers going back means a separate API exchange, the largest part of this work.
  • Source of prices and stockIf you keep stock in 1C or BAS, the exchange with Epicentr will rely on the website, and the website on the accounting system; that second leg is estimated separately.
Technologies & integrations

What we build on and what it connects to

Stack

  • XML yml_catalog with Epicentr category and attribute codes — a separate file, not a copy of the Rozetka feed
  • Epicentr Merchant API — REST with a token in the Authorization header. The help center confirms orders only; reference lists and batch price updates exist only in the closed-beta specification and need separate permission for the account. There is no test environment.
  • OpenCart 3 / 4 — we write the file generator and order exchange as a module for your catalog; we have not tested ready-made Epicentr modules
  • WooCommerce — the same, as a separate plugin
  • PHP or Node.js — background jobs: building the file, polling for orders
  • Exchange log — a table with every request, the marketplace's response and the item's status

Integrations

  • Epicentr Marketplace — XML import by link
  • Epicentr Merchant API — orders and reference lists
  • KeyCRM or another CRM — receives the orders
  • Nova Poshta / Ukrposhta — waybill number in the order
  • 1C / BAS — source of prices and stock
  • Rozetka and Prom — related feeds
When a file and the API pay off, and when the seller account is enough

How this option differs from the alternative

New productappears in the file and goes out with the next import
Price and availabilityauto-update by link, from once a day to hourly
Attributesattribute codes are filled in from the mapping table
Ordersarrive in the CRM; status and waybill number go back automatically
Large catalogthe same amount of work for hundreds or tens of thousands of items
What we need from you

We can't start without this — best to prepare in advance

  1. Access to the Epicentr seller account, or confirmation that the contract has been signed.
  2. An API token: it is generated by the Company administrator in the company settings, API tab.
  3. Website admin access with permission to install modules, and server access for background jobs
  4. A list of the categories you put on Epicentr and those you don't.
  5. A pricing rule for the marketplace, if it differs from the website.
  6. A person who confirms orders and maintains the product cards on the marketplace.

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

We already have a Rozetka feed. Can Epicentr read it?

On the surface the files look alike: a yml_catalog root, offer, price and param tags. But Epicentr expects the category as a code from its own reference list, and attributes as an attribute code plus, for list attributes, a value code. A Rozetka feed has none of these codes, so we take the data from it and build the Epicentr file separately. For moving over from Prom, the seller account has a built-in import by YML link — but the products it brings in arrive as drafts.

Can prices and stock be updated via the API, without a file?

Epicentr's help center answers this directly: for now the API is only for order processing. At the same time, the API specification describes a batch update method for price and availability, up to 1000 items per request, and the documentation itself is marked as a closed beta for a limited number of companies. So during the review we check what is open to your particular account. If the method is closed, auto-update by link does the job — that is enough for most of the range.

How often does Epicentr pick up prices from the link?

By default once a day at 24:00 UTC. A more frequent interval — 12, 4 or 1 hour — is switched on through the marketplace manager or support. It updates the price, the old price and availability. The mechanism looks up a product by its SKU in the seller account, so it will not create an item that is not there yet — that is the import's job. That is why the offer id in the file has to match the SKU field in the account.

Do orders have to be confirmed manually in the seller account?

No, if your CRM does the confirming via the API: the specification covers status changes, the list of statuses allowed for an order, cancellation with a reason and the waybill number. The deadline stays the same — the help center allows up to 120 minutes, the marketplace rules require 30 minutes during working hours. Automation helps because the person working in the CRM sees the order immediately.

Have you integrated with Epicentr before?

No. Among marketplaces we have worked with Rozetka — that is the case below. We have not had a single project with Epicentr, so everything about the marketplace here comes from its help center and API specification, checked on 12 September 2026. Whatever works differently in a live seller account will show up in the first batch — which is why that batch is small.

What is risky about re-importing from Prom?

The help center warns plainly: if products are already in the “Draft”, “Under review” or “Content filling” statuses, a repeat import wipes their categories and attributes. It is a typical scenario: you fill in some of the cards, press import again and lose that work. Before every import we check which SKUs are already in the account and what status they are in.

What photo size and description length are required?

Here the help center contradicts itself: the article on XLSX import gives a minimum of 500×500 pixels, the article on XML gives 600×500. The same goes for descriptions: the content requirements say 1500 characters, the XML and XLSX articles say 12,160. We cut descriptions to 1500 characters so as not to argue with moderation. For photos we go by the larger value, 600×500, and measure them during the review, so you don't learn about size from moderation rejections.

How long will the integration take?

7–22 working days after the review. Category mapping takes 2–5 days, the XML generator 2–4, the first upload 1–3, prices and availability 1–3, handover 1 — 10–22 in total if orders stay in the seller account. Exchanging orders with a CRM adds another 3–6 days. These timelines are our estimate based on work with Rozetka feeds; there is no Epicentr-specific experience behind them.

Send us a link to your catalog and we will check it against Epicentr's rules

Within 2–3 working days we will tell you how many items pass the required fields and length limits, which API methods are open to your seller account, and whether Epicentr's built-in XLSX import would be enough for you with no development at all.

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.