• Integrations

Integration of the site with Prom: export and ordering

Integration with Prom is two different tasks, and they cannot be confused in the estimate: give the catalog of your own site to the site as a feed or, on the contrary, remove the catalog from the storefront and transfer it to your domain. The first — 3–7 working days, the second — 7–15. Then begins what usually breaks: matching categories, availability that does not differ between two storefronts, and orders from the seller's office arriving in the CRM without manual typing. In the showcase that we measured on 07/31/2026, the site map showed 8,358 addresses with 4,000 real products. Therefore, let's start with the analysis.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Two scenarios, not one
feed from your site to the platform or moving the directory to your own domain
Price
after a free audit
Guarantee
30
days after project sign-off
Two scenarios, not one
feed from your site to the platform or moving the directory to your own domain
Term of works
15–32
working days, depends on the scenario and volume of the catalog
Before the estimate
free analysis, 2-3 working days
The size of the shop window on the site
8,358
addresses in the site map with 4,000 products and 170 categories, 07/31/2026
The quietest failure of export
the feed returns an HTTP 200 with a body of 0 bytes — and no one will know about it
Warranty period
30
calendar days for completed work
Who it's for

Situations where this service delivers results

Scenario 1 of 5

You keep the catalog on your website, and you sell hands on the platform

The manager opens the seller's office every morning and enters new items and prices there. The feed removes this work: the catalog remains alone — on your site, the platform reads it as a file on a schedule. The price changes in one place, not in two.

We'll review your situation in a free audit
What's included

Complete list of work and what you get as a result

  • We collect the catalog feed in a format that the platform reads — the site gives the file itself, without manual feeds by the manager
  • We draw up a diagram of the correspondence of your categories to the categories of the site - the product goes in its own section, not in "Other", where no one is looking for it
  • We set a pricing rule that takes into account the commission — the price in the window is calculated from yours, and not typed by hand
  • We synchronize availability according to the schedule - the buyer does not process what has already been sold, and you do not pay for a click on a missing product
  • We create an exchange log with a list of rejected items and the reason - it is clear what to add to the card, instead of blindly searching
  • We transfer the order from the seller's office to the CRM or the site administration together with the source - the manager does not enter the data a second time
  • We connect the language versions of the catalog to the download, if you have them - on the site, each page exists separately in each language
  • We transfer the catalog from the site to our own site - if this scenario is selected during the analysis
  • We put 301-redirects and save addresses when moving where it is technically possible — so that pages known to the search engine do not fall into 404
  • We show you how to read the log and restart the hand exchange - after the transfer, you are not dependent on us for your daily work
  • Guarantee of 30 calendar days for completed works, contract, invoice, act
When this service isn't right

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

  • The contract with the platform, commissions and tariff packages are your relationship with the platform
  • Transfer of seller rating, reviews and internal site traffic
  • Work with moderation and disputes on the site side
  • Copywriting of descriptions according to the requirements of the categories
  • Advertising inside the site and bets in it
Free audit

Free analysis: site or own site

Before integrating anything, it's worth figuring out what you actually have: a storefront on the site, your own website, or both. The direction of exchange and who owns the data depends on the answer.

What we measure

  1. Which is now a showcaseThe storefront we measured on the site gave 8,358 addresses in the site map, of which 8,000 were merchandise — but these were 4,000 products, each in two language versions. Such things are visible only during inspection.
  2. Who owns the data and functionalityA site map, structured data, and part of the functionality — the platform's boxed capabilities — are on the site's showcase. This is important to understand before making the decision to move.
  3. Is the catalog ready for download?Photo, characteristics by separate fields, unique identifiers. Without it, the feed will be collected, but the site will reject some of the items.
  4. Showcase speedIn the measured case, the server's first response was 995.7 ms at 132 KB of HTML — a number that the storefront owner can hardly influence.
  5. What you will lose when you moveThe seller's rating, reviews and internal site traffic are not transferred to your own site. It should be considered before, not after.

What you get

  • Current Status Report: What is the showcase, how many items are in it, and what's yours.
  • Comparison of two scenarios: export on the site and moving to your own site.
  • Evaluation of works according to the selected scenario.
  • A 30-minute conversation where we honestly analyze the risks of moving.

Timeline: 2-3 working days

Why is it free

Because the decision "to stay on the site or build your own site" is more expensive than any integration, and it should be taken with numbers.

What's next

After analysis, we give an estimate for the selected scenario. If it is more profitable for your volume to stay on the site, we will say so.

Short form: your contact and site URL
Contract and paperwork

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

  • 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.

  • Sole proprietor & bank transfer

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

  • Rights & access — yours

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

  • Client portal instead of email chains

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

  • Sites in nine countries

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

  • Verifiable numbers

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

  • Audit first, then pricing

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

  • We say "no" when unsure

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

  • 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.

  • Sole proprietor & bank transfer

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

  • Rights & access — yours

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

  • Client portal instead of email chains

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

  • Sites in nine countries

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

  • Verifiable numbers

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

  • Audit first, then pricing

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

  • 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.

