Kitchen printing

The restaurant problem

A browser cannot reliably print kitchen tickets on its own.

How Codefusion solves it

PrintNode (or equivalent) as a server-side print bridge. Accept prints one original ticket. Reprint is a separate, labelled job. If the printer fails, the order is still accepted.

What is included

Print driver on the server, default kitchen printer mapping in the owner dashboard, original + reprint, due time on scheduled tickets.

How installation and onboarding work

Codefusion sets PRINT_DRIVER and the API key on the server. The owner saves the PrintNode printer id. A test accept must print exactly one original.

The commercial benefit

The ticket appears when the kitchen accepts, without putting API keys on the tablet.

Who it suits

Every live restaurant that prepares food from the terminal.

What Codefusion manages

Driver, API key, platform. Never paste PrintNode keys into the tablet or public site.

What the restaurant manages

Paper, printer power, reprint after a jam.

Hardware requirements

80mm printer plus print bridge. USB-only consumer printers are not the design.

Support provided

Failed jobs show on the terminal health strip. Staff reprint when the printer recovers.

Frequently asked questions

Does a printer fault cancel the order?

No. Accept stays. The print job is marked failed and staff reprint.