Product
How to Get Online and Delivery Orders Straight Into Your POS
Three tablets on the counter and a cashier re-typing every order is how items go missing and reports go wrong. The three ways to handle online orders, the questions to ask about any integration, and a rush-hour checklist.
The short answer
You need an ordering platform that is integrated with your POS, so each order lands on the till by itself, prints in the kitchen and counts in your sales and stock. Re-typing from a tablet works at low volume, but it breaks at rush hour. Before you sign anything, ask how the menu syncs, what happens when the POS has a fault, and whether the orders show up in your reports.
This post is about the workflow. For what each delivery order actually leaves you after commission, read our post "Talabat vs Your Own Online Ordering".
What goes wrong on a counter with three tablets
Every app sends its own tablet. Each one chimes differently, and none of them talks to your till. So a person has to read every order and type it in again. That is where the mistakes start.
- Missed chimes: one tablet rings under the noise, and the order sits until the driver arrives.
- Wrong items: the cashier picks the wrong size or forgets a modifier while typing fast.
- Menus out of sync: you raised a price in the shop, but the app still sells it at the old one.
- Sold-out items still orderable online, so you call the customer or cancel.
- Stock that never moves for delivery orders that were not typed in.
- Reports that miss delivery sales, so you do not know your real best sellers.
The three ways to handle online orders
| Option | What it means for the counter |
|---|---|
| 1. Re-type by hand | Cheap to start. Every order is typed twice, and every mistake is yours. Fine for a few orders a day. |
| 2. A tablet and printer per app | The kitchen gets a ticket without typing. But the till, the stock and the reports still know nothing about the order. |
| 3. A platform integrated with the POS | The order lands on the till, goes to the kitchen and counts as a sale. The menu is kept in one place. It depends on how well the link is built. |
Most shops end up mixing them. The big apps may not connect to your POS at all, so you keep their tablets and re-type, while a connected platform handles the rest.
What to ask any vendor about an integration
"Integrated" can mean anything from a full two-way link to a PDF menu upload. These questions show the difference in ten minutes.
- Menu: does it sync one way or both ways? If I change a price on the POS, when does it change online?
- Branches: can each branch have its own price, and can a branch hide items it never sells?
- Promotions: do my discounts go online? Can I choose which ones, so a staff discount never becomes a public code?
- Faults: if the POS is offline, closed or has an error, is a paid order lost, retried or held?
- Status: when the kitchen marks an order ready, does the customer see it?
- Kitchen: does the order print by itself and reach the kitchen screen, with no one pressing send?
- Numbers: does the order count in my sales reports and deduct stock, like a counter sale?
- Money: is a paid online order kept apart from my cash drawer, so the cash count still adds up?
The question vendors dodge
Ask what happens to an order the customer already paid for when your POS cannot take it. If the answer is "it fails", someone on your team will be chasing refunds.
How it works with Outale
Outale is connected to one ordering platform: Tafadal (tafadal.co). Talabat, Snoonu and Keeta are not connected. Their orders are entered on the till by hand. Outale does not run an ordering website of its own and does not take online payments.
- Menu, one way: Tafadal pulls your menu from Outale. You edit it in Outale, not in two places.
- Branch prices: a branch that charges a different price sends its own price.
- Items a branch never sells: switch the item off at that branch and it is refused online there.
- Promotions: off by default. You switch each discount on for Tafadal and give it a code. Discounts limited to some items or with a minimum spend cannot be sent.
- On the till: new orders join an online-orders queue with a chime, marked PAID or COLLECT.
- Kitchen: orders print automatically when a kitchen printer is set up, and appear on the kitchen screen.
- Status, both ways: when the kitchen accepts or bumps an order, Tafadal is told (once your café's web address is saved on the connection, part of setup). When Tafadal's board moves it, the kitchen screen moves too.
- Reports and stock: a paid order is recorded as a sale, deducts stock and shows on its own line in the Delivery Partner Summary, kept out of expected cash.
When things go wrong: a paid order that arrives with no shift open is held and recorded the moment the next shift opens. If the system has a fault, Tafadal is told to retry, and a retry never charges twice. If a held paid order is still refused, it is listed on the dashboard with Retry and Mark handled, so someone acts on it.
One gap to know
"Sold out today" on the QR menu does not reach Tafadal. To stop an item being ordered online, switch it off at the branch, and remember to switch it back on.
A rush-hour checklist
- Before service, open the shift, so online orders land as sales straight away.
- Check the online-orders chime is not muted, and turn the tablets up.
- Print a test ticket on the kitchen printer.
- Switch off anything you have run out of, on every channel, not only one.
- Give one person the job of tablet orders that are not connected, so nothing is typed twice or skipped.
- Read PAID or COLLECT before handing a bag over.
- Bump orders on the kitchen screen as they leave, so the customer sees ready.
- After close, check the delivery sales against each app's own report.
Start with your busiest app
Count last week's orders per app. If one channel can be connected and the others cannot, the connected one should carry the most volume you can move to it.
Terms used here
- KDS (Kitchen Display System)A KDS is a screen in the kitchen that replaces printed tickets. Orders appear live as they are taken, staff mark them done as they go out, and nothing depends on paper that can be lost, smudged or stuck to a rail out of order.
- KOT (Kitchen Order Ticket)A KOT is the ticket that tells the kitchen what to cook. When an order is taken, the POS prints or displays a Kitchen Order Ticket listing the items, quantities and any special instructions, so the kitchen works from the order rather than from memory or a shouted request.
- Offline modeOffline mode lets a POS keep taking orders and printing receipts when the internet is down, storing everything on the device and syncing it to the cloud once the connection returns.
Related guides
- How Much Does a POS System Cost in Qatar? (2026)The real cost of a POS system in Qatar, broken into parts: the monthly subscription, terminals and branches, add-ons, hardware, card fees, setup and the hidden costs. With a worked year-one total for a café and the questions that get you a real quote.
- How to Switch POS Systems Without Losing Data or a Day of SalesA practical plan for moving from one POS to another: what to export before you cancel, what moves across and what doesn't, which day to switch, and how to run both systems for a week so nothing is lost.
More posts
- Outale vs Loyverse: Which POS Fits a Café, Restaurant or Shop in Qatar?Loyverse gives you a free POS with a kitchen screen, loyalty and multi-store. Outale is paid and goes deeper on cost, cash and branches. Where each one is stronger, where Outale is weaker, who should stay on Loyverse, and how to switch.
- Outale vs Foodics: Which POS Fits a Café or Restaurant in Qatar?A fair comparison, written by Outale: where Foodics is stronger, where Outale may suit you better, what each costs, and who should pick which.
Want this handled for you?
Outale runs the till and the back office in one system built for Qatar: stock, recipe costs, purchasing, shifts, cash and reports, across every branch, and it keeps selling when the internet doesn't.