Table of Contents

Test Environment

During the integration phase, UEAT provides POS partners with access to a dedicated test environment designed to simulate real-world scenarios and validate API interactions.

UEAT's Role

UEAT will:

  • Provide a non-prod API URL for sending test orders.
  • Supply a standardized test menu for validation.
  • Grant access to a test restaurant backoffice to monitor and manage test orders.
  • Maintain access to the POS lab during and after integration to support troubleshooting and ongoing validation.

Partner Expectations

POS partners are expected to:

  • Ensure their POS system can connect to the non-prod API at all time.
    • During the integration project
    • Once in production
  • Use the provided test menu to simulate order flows.
  • Use the mandatory status updates flow and the mandatory Error Handling.
  • Keep the POS lab accessible to UEAT for support and diagnostics.

Test Menu Structure

The test menu includes:

  • Multiple categories (e.g., Burgers, Drinks, Sides).
  • Sample items with modifiers and pricing.
  • Configurations that reflect common use cases.

Link to the Menu Template

Accessing the Test Backoffice

Partners will receive credentials to log into UEAT’s test restaurant backoffice. This interface allows:

  • Viewing incoming test orders.
  • Create test orders.
  • Monitoring order statuses.
  • Reviewing logs and payloads.

Best Practices

  • Use realistic payloads and scenarios.
  • Log all test interactions for review including prints if available.
  • Report issues with detailed examples and timestamps.

The non-prod environment is a critical part of the integration process and remains available post-launch to support continuous validation and troubleshooting.