What affects the price

Why two seemingly identical tasks are priced differently

  • Direction of exchangeGiving the site catalog to the site and taking the catalog from the site to the site are two different jobs. The first is based on the fields of the feed, the second on the number of addresses. To confuse them in the estimate means to make a mistake many times over.
  • The state of the characteristicsCharacteristics by separate fields — the feed is collected almost automatically. The characteristics of a paragraph in the product description have to be divided into fields, and this is a separate line of work, and not "connect the module".
  • Number of categories for mappingThe matching scheme is done by hand: each of your categories is tied to a site category. In the tool shop we measured, 361 such units are no longer an hour of work.
  • Status of export on the side of the siteBox export in CMS is either working or lying. In the two measured stores, the feed and sitemap returned HTTP 200 with an empty body - that is, you have to start with repair, not with configuration.
  • Where do the orders go?It's cheaper just in the site admin. In CRM with statuses, source and creation of TTN, it is longer: there you need to build status directories on two sides and agree on who is the boss.
  • Language versionsThe second language doubles the amount of downloads and the number of addresses when moving. In the measured storefront, 4,000 products gave 8,358 addresses precisely because of this.
Process steps

Transparent stages with approval at every step

Total duration:5–20 days

  1. Analysis and scheme of exchange

    2-3 working days

    Let's see what you have as a showcase, which directory is real and which is duplicated by languages, and which way the exchange should go. The output is a scheme: data source, receiver, periodicity, responsible from your side.

  2. Categories and characteristics

    2-4 working days

    We link your categories to the site categories and check whether all required fields are filled. Here we decide which sections we do not display at all — it is almost never necessary to display the entire directory.

  3. Feed and price rule

    3-7 working days

    We collect the downloads to the file according to the schedule, and not for each site request. We set the price rule taking into account the commission and start the first test download on a small section.

  4. Transferring the directory to your own domain

    7-15 working days

    The stage is only for the moving scenario: we remove the catalog from the storefront, disassemble the characteristics into fields, assemble the structure on our site and build a correspondence map of addresses for redirects.

  5. Availability and ordering

    2-4 working days

    Synchronization of balances according to the schedule and transfer of orders from the seller's office to CRM or admin. We agree on whose balance is the main one and fix it in writing - otherwise the two systems will overwrite each other.

  6. Test run and transmission

    1-2 working days

    Running through: export, comparing the number of items on both sides, ordering from the site to appearing in the CRM. We show the exchange log and give access with instructions.

Did not find your case?

Describe how it works on your side — we will tell you whether “Integration with the Prom site” fits and what it means in your situation. No brief and no call: one question, one answer.

Technologies & integrations

What we build on and what it connects to

Stack

  • XML / YML feed is a format that the site reads; what is not in the fields of the feed, will not be in the window
  • Prom API — orders and statuses; request frequency limits are set by the platform, so the exchange is scheduled and not "in real time"
  • OpenCart 3 / 4 - there is a boxed download, but in two measured stores it returned an empty file
  • PHP and background tasks - the feed is collected in a file in advance: generation for each request on a large directory takes tens of seconds
  • Next.js — when the catalog lives on its own front
  • exchange log — without it, there is nothing to find the reason for the position deviation

Integrations

  • Prom
  • export the catalog in the feed
  • transfer of orders to CRM
  • KeyCRM
  • Nova Poshta
  • GA4
Feed from a single source versus manual cabinet management

How this option differs from the alternative

Manual management of the seller's officeOur approach
Source of prices and balancestwo directories maintained by different people diverge in a monthone thing: the site directory, the platform reads it as a file
Availability updatewhen the manager mentioned; weekends and holidays are visible at onceaccording to the schedule; the window between downloads is visible and manageable
Rejected itemsvisible piece by piece in the office, if noticed at alllist with the reason in the exchange log
Add a thousand itemsdays of manual dialing, and every time anewone export without human intervention
Orders and analyticstransferred by copying, the share of the channel is counted per eyefall into the CRM with the source - the share of the site is visible
Cases

Tasks and results in numbers — all metrics measured by us

retail store of heating equipment, catalog of about 3.5 thousand items

Task
Before connecting the platform, check whether the store is able to hand out its catalog by machine.
Solution
We calculated the live catalog with regular CMS search and requested a site map and a regular feed.
Result
3,565 items, first server response 524.8ms at 295.7KB HTML. Defect found: /sitemap.xml and standard feed return HTTP 200 with 0-byte body, /sitemap_index.xml — 404. The file seems to exist, there is no content, and no external service will report it. Measured on 07/31/2026.

