Syncing with your back office
When to connect a POS or ERP instead of uploading a catalog, and what stays the source of truth.
A one-off upload is fine for the start. If products and stock live in a back-office system, connecting it is more reliable: the price and availability quoted in a chat then always match what your cashier sees.
What stays the source of truth
The back-office system. The platform reads items, prices and stock from it and never rewrites them on its side. There is one exception — the price floor: the minimum price and allowed discount are set in the EzguSavdo panel, because a POS usually has no field for them.
What can be connected today
- Billz — the connector is built; we run the first sync with you.
- 1C — exchange over CommerceML, scoped to your configuration.
- MoySklad — the connector is assembled for your stock setup.
- Open API / YML — if the system is your own.
Choosing the frequency
The more often the exchange runs, the smaller the drift and the heavier the load on your database. Fast-moving retail usually needs frequent stock updates and rare full-catalog ones. The exact schedule is fixed during setup.
What syncing does not solve
If the back office holds technical names and empty descriptions, the catalog becomes current but not understandable to shoppers. Names and descriptions are worth fixing in the system itself — then both channels win: the AI and your website.