Skip to main content

Closure

The GET /pos/closures/{date} endpoint tells you whether the end-of-day closure for a given date has already happened. This is mainly used before syncing orders for accounting purposes: once a day is closed, its orders are considered final and safe to process. How this status is determined depends on whether the POS itself exposes a native concept of closure.

Native closure connectors

Some POS systems track their own end-of-day closure (a Z-ticket, a shift document, a session, etc.). For these connectors, Chift checks whether that native closure exists for the requested date and returns its status directly — no inference is applied. The rule is the same across all native connectors:
  • A date that is today or in the future always returns open.
  • Any past date returns the status of the connector’s own closure record for that day.
Each connector’s own page details the exact native object used and any connector-specific nuance. See the linked sections above.

Connectors without native closures

When a POS does not expose its own closure concept, Chift infers the status using a time-based rule instead:
  • A date that is today or in the future returns open.
  • A date more than 7 days in the past returns closed.
  • For dates in between, Chift checks orders on the following days as an indicator that the requested day is settled.
Refer to each connector’s own page for the exact implementation of this rule.