A dependable integration defines where prices originate, how they are approved and published, and how failed updates are handled.
Start with the ESL Guide to understand the technology, or the Project Planning Guide to plan a deployment.
The business-data contract should be clear before development starts.
Choose SKU, barcode or an internal product ID as the durable pairing key.
Document normal and campaign prices, validity times, units and currencies.
Define which system creates prices and which fields the ESL platform only reads.
Delay, retries and partial failures matter as much as successful requests.
Choose event-driven, scheduled or hybrid synchronisation based on change frequency.
Processing the same update more than once must not create an incorrect result.
Separate failed products, retry safely and show an actionable result to the responsible team.
An API response alone does not prove that the shelf was updated correctly.
Test normal price, promotion, cancellation, code changes, connection loss and retries.
Compare source data, platform outcome and the physical label using one test identifier.
Define who sees an alert, performs first response and escalates before go-live.
Explore products directly or combine labels, accessories, infrastructure and services only to the extent your operation requires.
