"Does it integrate with my POS?" is the first thing owners want to know about any online ordering system, and every vendor says yes. What almost nobody asks next is what that yes actually covers. "Integration" gets stretched over everything from orders that land in your POS as line items with modifiers to a PDF that shows up in your inbox at closing time. On a comparison chart, both earn the same checkmark.
Below are five tests that tell a real POS integration from a painted-on one. Ask them before you sign. The answers decide whether your staff will be retyping orders for the next three years.
Test 1: orders inject as structured data, not tickets to retype
The heart of it: an online order should reach your POS the way a cashier would have keyed it in (items, modifiers, notes, discounts, payment status), with nobody in between. If the vendor's flow routes through a tablet where staff "confirm" each order into the POS by hand, you're paying for data entry with extra steps, not a connection. Retyping runs 1–2 minutes an order and breeds the transcription slips that later come back as refunds. With real injection, the order travels from the customer's phone to the kitchen ticket and nobody touches it on the way.
Worth probing too: what the system does when the POS goes briefly dark, say a router reboot or an update mid-shift. A solid integration holds the orders in a queue and feeds them in the second the connection returns, in sequence, with a heads-up to the manager. A brittle one loses them without a word, and you hear about it from an angry customer forty minutes later. Ask the vendor to walk you through the failure path, not just the happy one. How well they answer says a lot about how the rest of the product is built.
Test 2: the menu has one source of truth
Ask which system owns the menu. With a real integration you edit an item once (its name, price, modifiers, photo) and the change travels everywhere: the POS, the website, the app, any marketplaces you've connected. Without one, you keep parallel menus that slowly pull apart until a customer buys something at last month's price. Menu drift looks trivial until you add up the hours. Operators juggling three or more channels by hand tell us they lose several hours a week just keeping menus lined up, and none of that time comes back as revenue.
Test 3: stop-lists sync in seconds, both directions
You 86 an item on the POS, and it needs to disappear from every ordering surface before the next customer reaches checkout. The other direction counts as much: put it back in stock and it should return everywhere. When stop-list sync lags, every sold-out evening produces orders you can't fill, and each one costs a refund, an apology call, and a little trust. The gap between seconds and minutes is what separates a non-event from a nightly round of cancellations.
We'll show you exactly how orders, menus, and stop-lists move between Dots and your POS — no slides.
Test 4: statuses flow back out
Integration runs both ways. When the kitchen bumps an order, the customer's app should read "being prepared"; when it's ready, dispatch should assign a courier on its own. That return path, where POS and kitchen status feed delivery logistics and customer notifications, is what silences the "where's my order?" calls. A connection that only pushes orders in and reports nothing back leaves you running delivery blind.
Status flow also feeds the numbers you run the business on. When prep and delivery times move through a single pipeline, you can finally see where a slow Friday actually bogged down, whether in the kitchen, at the hand-off, or on the road, instead of relitigating it from memory on Saturday morning.
Test 5: the reports finally agree
The payoff of real integration that owners rarely see coming is that the numbers reconcile. When online orders skip the POS, closing out the day means stitching together the POS report, the ordering dashboard, and marketplace statements, three sources that never quite line up. Run everything through one pipeline and your sales reports put every channel in one place: revenue, item performance, and channel mix, with no spreadsheet séance at midnight. Owners tell us it's the feature they didn't realize they were buying, and the one they'd fight hardest to keep.
How Dots handles it
We built our integrations layer around these five tests, because we run the whole chain (ordering apps, website, order management, dispatch) and a weak POS link would break everything downstream of it. Orders inject with full structure. The menu lives in one place and pushes out from there. Stop-lists sync both ways, statuses flow back to the customer and to dispatch, and reporting covers every channel. That pipeline is what's carried 3M+ orders with no retyping station anywhere in sight. If your POS is one we haven't connected yet, we build the connector as part of the project, which is the sort of thing a custom platform can do and a take-it-or-leave-it SaaS list can't.
Before you sit through any demo, do one thing: stand by your counter for 20 minutes at Friday peak and count how often someone reads one screen and types it into another. Every tally mark is integration you don't have yet. Bring the number to the call.
One menu, synced stop-lists, unified reports — integrated and live in about two weeks.