🏪 Location View
Integration
The Integration page connects your location to third-party services — mainly delivery and courier providers that dispatch drivers for your orders, plus the Eatabit internet printer. It is a Location View feature: integrations you set up here apply to the location you are currently working on.
What is the Integration page?#
Each supported provider is shown as a card. A card can hold one or more connections ("integrations") for that provider, each tied to an ordering channel. Once a delivery provider is connected, the platform can automatically send a delivery request to that provider when an order reaches the status you choose (the Order Status Trigger).
Where to find Integration#
- View: Location View
- Menu: Store → Integration
Available providers#
In Location View the following provider cards are offered:
| Provider | Type | Connection details you enter |
|---|---|---|
| Tookan | Delivery fleet management | Team ID (Optional), Access Token, Has Pickup (on/off), Auto Assignment (on/off), Pickup Custom Field Template (Optional), Custom Field Template (Optional) |
| Shipox | Delivery fleet management | API Username, API Password |
| Stuart | Delivery fleet management | Client ID, Client Secret |
| Onro | Delivery fleet management | Client ID, Client Secret, Customer ID, Service ID, Vehicle Type ID, Base URL |
| Cab Treasure | Delivery fleet management | Client ID, Client Secret, Customer ID, Store ID |
| Uber Direct | Delivery fleet management | Customer ID (the Client ID and Client Secret are set at platform level) |
| ShipDay | Delivery fleet management | API Key |
| Eatabit | Internet order printer | SID, Token, Printer ID |
Some further providers (for example OneSignal, Twilio, iCabbi or Ably) are configured at platform level and are not offered in Location View.
Fields shared by every integration#
Channel (required)#
Which ordering channel this connection applies to: All, Web, iOS or Android. Leaving it empty shows "Channel is a required value".
Order Status Trigger (required for delivery providers)#
The order status that sends the delivery request to the provider: Pending, Accepted, Ready to pickup or On Its Way. Uber Direct additionally offers Manual. Leaving it empty shows "Order Status Trigger is a required value". The Eatabit printer connection does not ask for a trigger. All credential fields (API keys, tokens, IDs) are required unless their label says "(Optional)"; each shows a matching message such as "API Key is a required value" when left empty.
Common tasks#
Connect a provider#
- Find the provider's card and click the small + (Add) button in its top-right corner. The Add Integration window opens.
- Choose the Channel and, for delivery providers, the Order Status Trigger.
- Enter the credentials for that provider (see the table above). You get these values from your account with the provider.
- Save. On success you will see "Saved Integration Successfully" and the connection appears on the card, labelled with its channel.
Edit a connection#
Click the edit button next to the connection on its card. The Edit Integration window opens with the current values loaded.
Remove a connection#
Click the red delete button next to the connection. Confirm the question "Are you sure want to delete this integration?" with Yes! Delete, or cancel with No.
Troubleshooting#
No + button on the cards.
Your account doesn't have permission for this — ask your administrator. The same applies if the edit or delete buttons are missing.
Deliveries are not being dispatched.
Check that the Order Status Trigger matches the status your orders actually reach, and that the credentials are still valid with the provider.
A provider card shows an empty state.
That provider simply has no connections yet for this location — this is normal until you add one.