Start with the exact POS edition
“We integrate with your POS” is only the beginning. Record the vendor, product edition, country, software version and any required partner subscription. A brand name alone does not prove that your restaurant can use a connector.
Map the whole menu
Ask how the connection handles modifier minimums and maximums, nested options, item taxes, time-based menus, sold-out items and location-specific prices. Try a real complex item before approving a pilot. An unavailable topping must not remain purchasable online.
Follow an order into the kitchen
A successful payment is not a kitchen acceptance. Ask which system confirms the order, how a ticket reaches the right station, and how the guest sees a rejection or delay. Require a plan for retries that does not duplicate tickets or payments.
Confirm payments and refunds
Some POS systems require their own processor. Request a written breakdown of processing, API, account and payout fees. Confirm which team can cancel an order, issue a partial refund and reconcile it in both systems.
Run a deliberate pilot
Agree on hours, order limits, staff ownership and a stop procedure. Test sold-out items, closing time, a delayed confirmation and refund reconciliation. Switch Labs Order has no live POS connections today; this is the validation checklist guiding our planned pilots.