Understand offer states and handoffs
The source-defined Offers surface can present returned promotions for a session and ordering context. Offer visibility is informational. It does not prove cart eligibility, application, pricing, payment compatibility, or order settlement.
:::warning Important limits List, local search, detail, business handoff, cart validation, and final offer application are separate states. A changed screen or previously shown card is not an authoritative offer receipt. :::
Offer-list states
| State | Safe interpretation |
|---|---|
| Unavailable entry | No current Offers destination is established for the visible session state. |
| Loading | Offer read remains pending; placeholders are presentation only. |
| Returned list | Cards are shown for one source generation; current eligibility remains separate. |
| Empty | No cards are displayed for the returned state. |
| Error | Current read did not produce an accepted list state. |
| Retained prior cards | Their freshness and authority are unknown. |
| Context changed | Prior offers can be stale after location, order-context, account, or project change. |
Card and local-search states
An offer card can present a name, displayed expiration, optional image, and a View control. Local search can narrow already-loaded offer names. It is not a service-wide search and does not validate descriptions, business names, coupon data, or cart applicability.
Search text, filtered rows, and the loaded list can diverge after errors or context changes. Keep the list stale or unknown rather than repeating reads.
Detail states
Offer Details can present optional returned terms such as a displayed value, description, target, minimum, maximum, automatic-offer notice, coupon-type information, or associated businesses. Missing optional fields do not create a separate eligibility conclusion.
Opening View is a local detail handoff. It does not apply, reserve, validate, or consume an offer.
Business handoff
When a returned business row is present, Go to business can start a business page handoff. The handoff does not prove that the destination loaded, the offer is current for that business, or the cart can use it.
Cart coupon and automatic-offer settlement belong to the cart owner. The Offers surface does not own a purchase, coupon, or application procedure.
Failed, stale, and unknown reads
Initial error can replace cards. A later read can also fail while prior local state exists. Without current runtime proof, do not claim a specific coexistence layout or that old information was refreshed.
If a read fails, keep the result stale or unknown. Do not repeat refresh or request actions to diagnose it. Use only an already-present verified in-app return control when one exists.
Privacy and accessibility
Offer names, coupon-type information, displayed terms, businesses, images, location/order context, account/session, and search text can reveal private or commercial context. Support reports must use value-free states such as “offer list stale,” “detail unavailable,” or “business handoff unresolved.”
Cards, optional images, search, detail modal, close control, business rows, loading/empty/error/stale states, focus containment/return, large text, screen-reader semantics, keyboard, and platform Back require independent current-platform verification.
Safe troubleshooting
- If the Offers entry is absent, do not infer session or configuration cause.
- If search has no matches, distinguish local filtered state from the full returned list.
- If optional detail fields are absent, do not infer universal eligibility.
- If the business handoff does not settle, keep it unresolved and do not infer offer application.
- If a read fails, preserve stale/unknown state without repeated refresh or reporting location, project, timing, order type, business, account, or offer values.
Recertification triggers
Recheck this reference when Offers reachability, list reads, local search, detail fields, business handoff, context-change behavior, stale/error rendering, remote media, cart eligibility ownership, or shared accessibility primitives change.
Related guides: Choose a location · Choose an order type and time · Understand business discovery states · Open a business page · Understand coupon states