Review and output an order summary
Use the order summary to review the operational and billing information that will be sent to a system print or PDF flow. Opening an output flow does not confirm that a file was saved, shared, or printed.
Before you start
- Sign in to the intended project, open Orders, and select the correct order.
- Confirm the order number and status before opening the printer icon. The output controls are not shown for a pending order and can be unavailable for some logistics or grouped orders.
- Check the app's saved printers, the printer queue, and recent paper output before selecting the printer icon. If one or more printers are saved, selecting the icon opens Ticket Preview and immediately attempts to print the ticket to every configured printer before you can review the preview.
- Treat the summary as sensitive. It can include customer and business contact details, addresses, order notes, items, prices, payment information, and totals.
- Check whether this order may already have been printed automatically or manually. Repeating an output action can create another physical copy.
What the summary includes
| Area | Information to verify | Why it matters |
|---|---|---|
| Order | Order number, current status, order type, delivery preference when present, delivery date, and payment method information. | Confirms that you opened the intended order and output context. |
| Customer details | Base name, email, and address rows, which may be empty; phone numbers, unit or internal number, address notes, and postal code only when present. | May contain personal information that should go only to an authorized destination. |
| Business details | Base business name and email rows, which may be empty; phone numbers, address, and special address notes only when present on the screen. The generated output can retain an empty business-address row. | Identifies the location responsible for the order. |
| Order details | Order comment, products, quantities, options, removed ingredients, product comments, and line prices when present. | Helps the receiving operator prepare the correct items. |
| Bill | Subtotal, applicable discounts, offers, taxes, fees, delivery charge, driver tip, payment entries, and total when present. | Lets you compare the output with the order before using it elsewhere. |
The base customer and business rows described above can remain visible or be included in generated output with an empty value. The phone, internal-number, address-note, postal-code, delivery-preference, and applicable billing rows are conditional. A missing conditional row means only that the loaded order did not provide the value for this summary; it does not confirm deletion from another system.
Choose an output action
- After completing the saved-printer and prior-output checks above, select the printer icon once.
- Follow the branch that opens:
- If Ticket Preview opens, the app attempts to print one ticket to every saved printer as the preview loads. Check every configured printer's queue and paper output. Selecting Print ticket attempts another ticket on every saved printer, so use it only when you have confirmed that another full set is intended.
- If the order summary opens, review it and select Print. In Print order, choose System printer to open the operating system's print dialog, or Save / Export PDF to generate a PDF. On iOS, the PDF branch opens the system share sheet. On Android, it opens the system print flow for that PDF.
- Complete or cancel the applicable system flow. Return to the app and verify the intended destination independently.
Verify the result
The app can confirm only that it opened or attempted the system flow. Verify the result at the destination:
- For saved-printer ticket output, check every configured printer, its queue, and its physical output. The preview can attempt output before it appears, and Print ticket can send another full set.
- For a system printer, check the selected device, job state, page count, and physical output.
- For a PDF, check that the intended authorized location or recipient contains the correct file.
- If you canceled the system dialog or share sheet, treat the action as incomplete.
Do not use the return to the Business App, a closed dialog, or the lack of an error as proof that printing or sharing finished.
Limits and variations
- Save / Export PDF has different platform behavior: iOS opens sharing, while Android opens printing for the generated PDF.
- If PDF generation does not return a usable file or another export error occurs, the app can fall back to the system print flow. Review the dialog before continuing so you do not print unintentionally.
- If the system print dialog cannot be opened, the app can show Error and Could not open the print dialog. Please try again. This reports a caught handoff error, but it does not prove that no job reached a queue. Check the queue and paper before retrying.
- Saved-printer output can show a printer-specific message or the generic Order not printed, connection failed message. A caught error does not prove that every printer produced nothing; check each queue and paper output before retrying.
- System print, PDF creation, file storage, share destinations, printer drivers, queues, and physical output are controlled by the device or provider after handoff.
- The displayed behavior is source-intended for the documented version. Installed app, operating-system, provider, and deployed service equivalence have not been verified.
Troubleshooting
| What you observe | Likely boundary | Safe next action |
|---|---|---|
| The printer icon is missing. | The order is pending, is in a logistics/group state that hides output actions, or the visible workspace differs. | Verify the exact order status and scope. Do not change the order merely to reveal output; ask the project administrator or Ordering support to confirm availability. |
| Ticket Preview opens instead of the order summary. | Saved printers are configured, and the preview attempts to print to all of them while loading. | Check every saved printer's queue and paper immediately. Do not select Print ticket unless another complete set is intended. |
| Could not open the print dialog. Please try again. appears. | The operating-system print handoff returned an error, but the app cannot prove that no job was submitted. | Check the system queue and paper first. Retry once only if no output exists; escalate a persistent error. |
| Order not printed, connection failed or another saved-printer error appears. | At least one saved-printer attempt reported a failure; another printer or partial job may still have produced output. | Check every configured printer, queue, and paper. Retry only the intended output after accounting for all copies. |
| Save / Export PDF opens a print dialog. | This is the source-intended Android branch. | Select the intended printer or an available PDF destination in the system UI; verify the result there. |
| A PDF share sheet opens but no file reaches the destination. | Opening the share sheet does not prove that sharing or saving completed. | Choose the authorized destination again and verify it independently. |
| Output may have already occurred. | Automatic, ticket-preview, or earlier manual printing can create another copy. | Check the printer queue and physical output before retrying. Avoid repeated taps. |
| The summary contains unexpected or stale information. | The summary uses the order currently loaded in details. | Go back, refresh the order, verify its number and status, then reopen the summary. Do not output uncertain data. |
Related articles
:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program with exact phone and tablet summary states, saved-printer Ticket Preview automatic and manual all-printer output, queue and paper accounting, iOS and Android order-summary output choices, PDF and print error branches, redaction, an exact asset allowlist, effect receipts, and independent visual QA. :::