Table of Contents

Environments

This section provides an overview of UEAT’s environments and the recommended deployment process for POS integrations.

Available Environments

1. Non-Production Environment

  • Used for initial API implementation and internal testing.
  • Includes mock data and limited functionality.
  • Access provided upon request during the Preparation Phase.
  • Mirrors production settings but isolated from live data.
  • Used for certification and partner testing.
  • Includes:
    • Standard menu for testing.
    • Test restaurant structure (Brand → Location).
    • Dedicated test ordering URL.

3. Production Environment

  • Live environment for real transactions.
  • Access granted only after successful certification and pilot testing.

Lab Availibility

A dedicated lab environment is mandatory for both UEAT and the POS Partner throughout the entire lifecycle of the integration. This requirement is defined in the Statement of Work (SOW) and remains in effect during integration, certification, pilot, and full production operation.

Partner Lab Requirement

The Partner must provide UEAT with continuous access to a functional, isolated lab environment that reflects the Partner’s real POS behavior. This lab is essential for:

  • API integration and feature validation
  • Certification and recertification
  • Debugging and troubleshooting
  • Ensuring compatibility during updates or new releases
  • Reproducing customer‑reported issues safely

The Partner’s lab must remain available and operational even after the integration is live in production, as it is required for ongoing maintenance and support.

UEAT Lab Access for Partners

UEAT also provides Partners with access to a UEAT-managed lab environment, which includes:

  • A dedicated test restaurant (Menu → Location)
  • A controlled menu configuration
  • Test ordering URLs
  • Tools for simulating customer workflows
  • Test orders and sandboxed API activity

This environment mirrors core production behavior while remaining safe for validation and troubleshooting.

Duration

The lab availability requirement is not limited to onboarding—it applies:

  • During initial integration
  • During certification
  • Throughout production and maintenance
  • During any re-certification or feature expansion
  • For the entire duration of the commercial agreement

Ensuring stable lab access on both sides is critical for platform reliability, safe testing, and seamless support.

Best Practices

  • Maintain separate API keys for each environment.
    • Use secure API (can be generate by a tool)
  • Use version control for configuration changes.
  • Log all API calls and responses for traceability.
  • Validate edge cases before moving to production.