Stanleys Ukraine

online store of professional tools, catalog of over 6,000 items

Task
Estimate the download of a large catalog before connecting the site.
Solution
We found a site map at a non-standard address with robots.txt and took full statistics with a breakdown by products and categories.
Result
25,537 records in the file against 6,857 unique addresses — 6,486 products and 361 categories: each product is unloaded an average of 3.9 times under different paths. The file itself is generated in 34.2 seconds — it is impossible to collect it for each site request, only according to the schedule into a ready-made file. Measured on 07/31/2026.

garden tool shop with parallel sales on the site

Task
Keep your own store and sell on the external site at the same time, from the same catalog.
Solution
HTTP/2 shop with HSTS, two language versions, eight payment methods and four carriers; integrations include the platform and its delivery service.
Result
8,690 unique addresses: about 8,600 cards and 81 category nodes. Defects affecting the download: 33,493 entries in the site map for the same 8,690 addresses, and the second language version declared in hreflang was not included in the map. Measured on 07/31/2026.
What we need from you

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

  1. Access to the seller's office on the site.
  2. Access to the site and admin, if your own site already exists.
  3. Decision, which scenario to implement: export on the platform or moving to our own site.
  4. The pricing rule for the site including the commission — you count, we put.
  5. List of categories that we display and those that we do not display.
  6. A person who runs the seller's office and processes orders in it.
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

How is it different from moving from the site to your site?

In the direction of data. Integration is when the catalog lives with you, the site receives a copy of it as a file and returns the order; the showcase continues to work. Relocation is when the catalog is removed from the site forever, collected on its own domain, and old addresses are closed with redirects. The second is longer, more expensive and riskier, and we run it as a separate service. At the analysis, we say which script you need now, and not which one is bigger according to the estimate.

We have OpenCart, there's a drop-off in the box - what do you do on top of that?

We check to see if it works at all, and it usually turns out that it doesn't. In two stores from our sample, the standard feed and sitemap returned an HTTP 200 with a body of 0 bytes: the third-party service sees a successful response, but the inside is empty. Next comes what is not in the box in principle: site category matching, price with commission, a log of rejected items and the return of orders back to your system.

How often is availability updated and why not in real time?

We set a schedule — from several times a day to every hour, depending on how fast your balances move. There is no real time here: the platform reads the file itself and has its own limits on the frequency of requests, which it can change without warning. Therefore, the honest answer is this: there is always a window between exports, in which one position can be bought twice. We make this window short and visible in the magazine, and not pretend that it does not exist.

Commission on the platform - what about the prices?

The price for the site is calculated by the rule, not by the manager: it takes your price from the site and applies a formula to it, taking into account commission and shipping. The rule can be made different for different categories — their marginality is rarely the same. You calculate the formula itself: we do not see your purchase prices and will not invent them. If the existing margin does not support the commission, it is visible even before connection, and it is better to find out about it there.

Mydanchyk did not accept all the goods - why does this happen?

Most often due to empty mandatory fields: there is no photo of the right size, the characteristics are in a paragraph in the description instead of separate fields, there is no unique identifier. In such cases, the feed is collected successfully, and the site quietly rejects part of the items. That is why the work includes a journal: a list of rejected items with a reason for each item. Filling out the cards after that is the job of your content manager and is counted separately.

Is it possible to keep the catalog both on the site and on the site and not disperse?

It is possible, and this is the most common working option. One condition: one data source. The catalog is maintained on your site, the site receives a feed from it, the rest goes in one direction. Two separate catalogs run by different people diverge within a month - then the buyer sees one price on the website and another in the window and calls when the manager is at his busiest.

Where do orders from the seller's office go?

In what you use every day: in KeyCRM, another CRM with an open API or simply in the site admin. The source is transferred together with the order, so at the end of the month you can see the site's share in sales — this is one of the indicators by which the fate of the storefront is then decided. We reduce the statuses to one side: the site office remains the main one, because it is there that the buyer sees his status, and it makes no sense to argue with him about CRM data.

How long does it last and what about the warranty?

15–32 working days. Breakdown 2-3 days, categories and features 2-4, feed and price rule 3-7, availability and order 2-4, test run and transfer 1-2. The move scenario adds a 7-15 day directory migration phase, which is why the upper limit is like that. The sum of the days for the stages is greater than the deadline, because part of it is running in parallel, and part is waiting for your answers. Warranty — 30 calendar days for completed works.

Give a link to the seller's office and to the site - let's start with the analysis

In 2-3 working days, we will return with a document: what you really have as a showcase, how many items are in the catalog without language duplicates, and in which direction the exchange should go. If it is more profitable for your volume to stay on the site, you will hear it in the first email.

From measured cases3,565 items, first server response 524.8ms at 295.7KB HTML

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.