How a phone order gets into your restaurant POS: menu sync, kitchen routing and payment (2026)

A phone order reaches your POS in four stages. The POS menu is copied to the phone system, the caller's choices are checked against your modifier rules, the finished order is written into the POS, and the POS sends it to printers or kitchen screens by its own routing rules. Payment happens on the call or waits for pickup. Each stage needs its own test.

This page covers the settings on the POS side. For how an AI turns a guest's words into a ticket, read how AI ordering systems work. For the drive-thru lane, read how a drive-thru AI order reaches the POS.

Which POS systems can take Maple phone orders?

Maple's integrations page lists the systems it connects to, and each has its own page with setup and test notes: Chowbus, Clover, Lightspeed, Linga, NCR Aloha, NCR Voyix, Oracle Simphony, OrderCounter, Quantic, SkyTab (now Shift4 Dine), Smile, SpotOn, Square, Stream Orders, Toast and Tray. For reservations it lists OpenTable.

Shift4 renamed SkyTab POS to Shift4 Dine on May 12, 2026, and said accounts and integrations stay the same. Phone orders into the POS come with Maple Pro, which is $350 a month billed monthly or $220 a month billed annually on the pricing page.

How does the menu get from the POS to the phone?

Maple Pro sends finished phone orders into your POS, so the phone menu has to match the POS menu. Maple's product page says menu-update timing depends on the integration, so ask during setup which menus the phone agent uses, how and when changes reach it, and where edits belong. Then check each setting below on your own POS.

POS setting	What it does to a phone order	How to check it
Which menus are shared	Only shared menus can be ordered by phone	Ask for the list of synced menus and compare it with the ones you sell
Channel visibility (Toast: Online Ordering Partners)	Items hidden from partner channels may not be offered by phone; ask how your setting is treated	Order one hidden item; it should be refused
Modifier group minimum (Toast)	A required group should make the agent ask for the choice; an optional one should not	Order the item without naming the choice
Sold-out status	Ask whether an item marked out in the POS stops being offered	Mark an item out, resync if needed, then order it
Prices by size	Each size should carry its own price on the ticket	Order each size and compare the price with the POS

Two more questions for setup: where to add alternate names and spellings so the agent can match what callers say, and which system a permanent menu change belongs in, so a later update does not undo it. For the full modifier setup, see our phone order accuracy guide and the item worksheet in the menu preparation guide.

How does the order reach the printer or kitchen screen?

Once the order is in the POS, your POS routes it by the same rules it uses for any other order. First ask which order type or dining option phone orders arrive as, because routing rules and sales reports use it. Then check the routing in your system:

• Toast: item routing rules change which prep stations get an item based on the dining option or service area. Toast's example sends takeout items to a Packer station as well as the Hot, Cold and Dessert stations. Creating rules needs the 6.2 Kitchen / Dining Room Setup permission.
• Square KDS: each kitchen display chooses its sources in Routing, Source and fulfillment: orders from chosen POS devices, or "online, kiosk and delayed fulfillment orders". A screen with the second switch off will not show orders in that group.
• Clover: items carry printer labels. With "Print separate tickets based on labels" turned on, one order prints as separate tickets for stations such as Grill, Fryer and Bar, and unlabeled items print on the combined ticket.

Our kitchen display guide and Square KDS guide cover screen setup in more depth.

How is payment handled?

Maple Pro takes card payment during the call; the pricing page lists secure payment over the phone. Ask how an unpaid order is handled: whether it waits for payment before it reaches the kitchen, and how staff mark an order paid when they took payment another way.

The payment choices can also depend on the POS, so confirm the options for your system during setup. For card data rules on the phone, see our guide to phone payments.

What should you test before live calls?

1. Order an item with a required choice without naming the choice. The caller should be asked.
2. Add, remove and swap modifiers, then check the printed ticket word for word.
3. Order every size of one item and compare each price with the POS.
4. Mark an item sold out in the POS and try to order it.
5. Order one item from a menu you did not share, or one hidden from the phone channel.
6. Place a takeout order and stand at each station that should get a ticket or screen.
7. Test each payment path: paid on the call, payment abandoned, and pay at pickup. Check what the kitchen sees for each.
8. Run your end-of-day sales report and check that test orders appear under the phone order type.
9. Change a price in the POS, resync, and order the item again.

Warn the kitchen before any test that sends a real ticket, and void the test orders afterward.

What else connects to your POS?

Phone orders share the POS with other connected systems. Each has its own guide:

Also check	What to check	Guide
Delivery apps	Menu and price match, how orders arrive in the POS, commission on each order	Delivery app fees
Your own online ordering	Fees that remain and how orders reach the kitchen	Commission-free online ordering
Card payments	Rates and who holds the card data	Card processing fees
Internet outages	What the POS keeps doing offline	POS offline mode

Published by Maple, which sells AI phone answering and ordering for restaurants. This AI-assisted guide combines Maple's integration, product and pricing pages, Toast, Square and Clover documentation and Shift4's rename notice with an original test list. It does not claim that every POS supports every feature or report any restaurant's results.