ReceiptKit for WooCommerce

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 receipt designer (try it in your browser, no account needed), 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.

What you can do

• Print any order from your browser — open an order, pick a template, click Print. The receipt is rendered in your browser and sent to whichever printer you choose in the print dialog, so it works with any printer that has a driver installed, thermal or not. Free and unlimited on every ReceiptKit plan. Each order also shows its print history.
• Build print rules: when an order event happens (status change, refund, new order placed, or a manual button), if conditions on the order data are met, then print to the bridge, printer and template you choose.
• Manage all your rules from one overview table — each with an enable/disable toggle and a live health indicator — and edit them in a focused pop-up.
• See live status for every bridge and printer on your account, right on the settings screen, so you know a rule can actually reach its printer.
• Print refund receipts automatically when an order is refunded (full or partial).
• Route different receipts to different printers — add one rule for a counter receipt and another for a kitchen ticket on the same event.
• Add conditions on order data: total, payment method, coupons, item SKUs/categories, country, refund amount, and more — with is / is not / greater than / less than / contains operators. Money like $12.01 is compared numerically automatically.
• Print item variations and product add-ons (“Size: Large”, “No onions”) under each line item, plus the customer’s note — so kitchen tickets never miss a modifier.
• Include data other plugins attach to orders — delivery/pickup dates and times, tips, gift flags — by listing the meta keys you want in settings. Only the keys you choose are sent, never an all-or-nothing dump of hidden fields.
• Print the order’s fulfillment method (shipping vs. local pickup), status, coupon codes, fees, and a per-rate tax breakdown for VAT/GST tax-invoice receipts.
• Works with Orderable out of the box: when the Orderable restaurant plugin is active, the service type (delivery / pickup / table), requested date and time slot, location, table number and tip are available in your templates automatically, with matching “Orderable” templates in the gallery and one-click recipes for kitchen, delivery, pickup and table tickets.
• Open a cash drawer before/after printing, and print multiple copies.
• Add any rule to the order screen’s Print actions menu for on-demand (re)printing.
• Test a rule against a recent order to see exactly which conditions pass before you enable it.
• Send a test print from any rule’s row to confirm that rule’s printer end-to-end.
• Design branded receipts, refund slips, packing slips, and kitchen tickets in ReceiptKit.
• Admin screens in your language: the plugin’s settings, rule editor and order screens are translated into Arabic, Danish, Dutch, French, German, Indonesian, Italian, Persian, Portuguese (Brazil), Spanish, Thai, Turkish and Vietnamese, and follow your WordPress language.
• Receipts in your store’s language: the plugin tells ReceiptKit your store’s language and currency, so your ReceiptKit account can default its receipt language to match your store.

How it works

1. Design a receipt template in your ReceiptKit dashboard (or clone a “WooCommerce Order” or “WooCommerce Refund” template from the gallery).
2. Install this plugin, paste your ReceiptKit public key, and click Connect.
3. Open any order and click Print in its ReceiptKit box — the receipt prints from your browser to any printer on your computer. That’s it for attended printing.
4. Want receipts to print by themselves? Install the free ReceiptKit bridge on a computer on the same network as your printer, then add a print rule (or start from a recipe) — choose when it runs, any conditions, and what to print.
5. Orders print automatically, silently, with no dialog.

Requirements

• An active ReceiptKit account and public API key.
• For browser printing: any printer installed on your computer with its manufacturer’s driver.
• For automatic printing: the ReceiptKit bridge running next to a supported thermal printer (Star Micronics, Epson, or ESC/POS-compatible).
• WooCommerce 8.0+ (High-Performance Order Storage supported).

External services

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, your store’s name, address and phone number (from WooCommerce settings) for the receipt header, 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. Retention: by default ReceiptKit does not keep this order data after the receipt is sent to your printer. If you turn on “Design and reprint with your real orders” (offered when you connect, and in your ReceiptKit Organization settings), ReceiptKit keeps the order data of your latest 100 printed orders, none older than 30 days, so you can preview your templates with real orders, view and reprint recent receipts in your dashboard, and ReceiptKit support can see what printed; older orders are deleted automatically, and turning the setting off deletes them all right away.

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, which may redirect to ReceiptKit’s font CDN at d1uf62nizas2ue.cloudfront.net (Amazon CloudFront, operated for ReceiptKit; it serves only font files, and the request carries no order data or API key). 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.

