Order acceptance is currently blocked
:::danger Do not use this draft to accept orders No supported order-acceptance procedure can be documented for the current source pin. The single-order and grouped-order paths apply acceptance and preparation time differently, and the time shown on screen can differ from the value submitted in a boundary case. :::
This article is a safety boundary, not an operational procedure. Do not select Accept, Accept all, or submit Preparation time based on this draft. Doing so can change remote order state, contact customers, start fulfillment work, or lead to configured printer output without one reliable end-to-end result.
Before you start
- Do not perform an acceptance action from this article.
- Use only the visible order number and status needed for approved escalation.
- Wait for a later corrected and independently attested version before an acceptance procedure is used.
Current boundary
- In order details, selecting Accept can change the order from Pending before the Preparation time screen opens. The time is submitted in a separate request afterward. Acceptance can therefore succeed while the time update fails or remains unverified.
- In a displayed order group, Accept all opens Preparation time and submits the time for every supplied order, but the pinned group path does not prove that those orders were changed from Pending to accepted.
- A grouped result can close the screen after receiving one result slot per order even when individual results failed.
- The time field initially shows 00:00 and has no predefined choices. At the exact 60-minute boundary, the display can normalize the minutes to 59 while the submitted value still represents 60 minutes.
- A returned single-order result can continue into saved-printer output when automatic printing is configured. Neither queue acceptance nor physical output is verified here.
These differences mean that button presses, screen closure, displayed time, customer communications, realtime updates, or printer activity cannot be used as proof of one safe acceptance outcome.
What to do safely
- Do not use this draft to accept or batch-accept an order.
- Refresh Orders and record only the visible order number and current status needed for escalation. Do not copy customer or payment information into an unapproved channel.
- Contact your project administrator or Ordering support through your approved support process. Explain whether the issue is a single order or a displayed group and whether any prior attempt or printer output may already have occurred.
- Do not retry an acceptance, preparation-time update, or print action while the remote or device result is unknown.
- Follow only a later corrected and independently attested version of this article after the blocked notice has been removed.
If an earlier attempt already occurred
| What you observe | Safe response |
|---|---|
| The order left Pending, but preparation time is missing or unexpected | Stop. Refresh once, preserve the visible status and time, and escalate; do not repeat acceptance from this draft. |
| A grouped screen closed | Refresh every displayed group member separately. Treat each status and time as independent, and escalate any mismatch. |
| An order remains Pending after Accept all | Do not infer that the time update accepted the order, and do not retry from this draft. Escalate the still-pending order. |
| The displayed minutes changed from 60 to 59 | Treat the submitted value as uncertain. Do not submit or correct it from this draft; escalate with the displayed values. |
| An error or stale result appears | Keep the visible message, refresh once, and stop. Do not force a status change or repeat the request. |
| A ticket may have printed | Check every configured queue and physical printer without starting another job. Report possible prior output during escalation. |
Availability and re-entry
This block applies to phone, tablet, single-order, grouped-order, automatic- printing, and manual-retry variants at the current documented pin. Source does not prove deployed App/API equivalence or printer/provider behavior.
A supported procedure requires a corrected pinned flow and independent evidence for the exact order transition, preparation-time value, single and grouped results, partial/error handling, customer and fulfillment effects, and printer accounting. Until that evidence is accepted and this article is republished without the blocked notice, use the administrator/support escalation above.
Related articles
- Review an order without changing it
- Interpret order groups and statuses
- Recognize loading, connection, and error states
:::note Visual status Visual guidance is deferred. No capture can remove this content block without a corrected and independently attested acceptance contract, exact synthetic scenarios, effect receipts, an exact asset allowlist, and independent visual QA. :::