Printers: definitions & routing

Who this is for: reach requires printing.printer.read; adding, editing or routing requires printing.printer.manage. Where: Settings → Output & Operations → Printers

Two tabs, the same ?tab= pattern used across Settings (Charge codes, tax and billing setup is the other example): Printers is what the physical devices are, Routing is what prints to each of them.

Printers tab#

Each row is one printer: Name, Location (which outlet or area it sits in — the same outlets configured in Outlets and catalog), Type (e.g. Kitchen), and Active. Select Add printer to register a new one, or Edit an existing row.

Deactivating a printer removes it from the Routing tab's picker without deleting any route that already points at it — the same deactivate-not-delete convention as a reference-list entry or a charge code.

Routing tab#

A route is Document class → Outlet → Printer. The document class is the kind of output — kot (kitchen order ticket), drr (daily revenue report, configured on the night audit's Report Layout tab), a folio, or any other printable document class the product defines.

An outlet-scoped route wins for that outlet; a route with no outlet set is the hotel-wide fallback — what prints when nothing more specific matches. Select Add route to create one, and the trash icon to remove it.

Where routing actually fires#

Routing is configuration, not the print job itself — it is what the KOT-firing flow in Point of Sale, the night audit's report step, and document generation all resolve against when they ask "where does this go." A document class with no matching route and no fallback has nowhere to print, so set the hotel-wide fallback for every class you use before relying on an outlet-specific override.

What's next#

• Letters & document templates — the templates a printed document renders from
• Running the night audit — the Report Layout tab that names the drr document class
• Outlets and catalog — the outlets a route can scope to