--- title: "Review and print an order ticket" description: "Understand Ticket Preview, system print and PDF choices, and the separate checks required for a print request, queue, physical ticket, and order outcome." canonical: https://docs.ordering.co/docs/products/business-app/printing/preview-print-ticket/ --- # Review and print an order ticket **Ticket Preview** can display an order as a ticket. When saved printer settings are loaded, opening it can also start an output attempt before the ticket is fully visible. **Print ticket** can repeat the output loop. A preview, enabled button, provider message, or completed screen is not proof that every intended printer produced paper. > **Protect order and customer information** > > Ticket screens can include customer, business, address, payment, item, and order-comment information. Treat the captures in this guide as interface orientation only. Do not copy, share, or use displayed values as live order or customer data. ## Separate the results you need to verify | Result | What to check | What it does not prove | | ------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------- | | Ticket display | The ticket shows the intended order context and content. | That a printer provider received a request or a ticket emerged. | | Print request | The Business App attempted its configured ticket flow. | That every saved printer, queue, or physical printer completed. | | Provider or spooler | The relevant provider or local queue shows a settled job state. | That paper, cover, power, formatting, or the final ticket is correct. | | Physical ticket | Each intended printer produced the expected copy. | That the order, another printer, or a later repeat had the same result. | | Order effect | The intended order retains the expected status and fulfillment context. | That a printing attempt succeeded or failed. | If any saved printer, queue, paper state, or order effect is unknown, stop before repeating the output action. ## Before you start - Open **Orders** and verify the order number, business, status, and fulfillment context. The ticket can expose private customer and business information. - Check whether the order could already have been printed automatically or manually. A new action can create another physical copy. - Account for every saved printer before entering **Ticket Preview**. Check each approved queue and paper output for an earlier or pending copy, and record a clear before-state. - If any saved printer cannot be observed, do not select the printer action or enter **Ticket Preview**. Review the order in its current view or use an independently established non-output workflow. - If **Auto print after accepting order** is enabled, an eligible acceptance can open **Ticket Preview** and start the same all-printer handoff. Do not make a separate manual entry for that order. - The order view loads saved-printer settings once. If configuration changed after the order opened, return to **Orders**, reopen the intended order, and repeat the before-state accounting. - Do not use a real order, customer, printer, queue, or ticket as a test fixture. Discovery, permission prompts, provider calls, and physical-output tests require a separately authorized synthetic workflow. ## Open the ticket once 1. In an applicable non-pending order view, identify the printer action near the top of the order. If no saved printer settings are loaded, the app can open **Order summary** instead of **Ticket Preview**. 2. Reconcile the before-state for every saved printer. If a queue or paper state is unknown, stop here. 3. Select the printer action once. This is the print-request boundary; with saved settings, it can generate ticket commands and start one output attempt sequentially for every saved entry. 4. When **Ticket Preview** opens, do not leave and reopen it to refresh the display. Reopening can start another automatic output loop. 5. Wait for all known queue and paper states to settle before selecting another control. [![Order ticket view with a Print action at the bottom](https://docs.ordering.co/img/help-center-import/274184acd6245a9303ef835a.png)](https://docs.ordering.co/img/help-center-import/274184acd6245a9303ef835a.png) The ticket display lets you review the order in a print-oriented format. It 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. ## Use screen choices carefully Some app versions show controls for a printer, number of copies, and paper size. A visible control only describes the current interface branch; it does not establish which printer will receive a job or how many physical copies will emerge. [![Ticket screen with Select printer, Copies, and Paper Size controls](https://docs.ordering.co/img/help-center-import/377d551bb88d475cdf3ff931.png)](https://docs.ordering.co/img/help-center-import/377d551bb88d475cdf3ff931.png) Before changing a copy count, paper size, or target selection, confirm the intended output scope and account for every existing queue and paper state. Do not use those controls to probe hardware availability. ## Recognize PDF and all-printers branches If **Select printer** offers **Save as PDF** or **All printers**, treat those as different destination types: - **Save as PDF** begins a file or system-export handoff. Verify the resulting file at its authorized destination; it does not prove a physical print. - **All printers** can start a request for multiple saved printers. A result message for one provider does not prove that the other printers or paper output succeeded. [![Ticket screen with Save as PDF and All printers choices](https://docs.ordering.co/img/help-center-import/592b61430cf0b5c91b3c92c0.png)](https://docs.ordering.co/img/help-center-import/592b61430cf0b5c91b3c92c0.png) Screen availability varies by installed build, platform, and configured printers. Do not infer a current option or outcome from an older-looking interface alone. ## If the device asks you to add a printer A device can open a system or provider screen that lists printer services and offers **Add printer**. That is a hardware, operating-system, or provider setup boundary, not proof that the current order will print. [![System printer-services screen offering an Add printer action](https://docs.ordering.co/img/help-center-import/1f95674fa203acad7256e0b5.png)](https://docs.ordering.co/img/help-center-import/1f95674fa203acad7256e0b5.png) Do not create or discover a new printer while an order output is uncertain. First account for the current queues and paper; then use [Configure a saved printer](https://docs.ordering.co/docs/products/business-app/printing/configure-printer/) or the approved provider setup procedure. ## Verify the result Verify each layer separately: - **Ticket Preview** and its image confirm only that the app generated display content from the loaded order snapshot. - **Print ticket** becoming available confirms only that preview loading ended. An automatic all-printer loop can still be running. - A success message can represent only the last saved printer's provider call. It does not prove that earlier printers succeeded or that paper emerged. - A failure message can arrive after an earlier printer 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 physical result. Record each saved entry as completed, failed, pending, duplicated, or unknown. - Verify the order separately after the print activity. A ticket result does not establish the order's remote status, customer communication, or fulfillment outcome. If any entry is pending or unknown, the overall print result is unknown. Do not select **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 for safely. | Do not select the printer action or enter Ticket Preview. If auto-print is enabled, do not accept; safely disable it and account for prior queues and paper before continuing normal order work. | | A success message appears. | A provider call reported success for one visible 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 repeat actions. Reconcile every queue and paper state before an approved operator corrects paper, cover, power, permission, or connection. | | 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; plan 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, 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 loaded 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 available in the authenticated workspace. A manual printer action routes there only when saved printer settings are loaded; otherwise it can route to **Order summary**. An eligible acceptance can also route there when automatic printing and saved settings are both active. The output loop uses each saved entry's driver, connection type, target, print mode, and paper width. The reviewed path 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, connection, provider acceptance, queue delivery, paper output, cross-platform parity, or exactly-once printing. ## Related articles - [Configure a saved printer](https://docs.ordering.co/docs/products/business-app/printing/configure-printer/) - [Configure a Star Micronics printer](https://docs.ordering.co/docs/products/business-app/printing/configure-printer/star-micronics/) - [Set up a Sunmi printer](https://docs.ordering.co/docs/products/business-app/printing/configure-printer/sunmi/) - [Manage saved printers and automatic printing](https://docs.ordering.co/docs/products/business-app/printing/saved-printers-auto-print/) - [Review an order summary](https://docs.ordering.co/docs/products/business-app/orders/order-summary/)