Delivery apps and your POS: stop typing orders from a tablet on the wall

Walk into the back of a busy Riyadh restaurant and you will often find a shelf of tablets, one per delivery platform, each buzzing. A staff member reads an order from one and types it into the POS. Then the next.

Count the cost of that: at 45 seconds per order and 80 orders a night, it is an hour of wages every night, plus the errors — and errors on delivery orders are expensive, because the customer is not there to correct them.

What integration actually does

An integrated platform sends the order directly into your point of sale. It:

• Appears as an order with the correct items and modifiers
• Prints to the right kitchen station or shows on the KDS
• Is tagged with its channel, so your reports can separate delivery from dine-in
• Carries the platform's order reference for reconciliation
• Updates status back to the platform — accepted, preparing, ready

Wameed integrates with ten:Jahez, HungerStation, Keeta, Talabat, Noon Food, Mrsool, Ninja, The Chefz, ToYou and Carriage.

What integration does not fix

Your menu still has to be right on each platform. Integration handles orders; menu publishing varies by platform and some still require their own portal.

Commission is still commission. Seethe delivery commission maths.

Platform outages are still platform outages. When a platform's own systems have a problem, integration does not help.

Preparation-time promises are still yours to keep. Integration tells the platform when you accept; it does not make the kitchen faster.

The menu sync problem

The most persistent operational headache in delivery is menus drifting apart. You change a price at the counter; six platforms still show the old one. An item sells out; it is still orderable on four apps.

Practical rules:

1. One source of truth. Your POS menu is the master. Everything else derives from it.
2. A weekly menu audit. Pick three items and check the price on every platform. Fifteen minutes.
3. Availability first, price second. An item that is unavailable and still orderable produces a cancelled order and a bad rating. That hurts more than a stale price.
4. Delivery-specific pricing is legitimate — many restaurants price delivery items higher to absorb commission — but it must be deliberate, documented and consistent, not an accident of drift.

Reconciliation: the part nobody enjoys

At the end of the month, each platform sends a statement. Your job is to confirm that what they say they owe you matches what you actually sold, minus the commission you agreed.

Without integration this is close to impossible; with it, it is a report. What you are checking:

• Order count per platform matches
• Gross value matches
• Commission matches the contracted rate
• Refunds and cancellations are accounted for
• Promotional discounts funded by the platform are attributed to the platform, not to you

The most common finding is orders that exist in the platform statement and not in your POS — usually orders taken during an outage and never entered. That is money you sold and did not record.

The VAT question

How you invoice a delivery order depends on your commercial model with each platform — whether you sell to the customer with the platform as an agent, or sell to the platform. These differ between platforms.Confirm with your accountant, per platform. SeeZATCA for restaurants.

A practical setup order

1. Get your POS menu right first — items, modifiers, prices, availability
2. Integrate one platform, and run it for a week
3. Check the reconciliation for that week before adding the next
4. Add platforms one at a time
5. Once all are live, set a weekly fifteen-minute menu audit
6. Reconcile monthly against each statement

Adding all ten in one day is how restaurants end up with three of them silently misconfigured for months.

The integration list is on theintegrations page.