Maple POS Order Routing Verification (Delivery)

Maple POS Order Routing Verification (Delivery)

1. 01

   Confirm the client's POS against Maple's supported list before touching the dashboard

   Toast, Square, Clover, Shift4 Dine, Lightspeed, NCR Aloha, Oracle Simphony, and SpotOn are the systems named in the Maple Pro integration set. If the client runs anything else, stop the onboarding clock and tell the account owner: orders cannot reach kitchen screens without a POS connection, so the retainer scope changes.

2. 02

   Check the plan tier on the Maple account before configuring order flow

   Order-taking into the POS and reservation management sit on Maple Pro at $220/month annual or $350/month monthly. Maple Voice at $85/month annual or $150/month monthly answers calls and handles FAQs but does not route orders, so a client sold on order-taking must be on Pro.

3. 03

   Map every menu item, modifier, size, and price in the Maple menu configuration

   Allergy notes and modifiers must exist as structured fields, not free text, or the ticket arrives at the kitchen screen incomplete. Walk the client's full menu against the Maple item list line by line and flag anything the POS treats as a nested modifier.

4. 04

   Place three live test calls into the Maple number and trace each ticket to the kitchen screen

   One plain order, one order with a modifier, one order with an allergy note. Confirm totals match the POS and that the ticket lands on the correct station. A ticket that reaches the POS but not the screen is a routing failure, not a voice failure.

5. 05

   Verify reservation writes against the client's booking source

   Maple books, modifies, and cancels reservations and connects to OpenTable where the client uses it. Create a test booking in Maple, then confirm it appears in the reservation system the host actually reads. Cancel it from the host side and confirm Maple reflects the change.

6. 06

   Test secure payment capture on a single low-value order

   Maple Pro includes secure payment over the phone. Run one transaction end to end, confirm the amount settles against the POS record, then refund it. Do not leave payment capture enabled for a client whose staff have not been briefed on the refund path.

7. 07

   Enable intelligent upselling only after the base order flow is clean

   Upsell prompts change the shape of the ticket and can mask routing faults during testing. Turn them on last, then re-run one test call and compare the ticket against the pre-upsell baseline before signing off.

8. 08

   Log the verified configuration in the client's delivery record and set the review date

   Record POS type, plan tier, menu version, test call outcomes, and who at the client confirmed the kitchen screen behaviour. This record is what the agency cites when a ticket dispute reaches the retainer review.