Troubleshooting & FAQ
Printing is not working
Check client capability, printer power/network, Store assignment, print-job state, and bridge ownership before reprinting repeatedly.
Overview
- Native MiniTill POS can provide direct local printing capabilities; Web POS does not have the same native local-hardware path.
- MiniTill records whether a print request is waiting, completed, or failed so it can be retried safely.
- Printer configuration is Store-scoped.
- If printing depends on a MiniTill device or printer bridge, make sure that device is online and connected to the configured printer.
When to use this
- Use this when receipts/kitchen dockets do not print, print to the wrong device, or repeatedly fail/retry.
Step-by-step
- Confirm the client actually supports the intended local printing path.
- Check printer power, paper, network/address, and Store assignment.
- Run a test print from printer settings where available.
- Inspect failed print-job state and Retry once the underlying issue is fixed.
- For bridge workflows, confirm the intended active bridge/session owns automatic printing.
Common mistakes
- Do not expect Web POS on a laptop to behave like native POS for local printing without a supported bridge/native path.
- Do not repeatedly generate new receipt jobs while an existing failed/retry job is unresolved.
- Do not change printer addresses during service without confirming routing.
Troubleshooting
- If only one printer fails, focus on that printer/network/configuration.
- If every printer on one POS fails but other POS devices work, focus on that client/bridge session.