Prom

A module without a single register: three settings and five services. This is pure integration with the Prom.ua marketplace, and it stores no data of its own — everything arriving from the platform lands in the system's ordinary objects. A buyer's order becomes a sales order, the buyer becomes a contact.

The idea is simple: the shop window lives on Prom, the accounting lives with you, and four things have to travel between them. Outbound — prices and stock. Inbound — orders and statuses (and a status changed on an order is sent back to Prom).

The route: from connection to an order in the system

Prom Options (access key, stock location, price list)
        ↓
Prom: update item keys — stitching the catalogues: our item ↔ Prom's item
        ↓
   ┌── outbound ──────────┐        ┌── inbound ────────────────┐
   │ Update prices        │        │ Update orders             │
   │ Update stock         │        │ Download statuses         │
   └──────────────────────┘        └───────────────────────────┘
        ↓                                   ↓
   the window shows the truth       sales order + contact
                                     ("Prom" tab on the order)

1. Prom Options — the connection point: the token and the API address, plus the answers to "what to upload and from where": which location (or several) supplies the stock figures, which price list supplies the prices.
2. Prom: update item keys — stitching the catalogues. The service pulls the shop's item list, finds the matching card in the system by article (Prom's SKU = the item code) and writes Prom's identifier into it.
3. Prom: update prices and Prom: update stock — the outbound half: so the buyer sees the price from the books rather than something typed into the cabinet long ago.
4. Prom: update orders — the main service: it brings buyers' orders into the system with a customer, item lines and a status. From there they are handled like any other — shipment, invoice, payment.
5. Prom Creation of New Customers — the rules by which a buyer turns into a contact card when they are not in the database yet.
6. Prom: download statuses fills the Prom Statuses reference — the same vocabulary the buyer sees.

What is worth understanding

Stitching the catalogues comes first. Until the item cards carry Prom identifiers, there is nowhere to upload prices and stock: the system does not know which of your items matches which item on the window.

Prices and stock go out only with the flags on. In Items Setting "Enable synchronization with Prom.ua" must be ticked — with it cleared, the price and stock services send nothing. On top of that, each item goes out only if "Synchronization with Prom.ua" is ticked on its own card; stitching ticks it itself when it binds an item for the first time.

The direction of the exchange matters. Prices and stock are pushed to the marketplace; orders and statuses are pulled. The exception is an order's status: change it on the "Prom" tab of a sales order and the system sends it to Prom. Editing a price by hand in the Prom cabinet lasts exactly until the next run of the service.

Zero stock means "out of stock". That is why the stock update is usually scheduled more often than the rest: it protects you from orders for goods that ran out long ago.

A new buyer becomes a contact automatically. With what details is decided by the Prom Creation of New Customers setting. Left empty, it produces a database of faceless cards that are hard to reconcile with real people later.

Statuses are the marketplace's vocabulary, not yours. They are not invented here: the list is pulled from the cabinet, and the "Prom" tab of a sales order picks from exactly that list.

The module calculates nothing. It makes no postings, moves no stock and keeps no separate sales. All the economics live where the orders landed — in the sales ledger.

Where to start in a new database

1. Prom Options — the access key, the stock location, the price list; in Items Setting — "Enable synchronization with Prom.ua".
2. Prom: update item keys — stitch the catalogues.
3. Prom: download statuses — fill the statuses reference.
4. Prom Creation of New Customers — decide what the buyers' cards will look like.
5. Schedule (the "Scheduled" button in the service window) prices, stock and orders — from there the module runs itself.

Common tasks

You need	Where to go
connect a shop on Prom	Prom Options
link your items to the window	Prom: update item keys
refresh the prices on the window	Prom: update prices
take out of sale what you do not have	Prom: update stock
collect the buyers' orders	Prom: update orders
set up the cards of new buyers	Prom Creation of New Customers
refresh the list of statuses	Prom: download statuses · Prom Statuses

Everything in the module

Settings: Prom Options · Prom Creation of New Customers · Prom Statuses

Maintenances: Prom: update item keys · Prom: update prices · Prom: update orders · Prom: update stock · Prom: download statuses

Where to look next

• Sales orders — where marketplace orders arrive.
• Prices — the price list the window's prices come from.
• Rozetka — the second marketplace, built differently.
• Nova Poshta — delivering the orders to buyers.