Why printers are per-location
A receipt printer is a physical device that lives at one front desk. Even if two branches use the same printer model, they almost never share the same connection details, vendor account, or paper workflow.
The Receipt Printer settings sit inside the per-location container and share the settings_payment_location_enabled flag with the Payment area. When that flag is on, each branch carries its own printer configuration row tied to its location_id.
Configuring vendor & connection per branch
Go to Admin → Settings → Receipt Printer, switch the location selector to the branch you want to set up, then choose:
- Vendor — currently Amego is the supported integration; pick this if the branch issues Amego e-invoices
- Connection type — how the printer is reached (for example direct device or cloud relay)
- Any branch-specific credentials, store code, or device identifier the vendor requires
Save and repeat for the next branch. The credentials stored under one branch never leak into another, so a misconfigured device at one site cannot accidentally print receipts at another.
Auto-print rules per branch
Each branch also has its own automatic receipt generation toggle. With it on, a receipt is issued and printed the moment an order is completed at that branch; with it off, staff must trigger the print manually.
This is helpful when one branch runs a busy walk-in counter where every sale needs an immediate paper receipt, while another branch handles mostly pre-paid bookings and prefers to print on request only. Because the rule is read from the branch's own row, changing it at one location doesn't disturb anywhere else.
