CRM for Prom.ua
X10 CRM pulls orders from your Prom.ua cabinet every five minutes, writes the status and waybill number back, and keeps your listing stock and prices current.
A new order becomes a lead with items, delivery details and buyer contacts.
Operators work only in the CRM — the Prom cabinet learns about changes automatically.
Listings are pulled into CRM products; stock and prices are pushed back.
Several companies or stores run in one CRM without mixing their leads.
Prom.ua brings traffic and orders but no process: the cabinet knows nothing about calls, stock or operators. X10 CRM pulls the orders in, builds a real funnel around them, and sends back exactly what the platform needs — the status and the waybill number.
#Orders become leads
The CRM polls the Prom cabinet every five minutes. Each new order turns into a lead with the buyer, cart items, total and chosen delivery method — next to leads from landing pages, calls and other marketplaces.
- Order items land in the lead's cart with quantities and prices, so the total matches the cabinet.
- The delivery method is recognised and prefilled into the waybill form — Nova Poshta, Ukrposhta or Meest.
- A waybill number created in the cabinet is picked up into the lead and tracked from there.
- One order is one lead, permanently. A repeated import never overwrites what an operator has already done.
#What goes back to the cabinet
- 01
The operator changes the lead status
Confirming the order after a call, moving it to rejected, or closing it as a sale.
- 02
The CRM writes the status to Prom
The mapping between CRM and cabinet statuses is configured once, to fit your process.
- 03
A waybill is created — the number follows
The tracking number reaches the platform order right after it is created on the lead card.
The write-back runs on a background queue once the change is safely saved, so a slow platform response never freezes the operator's screen.
#Catalogue, stock and prices
Once an hour the CRM reconciles the catalogue: Prom listings are pulled into your product directory and linked to order items. Stock and prices travel the other way — inventory lives in the CRM and the platform receives current numbers without file uploads.
| Direction | What is synced | Frequency |
|---|---|---|
| Prom → CRM | Orders, items, delivery, buyer | every 5 minutes |
| Prom → CRM | Product listings and links to your catalogue | hourly |
| Prom → CRM | Product images | separate queue, in batches |
| CRM → Prom | Order status, waybill number | immediately after the change |
| CRM → Prom | Stock and prices | hourly |
#What you need to connect it
- An API token from your Prom.ua cabinet
- SKUs filled in on your products, if you want stock and price sync
- A status mapping between the CRM and the cabinet that matches your process
- A connected carrier, if waybills are created from the CRM
What to configure on the CRM side: statuses, groups and transitions for your process, the cart, products and prepayments for stock and reservations, and the lead card — what an operator works in every day.
#Alongside your other order sources
Marketplaces in X10 CRM share one contract, so Rozetka and Horoshop can run next to Prom in a single dashboard. Leads from your own landing pages arrive through the API. The whole picture is on the CRM for an online store page.
Frequently asked questions
- How quickly does a Prom.ua order reach the CRM?
- Within five minutes. Prom sends no webhooks, so the CRM polls the cabinet on a schedule — operators see an order almost as soon as it is placed.
- Is the order status written back to Prom?
- Yes. When an operator changes the lead status in the CRM, the matching status is written to the cabinet. The waybill number is sent the same way right after the shipment is created.
- Are stock levels and prices synchronised?
- Yes, hourly. Products need their SKU filled in: Prom accepts stock updates by the identifier from your own accounting system.
- Can I connect several Prom cabinets?
- Yes. Each cabinet has its own token and status mapping, and its leads carry the source logo in the dashboard.
- Will a duplicate lead appear if an order is imported twice?
- No. One platform order is permanently bound to one lead — a repeated import only refreshes the internal mirror and never touches the operator's work.