5. Template preview data. To set up your receipt templates so they preview the way your receipts print, the plugin sends ReceiptKit: your store name, address, phone number and logo (the site logo, WooCommerce email header image or site icon that prints best, as the image file WordPress already has); your currency, number, date and time formats; your tax rate names (for example “VAT 20%”); your first enabled shipping and payment method names; and example items (name, SKU, variation and price) from a few of your top-selling products, priced and formatted by WooCommerce. The customer on the example receipt is made up (name, email, phone and address are placeholders). What is not sent: no order, customer or personal data. When: once right after you connect, and whenever you click “Update previews from my store” on the Templates tab; never in the background. Why: ReceiptKit writes these values into your WooCommerce templates’ sample data, which previews and test prints use; real receipts always print the real order. Retention: ReceiptKit keeps the latest one with your account until it is replaced or you delete your ReceiptKit account.

6. Print rules. So your ReceiptKit dashboard can show how printing is set up, and ReceiptKit support can help when a receipt doesn’t print, the plugin sends ReceiptKit a copy of your print rules: each rule’s name, whether it is on, its event and order status, its conditions, and its printer, template, copies and cash-drawer settings. With them go the names of your Extra order fields (the template field each one becomes and its label, for example deliveryTime “Delivery time”), so the ReceiptKit designer knows your store sends them and doesn’t warn that it doesn’t. What is not sent: no order, customer or personal data, and never the values of your extra order fields. A condition on a customer field (billing email, customer note, refund reason or a custom order field) is sent without its value, marked as hidden. When: shortly after you change your rules or Extra order fields (and once after updating the plugin); unchanged rules are not sent again. Retention: ReceiptKit keeps the current rules and earlier versions with your account until you delete your ReceiptKit account. The rules in your store stay the ones that print; ReceiptKit never changes them. Each print in (1) also says what sent it (a print rule and its event, the order screen, or a test print) so your print history can show it.

7. Deactivation feedback. When you deactivate the plugin, a short optional dialog asks why. Only if you pick a reason and click “Send & deactivate”, the plugin sends ReceiptKit: the reason you picked, the note you typed (if any), your email address (only if you tick “You can email me about this”), your store URL (in WordPress’s standard User-Agent) and the plugin and WooCommerce versions. Your API key is included only if the store is connected; otherwise it is sent without one. “Skip & deactivate” sends nothing. Why: to learn what to fix, and to reply when you ask us to. Retention: ReceiptKit keeps it with your account (or, without one, with your store URL) until you delete your ReceiptKit account or ask us to remove it.

8. Diagnostics. The Settings tab has a “Send diagnostics” button for when you need help. Only when you click it, the plugin sends ReceiptKit a snapshot of how printing is set up on your store: the plugin, WooCommerce, WordPress and PHP versions; your site language and time zone; your theme and active plugins (names and versions); whether HPOS and multisite are on, and the memory limit; whether WP-Cron runs (its settings and how many scheduled tasks are late); your ReceiptKit connection (the ReceiptKit URL, whether a public or secret key is set but never the key itself, your organization name, whether ReceiptKit answered and how fast, and how many bridges, printers and templates it has); your extra order field keys and line item setting; your print rules (as in (6)); and up to 50 recent print attempts (time, order number, bridge or browser, template, rule, printer, and whether it worked or the error). What is not sent: no customer or order details; print attempts carry only the order number. “Show what will be sent” shows the exact data first, and you can copy or download it to email it instead. ReceiptKit answers with a code (for example RK-7F3A9C) to quote to support. Retention: ReceiptKit keeps each snapshot with your account until you delete your ReceiptKit account.

Every request the plugin’s server code makes to ReceiptKit carries the plugin version and the WooCommerce version (for example receiptkit-for-woocommerce/1.6.0 WooCommerce/11.1.2), alongside WordPress’s standard User-Agent (WordPress version and your store URL), so ReceiptKit support knows what your store runs.

The authenticated requests in (1), (2), (3), (5), (6) and (8) also carry your store’s language and money format: the WordPress site language (for example de_DE), the WooCommerce store currency and its symbol, the currency position, the number of price decimals, and the decimal and thousand separators. ReceiptKit stores the latest values with your account so your receipts can default to your store’s language and show prices the way your store does. These are store settings only; no order, customer or personal data is part of them. The printer support request form in (4) does not send them.

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 and the font CDN run on Amazon Web Services: AWS privacy notice, AWS service terms.