Review Ticket Preview without repeating output
Ticket Preview builds a ticket from the current order and can immediately start physical output to every saved printer. It is not a review-before-print screen: the first output attempt can begin before you can inspect the rendered ticket, and Print ticket repeats the output loop.
Before you start
- Confirm the intended order in Orders before selecting any printer action. Ticket content can include private customer, business, item, payment, amount, address, contact, and order-comment information.
- Do not open Ticket Preview merely to inspect a ticket. Opening it with saved printer settings can begin output automatically.
- Account for every saved printer before entry. Check each approved queue and paper output for a pending or completed copy, and record a clear before-state. If you cannot observe every saved printer, stop. Do not select the printer action or enter Ticket Preview. Review the order in the current order view or use an independently established non-output workflow.
- If automatic printing is enabled before a pending order is accepted, do not accept the order until automatic printing is safely disabled under the saved printer procedure and every prior queue and paper state is accounted for.
- The order view loads its saved-printer settings once. If printer settings changed after you opened the order, return to Orders, reopen the intended order, and repeat the before-state accounting before any printer action.
- If automatic printing is enabled, accepting an order can open Ticket Preview and start the same all-printer handoff. Do not perform a separate manual entry for that order.
- Do not use a real order, customer, printer, queue, or ticket as a test fixture. Discovery, connection tests, permission prompts, provider calls, and physical-output tests require a separately authorized synthetic workflow.
Complete the task
- In Orders, verify the order number, business, status, and fulfillment context. The printer action is available only in applicable non-pending order views, and it opens Order summary instead when no saved printer settings are loaded.
- Reconcile the before-state for every saved printer. If any queue or paper state is unknown, do not open Ticket Preview.
- Preview the consequence before acting: selecting the printer action once, or completing an eligible acceptance while automatic printing is enabled, can open Ticket Preview, generate ticket commands, and send one output attempt sequentially to every saved entry.
- If the operational output is authorized and every before-state is known, enter Ticket Preview once. Do not leave and reopen it to refresh the display; reopening can start another automatic output loop.
- Wait for all saved-printer queues and paper states to settle. The Print ticket button can appear before the automatic loop has finished, so do not select it during this verification.
- After queue and paper accounting, review the displayed ticket against the intended order. The source-generated content can include order type and status, payment method, delivery timing or preference, customer and business details, products and comments, discounts, taxes, fees, tips, totals, and recorded payment information when those fields exist.
Verify the result
Verify each layer separately:
- Ticket Preview and its image confirm that the app generated display content from the order snapshot. They do not confirm provider handoff or paper output.
- Print ticket becoming available confirms only that preview loading ended. The automatic all-printer loop can still be running.
- A success message is requested only for the last saved printer. It does not prove that earlier printers succeeded or that paper emerged.
- A failure message can occur after an earlier printer already completed. A missing message can also leave the result unknown.
- Only the reconciled before/after state of every approved printer queue and its paper output establishes the operational result. Record each saved entry as completed, failed, pending, duplicated, or unknown.
If any entry is pending or unknown, the overall result is unknown. Do not use Print ticket, reopen Ticket Preview, or repeat the order action.
Recover safely
| What you observe | What it means | Safe next action |
|---|---|---|
| Print ticket appears while a queue is still active | Preview loading ended before the automatic output loop settled | Do not select the button. Continue observing every saved-printer queue and paper state |
| One or more saved printers cannot be observed before entry | The all-saved-printer effect cannot be accounted safely | Do not select the printer action or enter Ticket Preview. If auto-print is enabled, do not accept; safely disable it and account prior queue/paper state before continuing normal order work |
| A success message appears | The last saved printer's provider call reported success in the source path | Check every queue and paper result; do not infer that earlier printers or physical output succeeded |
| A failure, permission, timeout, no-paper, open-cover, offline, unreachable, or connection message appears | That provider attempt reported an error, but earlier entries can already have completed | Stop all repeat actions. Reconcile every queue and paper state before an approved operator corrects paper, cover, power, permission, or connection without submitting another job |
| No message appears | Permission handling, an earlier-only result, provider behavior, or an unsettled loop can be silent | Treat every output as unknown. Do not reopen or select Print ticket; escalate with per-printer queue and paper observations |
| Some printers completed and others did not | The sequential all-saved-printer loop produced a partial result | Preserve the completed copies and queue evidence. Do not repeat the all-printer loop; ask the printer-operations owner to plan a targeted recovery outside this procedure |
| A ticket is partial, duplicated, or belongs to an unexpected order | Provider, queue, repeated entry, manual repeat, or stale order context can settle separately | Stop output, protect the ticket as private data, disable automatic printing if safe, and escalate the order plus per-printer accounting without exposing customer details |
| A recently changed printer is missing or an earlier printer is targeted | The order view can retain the saved-printer snapshot loaded when it mounted | Do not reopen Ticket Preview or repeat output. Return to Orders only after accounting, reopen the intended order, and escalate any already-started job |
| Ticket content looks wrong after output may have started | Display generation and physical handoff use the same order snapshot, but output can precede review | Do not print again. Return to Orders only after queue accounting, verify the current order, and escalate the mismatch |
| Paper or a queue changes after you leave | A provider job can settle after the visible screen changes | Do not reopen Ticket Preview. Continue accounting until every saved entry is completed, failed, or escalated |
Availability and platform differences
Ticket Preview is registered in the authenticated workspace. A manual printer action routes there only when saved printer settings are loaded; otherwise it routes to Order summary. An eligible accepted-status result can also route there when automatic printing and saved settings are both active.
The output loop uses each saved entry's Star Micronics or Epson driver, connection type, target, print mode, and paper width. The reviewed source uses 80 mm as the fallback width and also supports a 58 mm layout. Epson USB output is Android-only. Bluetooth permissions, LAN/Wi-Fi reachability, USB support, provider behavior, queues, and paper state vary by platform, device, printer, and installed build.
This guide does not guarantee current deployment equivalence, content completeness, connection, provider acceptance, queue delivery, paper output, cross-platform parity, or exactly-once printing.
Related articles
:::note Visual status authorized synthetic capture program with accepted exact asset allowlist and independent visual QA :::