Table of Contents

Status Management

This section defines how UEAT handles order status communication with POS systems. UEAT does not track intermediate POS statuses such as “in preparation” or “printed.” Only the final status matters: Completed or Rejected.

Order Status Flow

When UEAT sends an order to the POS, the POS must respond with one of the following statuses:

1. Completed

Indicates the order was successfully accepted and processed by the POS.

Example Response:

{
  "status": "Completed",
  "checknumber": "123456"
}

2. Rejected

Indicates the POS cannot process the order. The response must include an error code, the posOrderId and message explaining the reason.

Example Response:

{
  "status": "Rejected",
  "checknumber": NULL
  "errors": [
    {
      "code": "TOTAL_MISMATCH",
      "message": "Total amount does not match expected value"
    }
  ]
}

Important Rules

  • Functional errors (e.g., missing item mapping, invalid discount) should result in Rejected, not silent failures.
  • UEAT does not expect intermediate statuses like “preparing” or “ready.” These remain internal to the POS.
  • Once Completed is returned, UEAT considers the order finalized.

Resend Flow for Rejected Orders

If an order is rejected:

  • UEAT supports a manual resend after correcting the issue.
  • The same orderId will be reused; POS must accept the corrected order without duplication errors.
  • POS should log both the initial rejection and the successful resend for traceability.

Best Practices

  • POS must log every status response (Completed or Rejected) for audit and certification.
  • Rejected orders should include clear error codes for troubleshooting.
  • UEAT will not send further status updates beyond the initial response.