---
title: "Understand preorder availability"
description: "Distinguish reachable scheduling candidates from settlement and unsupported standalone routing."
canonical: https://docs.ordering.co/docs/products/customer-app/browse/preorder/
---

# Understand preorder availability

The reachable current authority is a business-supplied MomentOption journey. The registered legacy BusinessPreorder route has no proven ordinary caller and is not a supported standalone flow.

:::warning Candidate time is not acceptance A visible slot, closed screen, changed label, or automatic navigation does not prove business, order-option, cart, or server settlement. :::

## Reachability boundary

| Surface                 | Disposition                                                                   |
| ----------------------- | ----------------------------------------------------------------------------- |
| Business MomentOption   | Reachable conditionally from current business surfaces; candidate state only  |
| Legacy BusinessPreorder | Registered source without ordinary caller; not a supported standalone journey |

## Eligibility and time authority

Scheduling depends on project/order-type gates, business/menu schedule, lead and interval rules, current open/closing state, device/business/server clocks, timezone and current cart revision. Missing or disabled schedules can still produce generic candidates; those are not business eligibility.

## Settlement and automatic effects

Selection can update order options and carts before callbacks/navigation settle. Closing-time timers can navigate automatically. A screen close or ASAP fallback is not customer intent or success.

## Unknown states

Treat missing slots, generic slots, closing-time overlap, timezone disagreement, early navigation, lost response, and multi-cart disagreement as unknown. Do not reopen, refocus, change clocks, select, or place an order to diagnose them.

## Accessibility and disposition

Slots, timezone, disabled/loading/error/unknown and automatic-navigation consequences need complete semantics, focus, 200% text and reduced-motion verification. An ordinary supported journey and exact settlement remain unproved.

**Related guides:** [Business page overview](https://docs.ordering.co/docs/products/customer-app/browse/business-page/) · [Schedule and preorder states](https://docs.ordering.co/docs/products/customer-app/cart-checkout/scheduling-preorder/) · [Review your cart](https://docs.ordering.co/docs/products/customer-app/cart-checkout/)