

The ReceiptKit settings screen — your print rules, each with an enable/disable toggle, a live health indicator, and a per-row Test print, plus the "request printer support" form for printers not yet on the supported list.
Print real receipts for your online orders — not invoices, receipts. Two ways to print, with the same designed templates: print from your browser on any printer installed on your computer (free, unlimited, nothing to install), or add the free Receipt Bridge for silent automatic printing on the events you choose — no PDF step, no print dialog, no clicks. Start with polished pre-made templates (customer receipts, kitchen tickets, delivery/pickup tickets, gift receipts, packing slips, refund slips), design image- and font-rich receipts in our visual designer, or generate with AI authoring tools.
Unlike PDF/invoice plugins, ReceiptKit renders a receipt you design — line items with variations and product add-ons, totals, logo, QR codes, barcodes, huge order numbers your kitchen can read across the room — and pushes it to your printer over a fast cloud connection through a small bridge app running on your own network. Design the receipt once in the ReceiptKit editor; change it any time without touching code, and size every element independently.
Supported printers: ReceiptKit prints to Star Micronics, Epson, Rongta, Munbyn, and most ESC/POS-compatible thermal printers (via the ReceiptKit bridge). Tested end-to-end: the Star mC-Print3 (our production model) and TSP100/TSP143 series, Epson TM-T88 series, Rongta RP326, and Munbyn 80mm models; other ESC/POS printers are supported generically. Look up your model in the printer compatibility matrix — and if yours doesn’t work, there’s a form in the settings to tell us.
$12.01 is compared numerically automatically.This plugin is a connector for ReceiptKit (https://www.receiptkit.io), the cloud receipt-printing service, and requires a ReceiptKit account. It communicates with ReceiptKit in these ways:
1. Automatic printing (bridge). When a print rule runs (or you click Test print), the plugin sends the mapped order data — line items, totals, order and customer details, and any extra order fields you configure — to ReceiptKit’s print API at www.receiptkit.io, authenticated with your public API key, so the receipt can be rendered and delivered to your printer.
2. Browser printing. Browser printing renders the receipt in your own browser; the order data never leaves it. To do that, the “Print receipt” page loads three things from your configured ReceiptKit host (www.receiptkit.io by default) over HTTPS, authenticated with your public API key where noted: (a) the template definition (your receipt design — layout, text and fields; authenticated), fetched by your server and cached locally for an hour; (b) ReceiptKit’s renderer script (/renderer/v1.0.0/receiptkit-browser-print.js), the service’s client-side component that turns a template plus order data into a printable receipt — loading it sends no order data, only the ordinary HTTP request; and (c) the font files your template uses, fetched by hash from ReceiptKit’s public font endpoint. After a receipt is printed, the plugin sends a small usage event to ReceiptKit’s API (event type, the template id, the order id, and “woocommerce” as the source) so your dashboard can show printing activity; no order contents are included.
3. Settings screen (data + live status). The settings screen loads your bridges, printers and templates from ReceiptKit’s API to populate the rule editor. It also opens a single read-only WebSocket connection (MQTT over WSS) to ReceiptKit’s live-status message broker at a3cdv9umpaq1po-ats.iot.us-east-1.amazonaws.com — an AWS IoT Core endpoint operated for ReceiptKit — authorized with your public API key, to show live bridge and printer status (online/offline, out of paper, cover open). This connection only receives status messages for your account; no order or customer data is sent over it. The MQTT client library (mqtt.min.js) is bundled with the plugin.
4. Printer support requests. If you submit the “Request printer support” form, the details you enter (printer make and model, order volume, your email, an optional note, and your store URL) are sent to ReceiptKit so we can follow up.
Every request the plugin’s server code makes to ReceiptKit carries the plugin version and the WooCommerce version (for example receiptkit-for-woocommerce/1.4.4 WooCommerce/10.1.0), alongside WordPress’s standard User-Agent (WordPress version and your store URL), so ReceiptKit support knows what your store runs.
Apart from the ReceiptKit renderer script and font files described in (2), which are part of the ReceiptKit service and load only on the “Print receipt” page, no remote scripts, styles or images are loaded from any host.
ReceiptKit: terms of service, privacy policy. The live-status endpoint runs on Amazon Web Services: AWS privacy notice, AWS service terms.