MOP Validation and User Acceptance

Configuration Checks

• The correct location and revenue center are selected and the connection is active.
• Dine In and Pickup use the same configured Simphony order type reference.
• Dine In orders identify the customer table for delivery. Pickup orders are collected at the counter.
• Transaction references, import tags, SLU number, image slot, and condiment selections are correct.
• Menu items, category sequence, popular items, and filters show the intended content.
• Menu periods show the intended items and specific pricing at the configured days and times.
• Restaurant hours reflect when the revenue center is open for business, including overnight operation where used.
• The configured gateway, currency, and payment methods match the merchant configuration.
• Tips and alcohol limits behave as configured.
• Gift card connection and enablement changes take effect only after publication.
• Gift card verification, amount application, removal, and remaining totals behave correctly.
• Gift cards are unavailable with Apple Pay and Google Pay.
• Revenue center level Disable Alcohol takes precedence over the published Customize experience setting.
• Restaurant name and the enabled subtitle appear correctly in the ordering header.
• Info access and the individual information sections follow their display settings.
• The uploaded information banner appears after publication.
• Policy labels, text-policy pages, and external policy links open the intended content.
• Checkout displays the configured Marketing Opt-In text after publication.
• Editing or restoring Marketing Opt-In text leaves checkout fields, requirements, and consent control visibility unchanged.
• Branding, information, and legal changes are checked in the customer experience.
• Shared draft changes are saved, previewed, and published successfully.
• QR codes have the intended destination, location context, and activation state.

Validate the Customer Ordering Experience

Use the following procedure to verify the complete customer ordering experience, from menu selection through payment and order confirmation.

1. Open the published ordering site or scan an active QR code.
2. Select Dine In for delivery to the table or *Pickup for collection at the counter.
3. Browse menu categories, search for items, and use the available filters.
4. Select a menu item, configure its options and quantity, and then add it to the cart.
5. If combo meals are available, select the required combo options and add the combo to the cart.
6. Review the cart, adjust quantities or remove items as needed, and then proceed to checkout.
7. Enter the required customer information. For Dine In orders, provide the table or location identifier when prompted.
8. Select a payment method, add a tip if applicable, and then place the order.
9. Complete any additional payment authorization or authentication steps.
10. Verify the payment result, order summary, and receipt download.
11. Confirm that the order and payment details are recorded correctly in Simphony and the merchant’s payment reports.

The ordering widget includes a My Orders view that displays restaurant-specific order history stored on the customer’s device. Verify this functionality using the same device used to place the order.

My Orders does not provide a customer account or synchronize order history across multiple devices.

Test Operational Changes

Perform the following tests to verify that operational settings and changes work correctly in the customer ordering experience:

• Verify ordering availability before opening, during business hours, and after closing.
• Test each enabled payment method, including digital wallets on compatible devices.
• Test declined and interrupted payments, and verify that the appropriate messages appear to customers.
• Verify that special pricing is applied correctly when configured menu periods begin and end.
• Test Suspend and Activate, and confirm that the customer ordering experience reflects each change.
• Test alcohol availability and the per-order quantity limit separately.
• Disable alcohol ordering from the RVC Mappings page while it remains enabled in Customize Experience, and verify that the operational setting overrides the published configuration.
• Verify that saving payment and gift card settings does not affect the live ordering experience until the changes are published.
• Scan representative QR codes from each configured location range to verify that they open the correct ordering experience.
• After publishing changes, reopen the customer ordering site and verify that the updated settings are displayed correctly.

Use the test results to support customer acceptance. For each test, record the revenue center, test scenario, expected result, actual result, test date, and reviewer.

Resolve any identified issues before approving the configuration for production use.