Prints on the status you choose
Tick the order statuses that should print. New orders from checkout, the POS and the kiosk all go through the same path, so a ticket looks the same wherever the order came from.
[ WordPress plugin v1.1.3 ]
Your WooCommerce orders, on the kitchen printer.
Print.Codeon is the WordPress half of CodePrint. It listens for orders on your site, signs them, and hands them to your printers through the CodePrint agent. Free to install, and it works whether or not you use CodeOrder.
WooCommerce 7.0+ and HPOS HMAC-SHA256 signed Retries when the network drops
1
An order is placed Checkout, POS, kiosk or a QR code at the table
2
The plugin signs and sends it HMAC-SHA256, over HTTPS, with an idempotency key
3
CodePrint routes it One ticket per printer, by location and category
4
The agent prints it USB or LAN thermal printer, in the kitchen
[ What it does ]
Four things, done properly.
Understands a restaurant order
Table number, service type, add-ons and the customer's note travel with the order, so the ticket says Table 12, eat-in, no onions rather than a bare list of products.
Survives a bad connection
A job that cannot be sent is queued in your own database and retried every minute, four times. Whatever still fails is listed with the error, and an email goes out rather than a ticket quietly disappearing.
Reprints on demand
Paper jam, or a ticket someone binned. Reprint from the order's own actions in WooCommerce — and from the order panel in CodeOrder's live orders screen.
[ Setup ]
From zip to first ticket.
Fifteen minutes, most of which is deciding which printer gets what.
- 1
Install the plugin
Download the zip, then in WordPress go to Plugins → Add New → Upload Plugin. Activate it. A Print.Codeon entry appears under the WooCommerce menu.
- 2
Pair it with your workspace
Open Print.Codeon and paste the API key from your CodePrint workspace. The plugin pulls your business and locations, and you pick the one this site belongs to.
- 3
Choose what prints
Tick the order statuses that should produce a ticket — most kitchens print on Processing, some on Completed. Anything not ticked is still reported to the dashboard, without printing.
- 4
Route it to a printer
Routing lives in CodePrint, not in WordPress: send everything to one printer, or split by product category so drinks reach the bar and food reaches the kitchen.
- 5
Place a test order
Use Test Connection in the plugin first, then put a real order through. The queue screen shows every job, when it was sent, and what came back.
[ On the ticket ]
What reaches the kitchen.
- Order number, date and time, in your site's own format
- Every line item with quantity, add-ons and per-line notes
- Table number or name, for a dine-in order
- Service type — eat-in, pickup or delivery
- Customer note and special instructions
- Billing and delivery address, when there is one
- Totals, tax lines, fees, tip and the payment method
The layout itself is a template in CodePrint, so you can change what the ticket looks like without touching WordPress.
What you need
- WordPress
- 5.8 or newer
- PHP
- 7.4 or newer
- WooCommerce
- 7.0 or newer, HPOS compatible
- A printer
- Any ESC/POS thermal printer on USB or LAN
- One computer
- Running the CodePrint agent, on the same network as the printer
[ Questions ]
Before you install it.
Do I need CodeOrder to use this?
No. The bridge works on any WooCommerce store. If you do run CodeOrder it reads the extra fields too — table number, service type and special instructions — and a Reprint button appears on each order in the live orders screen.
Does it print without the desktop agent?
No. The plugin sends the order to CodePrint; the agent, running on a computer next to your printers, is what puts ink on paper. Install it on the machine the printers are attached to, or one on the same network for LAN printers.
What happens if the internet drops mid-service?
The job goes into a queue in your own database instead of being lost. WordPress retries it every minute, up to four attempts, and anything that still fails is listed in the plugin with the error the API returned so you can send it again.
Can the same order print twice?
Each job carries an idempotency key, so a retry after a timeout is recognised as the same ticket rather than printed again. Reprints are deliberate: you ask for them from the order screen.
Is the connection secure?
Every request goes over HTTPS and is signed with HMAC-SHA256 using a secret only your site and your workspace hold. An unsigned request is refused, so nobody can make your printers produce tickets.
How do I update the plugin?
Download the current zip from this page and upload it over the old one — WordPress will offer to replace it. The bridge does not update itself yet.
Put it on your site.
The plugin is free. You need a CodePrint workspace for the routing and the agent — start one, pair the plugin, and print a test ticket today.