Introduction

The integration middleware connects your POS to the ordering platform.

What you implement

Operation	Direction	What it means
Receiving orders	us → you	You expose an HTTP endpoint where we post every new order as JSON.
Menu updates	you → us	You send us the store menu as JSON whenever it changes — at most 5 full updates per day, per store.
Order lifecycle	you → us	You confirm order acceptance from the POS, with a preparation time, and then its transitions.

These three are the minimum for a working integration. Without order reception you have nothing to process; without menu updates, customers order things you do not sell; without lifecycle reporting, the courier is dispatched on wrong estimates and the store’s statistics degrade.

Acceptance with a preparation time

Of the whole lifecycle, the call that matters most is acceptance with committedPreparationTime set: it decides when the courier leaves for the restaurant. See order lifecycle.

What you may implement

Operation	When you need it
Individual product and attribute changes	Prices or availability change often and you do not want to resend the whole menu.
Temporary closing	You need to close one store for a while (restocking, breakdown, holiday).
Cancelled-order notification	You want the POS to learn when an order was cancelled.

What you get

• Delivery with retry. If your endpoint does not answer, we retry under a policy you choose yourself.
• Full traceability. For every order we keep what we sent you, what you replied, how long it took and what errors occurred. You look it up yourself.
• A test store, which you allocate yourself, to verify the integration end to end before touching real stores.
• A portal where you manage brands, locations, keys and endpoints.

The menu becomes your responsibility

Once the integration is live, store content is managed exclusively through the middleware. Changes made elsewhere are overwritten by the next menu update you send.

Environment

This documentation describes the production environment. There is no separate test environment with its own data: testing happens on the real infrastructure, through a test store placed in a dedicated area, where orders are test orders and never reach real customers.

Full environment addresses are in environments and URLs.