Device-based printing routes prints to a specific station's printer, regardless of where the order was opened or which channel it was placed through. Use it when you have multiple POS stations and want each station's actions to print at its own printer.
For example: a customer opens a tab at the Main Bar, then moves to the Cigar Room. Staff at the Cigar Room add an item to the tab. With device-based printing set up, the receipt for that addition prints at the Cigar Room's printer — not back at the bar.
📎 Related: Channel-Based Printing filters by channel (e.g. dine-in vs takeaway). Device-based filtering is a sibling to channel filtering and the two can be combined.
Pairing a device
Each browser-based POS station gets a one-time pairing. Once paired, that browser carries a device cookie and keeps its identity until you remove it.
On the dashboard (admin), go to Settings → Devices.
Click Pair new device and give it a name — for example Main Bar, Cigar Room, Cashier 1. Names show up later in printer-group settings, so make them recognisable.
Click Generate pairing code. A short 8-character code appears, along with a QR.
On the POS device (the tablet or browser that will become the station), open
merchant.papaya.co.th/pairand either type the code or scan the QR.The device is paired. It appears in your Devices list and is ready to route prints once a printer-group filter references it.
Routing prints to a device
After pairing, link a printer group to one or more devices:
Go to Settings → Direct Printing → Printer Groups.
Edit (or create) a printer group.
In the Devices field (sits next to Channels), pick the devices that should trigger this group's prints.
Save.
Leave the Devices field empty if the group should print regardless of which device rang the print — for example a general kitchen ticket that always fires. Set one or more devices to scope a group to specific stations only.
When a device-filtered group is set and an order is rung up from a non-paired browser (e.g. customer-app QR), the group is skipped. That's intentional — device filtering is for station-specific routing.
How device + channel filters combine
The two filters compose with AND. If you set both, the group fires only when both the channel matches and the device matches.
Devices filter | Channels filter | Behaviour |
Empty | Empty | Prints for every order |
| Empty | Prints only for orders rung at Main Bar |
Empty |
| Prints only for dine-in orders |
|
| Prints only for dine-in orders rung at Main Bar |
Re-pairing a device
If a device loses its cookie (browser cleared, profile switched, cookies expired):
Go to Settings → Devices and click the 🔗 re-pair icon next to the device.
A new code appears. The device's name and printer-group bindings stay the same.
Enter the new code on the device. It's back online.
Re-pairing is faster than removing and re-adding because the device keeps its existing id, so any printer groups that reference it keep working without re-configuration.
Removing a device
To unpair permanently:
Settings → Devices → click the 🗑 trash icon.
Confirm
The device row is removed and any printer-group references to it are stripped automatically. Future prints from that browser will skip device-filtered groups.
FAQ
What happens to existing printer groups when this feature is enabled?
All existing printer groups have an empty Devices filter, so they fire for every order regardless of device. No change in behaviour until you add a device filter to a group.
Can the same browser hold multiple devices?
No — pairing a new device on a browser replaces the previous one's cookie. The previous device row stays in the Devices list but no longer routes from this browser. Re-pair the original if you want it back.
Can a customer phone trigger device-filtered prints?
No. Customer-app orders carry no device cookie, so device-filtered groups skip them. Customer-facing orders should use unfiltered groups (or channel-filtered groups).
Does pairing a device let staff log in?
No. Pairing is for print routing only — separate from staff login. Staff still log in with their normal credentials.