Settings
Configure and Test Kiosk Printer Names
The Kiosk Print tab accepts one or more printer-name rows for the active branch. Names are trimmed and duplicates are removed when saved, but current kiosk and QR catalog responses expose only the first saved name as printer_name.
- Menu path
- Settings -> Sales Channels -> Kiosk -> Print
- Verified from
- Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence
Live demo Settings -> Sales Channels -> Kiosk -> Print audited and captured 2026-09-04, frontend/modules/settings_write.html kioskprint_form, frontend/static/script/js/modules/js/settings.js printer row loading add remove normalization and save, api/src/models/setting.model.js kioskPrinterSettingsModel, api/src/repositories/item.repository.js accessKiosk and accessQr first-printer response, api/src/controllers/settings.controller.js kioskPrinterSettings plan access
Understand What Is Saved and Used
| Behavior | Current result | Operator consequence |
|---|---|---|
| Printer rows | The page can load and save multiple names. | Put the intended primary kiosk printer first. |
| Normalization | Leading and trailing spaces, blank rows and duplicate names are removed. | Reopen the tab after Save and review the resulting ordered list. |
| Legacy compatibility | The first saved name is also stored as printer_name; clearing every row sets it to null. | Removing or reordering the first row can change the printer used downstream. |
| Customer-channel response | Current kiosk and QR responses expose only printer_name, not the full printer_names array. | Do not assume every saved row receives a copy; prove each required destination physically. |
| Save result | A successful request reports Kiosk settings updated successfully. | The message proves persistence, not printer connectivity or paper output. |
Find the Exact Printer Name
- Use the same computer, kiosk device or print bridge that will produce customer orders.
- Open the operating-system printer list or the print bridge configuration and identify the exact queue name.
- Confirm the queue can print an operating-system test page before configuring Posnic.
- Record spelling, spaces, hyphens and suffixes exactly; the Posnic field is a name, not printer discovery.
- Avoid friendly abbreviations unless the connected print service uses that exact abbreviation.
Configure the Primary Kiosk Printer
- Confirm the active branch and Kiosk Store ID.
- Open Settings -> Sales Channels -> Kiosk -> Print.
- Enter the exact working queue name in the first Printer Name row.
- Click Save and wait for Kiosk settings updated successfully.
- Leave the tab, return to Print and confirm the same name reloads in the first row.
- Start a fresh customer-facing kiosk session for the same Store ID before testing.
Add, Remove and Reorder Printer Rows
- Click plus to append a new empty row. Only the last row shows the plus control.
- The trash control removes a row when several exist; on the final remaining row it clears the field instead.
- To reorder names, edit the row values into the required order and Save.
- Duplicate or empty values disappear from the saved list because the client and API normalize them.
- Current customer-channel code consumes only the first saved printer. Additional rows are stored configuration, not proof of multi-printer delivery.
Run a Physical Kiosk Print Test
- Load paper, power on the printer and clear any paused or offline queue state.
- Open the exact customer-facing kiosk or QR route for the configured branch in a fresh session.
- Create a low-value controlled order with a distinctive item and quantity.
- Complete the approved payment path and record the kiosk order ID.
- Confirm one legible output reaches the intended printer without a duplicate copy.
- Check shop name, order ID, item, quantity, modifiers where applicable, total, payment state, date and time.
- Find the same order in Detailed Kiosk Reports and compare its values with the paper output.
- Repeat from every kiosk device or QR route that the shop will use.
Troubleshooting
| Symptom | Check | Corrective action |
|---|---|---|
| Save succeeds but nothing prints | A saved name does not establish connectivity. | Print an OS test page, verify the exact queue name and inspect the kiosk print bridge or device. |
| Wrong printer receives the order | The first saved row may name another queue. | Put the required primary queue first, Save, reopen and retest in a fresh kiosk session. |
| Second saved printer gets no copy | Current kiosk and QR responses expose only the first printer_name. | Do not promise multi-printer output from extra rows; use the approved print service topology and test every destination. |
| Duplicate names disappear | Client and API remove duplicate trimmed values. | Keep each intended queue name once. |
| Last row will not delete | The final row is retained as an empty input by design. | Clear it and Save to remove all configured printer values. |
| Old name returns | Save failed, the wrong branch is active or another operator changed it. | Confirm branch, save again, wait for success and reopen the tab. |
| Order prints twice | More than one bridge or device may process the same order. | Stop rollout, preserve the order ID and logs, and leave only the intended consumer active before retesting. |
| Paper prints unreadable or cropped | Driver, paper width, encoding or receipt settings may not match. | Correct the OS driver and receipt format, then run another controlled order. |
Go-Live Record
- Branch, Store ID and customer route tested.
- Exact first printer name and operating-system test-page result.
- Every additional saved row and its proven purpose.
- Kiosk order ID, payment method, printed date and device.
- Paper content and Kiosk Report reconciliation result.
- Duplicate, offline and restart test results.
- Named operator and manager approval.