Multiple delivery tablets: what a POS integration must handle

Reading a delivery order from a tablet and entering it again in the POS adds a task for staff. An integration can reduce that work if it transfers the right information and handles exceptions.

Start by mapping each channel. Which information is entered again? Where is the menu changed? Who contacts the guest when something is unavailable? This reveals what the connection needs to solve.

Separate order receipt from menu management

Receiving an order in the POS does not automatically mean prices and sold-out items can be controlled there. Check both the direction and scope of the connection for each delivery service.

For example, Wolt documents separate order, menu and availability functions in its developer documentation. This shows what an integration can include, not that every POS supplier has implemented those functions.

Ask for written confirmation covering your supplier, country and channels. Check what requires a separate integration partner, licence or service.

Test more than a standard order

Try an order with several options, a changed price and a sold-out product. Check names, quantities, charges, payment status and planned collection time in both the POS and kitchen.

Then follow a cancellation and refund. Decide which system controls each action. The same order should not be created twice when a connection recovers or a notification is resent.

Wolt’s order guide describes status communication through APIs and notifications. Restaurant staff still need to understand what statuses mean and who acts when something fails.

Plan a fallback procedure

Ask what happens if the POS, delivery service or network stops responding. Where does an undelivered order appear? Who monitors it, and how is it entered without duplication?

Do not remove access to the delivery service’s tools until you know which tasks still require them. A successful normal order is not a complete operational test.

Reconcile sales and payouts

A provider’s payout may differ from sales because of commissions, charges, refunds and reporting periods. Check these components separately. An order integration does not automatically guarantee correct accounting or VAT settings.

Measure order-handling time before and after implementation. Record missed options and manual corrections too. That gives you a more useful result than a general promised saving.

Vendion’s own ordering channels can work in the same system. Review current integrations and ask us to confirm which external delivery connections can be supplied for your setup. Book a demo using these test cases.