| 开发者 | receiptkit |
|---|---|
| 更新时间 | 2026年9月5日 06:51 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
$12.01 is compared numerically automatically./wp-content/plugins/receiptkit-for-woocommerce, or install it from the Plugins screen.rk_pub_) and click Connect.You need a thermal printer that speaks StarPRNT, Star Raster, or ESC/POS — that covers Star Micronics, Epson, Rongta, Munbyn, and most generic ESC/POS-compatible models. Tested end-to-end: the Star mC-Print3 and TSP100/TSP143 series, the Epson TM-T88 series, the Rongta RP326, and Munbyn 80mm models. Check your exact model in the printer compatibility matrix. If your printer doesn't work — an impact/dot-matrix model, or a brand that doesn't follow ESC/POS — use the Request printer support form on the settings screen to tell us the make and model, and we will email you when yours is supported.
In your ReceiptKit dashboard under Settings → API Keys. Use your public key (rk_pub_…) — it is safe to store here and can only print and read status.
Each rule is a When / If / Then automation. When an order event happens (a status change, a refund, an order being created, or a manual click), the rule checks if your conditions match the order's data, and if so runs the then — one or more print actions (template + printer + optional cash drawer + copies). Add as many rules as you like; for example one for order receipts on Processing and another for a refund receipt when an order is refunded. Use the Test button on a rule to check it against your most recent order before enabling it.
Yes. Add a rule whose event is Order is refunded and point it at a refund template (clone the "WooCommerce Refund" template from the gallery). It prints on both full and partial refunds, once per refund.
Yes. Many plugins (delivery-slot pickers, tip add-ons, gift options) store their data as order meta. In WooCommerce → ReceiptKit → Settings → Extra order fields, list the meta keys you want on your receipts — one per line, with an optional label after a | (for example _delivery_time | Delivery time). Each order then sends those values to your templates two ways: a repeatable metaFields list (label + value) you can drop into any template, and an individual field per key (_delivery_time becomes {{deliveryTime}}) for prominent placement — like a big pickup time at the top of a kitchen ticket. Only the keys you list are sent.
Yes. Each line item includes a meta field with its variations and product add-on selections ("Size: Large", "No onions"), one per line. The WooCommerce gallery templates render it under the item name; on kitchen tickets it's bold so modifiers never get missed.
Yes. The plugin reads orders through WooCommerce's standard order APIs and declares HPOS compatibility.
No. Each rule prints an order (or refund) once, when its event happens after the rule is configured — never retroactively.
meta), so kitchen tickets can print every modifier.metaFields row and as its own template field (e.g. _delivery_time → deliveryTime).shippingMethod), order status, coupon codes, fees, and a per-rate tax breakdown (taxLines) for VAT/GST tax-invoice templates.