Topics: Setting up integrations
- Help & docs
- Setting up integrations
- Connect WooCommerce
Connect WooCommerce
Rechnungskit connects WooCommerce without a plugin, through the REST API with signed webhooks and a 4-hourly catch-up. Setup, prepayment, post-purchase upsells, Germanized vouchers and limits.
Updated
On this page 13
- Setup
- What happens automatically
- Pay by invoice with WooCommerce
- Order reference or cost centre
- Service period per line
- Prepayment with WooCommerce
- Post-purchase upsells (FunnelKit, CartFlows)
- Vouchers (Germanized)
- Invoice amount equals the amount paid
- Limits
- Several shops in one project
- Shipping tax
- Where to find it in the app
Rechnungskit connects WooCommerce without a plugin: a lean REST API connection delivers the order data, and all the invoicing logic runs outside your shop. The product page gives an overview of the WooCommerce connection without a plugin. What the monthly batch for your tax advisor looks like, and which routes lead from WooCommerce to DATEV, is explained in the guide WooCommerce DATEV export.
- MatchPayment to order, by payment reference or order number
- Invoice at "Completed"E-invoice in ZUGFeRD format; the shipping date is the date of supply
- Cancellation on refundCancellation invoice; the invoice itself stays unchanged
Rechnungskit matches the payment to the order by payment reference or order number (see zahlungen-abgleich). For goods, the e-invoice in ZUGFeRD format is created once the order is set to "Completed", and the shipping date becomes the date of supply. Every document is then archived unchangeable in the GoBD archive (the German bookkeeping rules) and goes into the monthly DATEV export, with revenue and payments kept separate.
Setup
- Step 1 · WooCommerceCreate a REST API keySettings → Advanced → REST API, permission Read/Write
- Step 2 · RechnungskitEnter the credentialsUnder Settings → Connections → Shops and payment providers: shop URL, consumer key (ck_…) and consumer secret (cs_…)
- Step 3 · automaticCheck and create webhooksRechnungskit creates the webhooks and signs themConnected
In WooCommerce, go to Settings → Advanced → REST API and create a new key with Read/Write permission. Rechnungskit only needs write access to set up the webhooks for you.
In Rechnungskit, under Settings → Connections → Shops and payment providers, enter the shop URL (https://your-shop.com), the consumer key (ck_...) and the consumer secret (cs_...). The shop URL must be the final address (with or without www, the way the shop actually responds); Rechnungskit does not follow redirects and tells you so when you connect.
Once the shop URL is in, the link "Open REST API keys in your shop" takes you straight to the right page in WooCommerce:

Rechnungskit checks the credentials, creates the webhooks automatically and signs them. You don't need to configure anything else in WooCommerce.
What happens automatically
- New and changed orders arrive by signed webhook; refunds and the shipping status (order "Completed") ride on the same events.
- A 4-hourly sync catches anything a webhook may have missed: all orders changed in the last 24 hours, fetched completely page by page, even with hundreds of orders a day.
- On the Orders page, "Sync now" also starts a sync of the last 7 days in the background, for example after an outage or right after setup.
- If the webhook goes quiet, Rechnungskit helps itself: the sync reactivates paused or disabled Rechnungskit webhooks in the shop through the REST API (and recreates missing ones), fetches orders every 15 minutes instead of every 4 hours in the meantime, and loads an order individually right away as soon as a payment refers to it but the order is still missing. The task "Webhook-Verbindung still" (webhook connection silent) only stays open if none of this works; then check WooCommerce under Status → Logs (source "webhooks-delivery") or reconnect.
- Products are taken over from the order lines and maintained under Products → From your shops.
- Refunds create the cancellation invoice (Storno) automatically. For a partial refund it lists exactly the refunded items WooCommerce reports, even when the money went back through PayPal, Stripe or Mollie. If the item details are missing, your document rule decides: proportional, as a single line, or allocated manually (see belege-archiv). For pay by invoice, the open item drops by the amount of the cancellation invoice, see Refunds in the shop for pay by invoice.
- Payment methods from payment plugins (WooCommerce Stripe with card, SEPA direct debit, Klarna and similar, PayPal Payments, Mollie) need no document rule once the provider is connected in Rechnungskit, because the payment arrives from that provider. Stripe reports a SEPA direct debit only after the bank has confirmed it, usually within a few business days. Until then the order reads "Payment is being fetched from Stripe", and the invoice is created when the payment arrives (see stripe).
- Existing documents from an old PDF plugin stay untouched, and your number range continues without a break (set the starting number at go-live).
Pay by invoice with WooCommerce
If your shop's payment method (for example "invoice") is listed under pay by invoice in the document rules, the invoice carries a payment term and your bank details and shows up as an open item under Invoices → Open items (/receivables). The statuses "Processing" and "Completed" do not count as payment. The invoice is paid once a payment is matched or you mark it paid under open items. The payment method on the invoice is the name your customers saw in the shop, such as "Kauf auf Rechnung".
When the invoice is created: for orders with shipping, when you set them to "Completed". For orders without shipping, such as tickets or other virtual products, as soon as the order comes in ("Processing" or "On hold").
Orders over €0, such as the start of a subscription with a trial period, get no invoice. Without consideration there is no supply under § 1(1) No. 1 UStG, which is what § 14(2) UStG requires an invoice for. The invoice comes with the first order that has an amount. One exception is an order paid with a multi-purpose voucher: there the voucher is the consideration (§ 3(15) UStG), and the invoice is created as usual. If you give goods away with a 100% discount, ask your tax advisor whether that counts as a deemed supply under § 3(1b) UStG.
Order reference or cost centre
Many business customers need their own reference on the invoice, usually a cost centre or purchase order number. Add a field to your checkout for it, for example with a checkout field plugin, and give it a name containing "kostenstelle", "bestellreferenz", "kundenreferenz" or "buyer_reference" (such as billing_kostenstelle). Alternatively, set the order meta field _rk_buyer_reference. Rechnungskit puts the value on the invoice as "Ihre Referenz" and into the e-invoice (buyer reference, BT-10). The invoice stays a regular ZUGFeRD invoice. Rechnungskit does not read the order notes, because customers write other things there too.
Service period per line
If you sell services that run over a period, such as maintenance, courses or rentals, the invoice can show the service period instead of the shipping date. Give each order line two meta fields, for example with a plugin or a code snippet in your shop:
rk_leistung_von: start, for example2026-11-01rk_leistung_bis: end, for example2026-11-30
For a single day, rk_leistungsdatum is enough. A period that covers just one day also shows on the invoice as "Service date" with one date. Dates can be YYYY-MM-DD or DD.MM.YYYY. With a leading underscore (_rk_leistung_von) the fields stay hidden in WooCommerce and don't show up in customer emails.
How the period ends up on the invoice:
- If all lines share the same period, it goes into the invoice header as the service period (BT-73 and BT-74 in the e-invoice).
- If the lines have different periods, the header shows the overall span and each line shows its own period (BT-134 and BT-135).
- Lines without the fields work as before.
If you use accrual accounting (Bilanz) and the product is set to "one-off service" (an event ticket, say), Rechnungskit books a payment received before the end of the period as an advance payment. In the DATEV export it turns into revenue on the last day of the period.
An order with a period is invoiced when it's paid and doesn't wait for "Completed". If an order that gets shipped also has lines without a period, the shipping date stays the date of supply.
Prepayment with WooCommerce
Prepayment works fully: the order waits ("On hold"), you mark it as paid in the shop once the money arrives ("Processing"), and only then is the invoice created, for goods once the order is "Completed". Your shop remains the source of truth for incoming payments; Rechnungskit does not reconcile a bank account. The payment method is mapped by the exact gateway name from the shop (see zahlarten-rechnungskauf-vorkasse).
Post-purchase upsells (FunnelKit, CartFlows)
If an upsell plugin adds items to the existing order after checkout and collects a second payment for them, Rechnungskit automatically creates a supplementary invoice (Nachtragsrechnung) for exactly the new items. The first invoice stays archived unchanged (see upsell-nachtragsrechnung).
If the plugin puts the upsell items on the same order before it ships (FunnelKit does), there is no supplementary invoice: the one invoice at dispatch contains all items, and both payments settle it.
Vouchers (Germanized)
If a customer redeems a multi-purpose voucher from Germanized (created in Germanized as a Mehrzweckgutschein), Rechnungskit recognizes this on the order. A voucher is a payment, not a discount: the invoice shows the VAT on the full amount and names both parts, for example "Credit card (€54.18) and voucher (€25.00)". In the voucher register under Vouchers, the liability goes down by the redeemed amount. If a customer pays entirely with a voucher, Rechnungskit issues the invoice without an incoming payment. Regular discount coupons (percentage or fixed amount) remain discounts and reduce the invoice amount.
If your voucher plugin books the redemption as a negative fee without VAT (for example "Wertgutschein: ABC123" with -€50), Rechnungskit also recognizes it as a multi-purpose voucher and handles it the same way.
Fees with a positive amount, such as reusable packaging, become their own invoice line with the VAT rate from WooCommerce.
Fees with a negative amount and VAT, such as a "Bundle-Rabatt (2 Beutel · −6%)" from a bundle or discount plugin, are discounts. Rechnungskit spreads them over the order's lines and uses the fee name as the discount reason. VAT per rate stays as WooCommerce calculated it: the invoice has to show the consideration broken down by tax rate, including any reduction agreed in advance (§ 14(4) sentence 1 no. 7 UStG). If WooCommerce sends no tax amounts per rate, Rechnungskit splits the discount by the gross value of the lines at each rate.
Rechnungskit does not recognize other voucher or store credit plugins yet. If you use such a plugin, write to us at support@rechnungskit.de before you rely on it.
Invoice amount equals the amount paid
The invoice is for the amount your customer paid in WooCommerce. Rechnungskit handles four cases on its own to get there:
- Product bundles and free items (for example with WPC Product Bundles): some plugins show a price on bundle parts but don't charge it. Those lines appear on the invoice at €0.00, so the quantity and type of goods are complete. The price sits on the lines the shop actually charged.
- Shipping: what counts is the shipping amount included in the order total. If the shipping line and the order's totals disagree, Rechnungskit takes whichever one makes the order add up to the amount paid and takes the VAT out at the shipping's rates. If the shipping line is missing, the order's totals apply.
- VAT rate per line: Rechnungskit uses the rate WooCommerce actually charged tax at, even when the order lists other rates with no amount.
- Upsell charges (FunnelKit): when an upsell plugin takes a second payment after checkout, WooCommerce often recalculates shipping for the mixed cart and lowers the order total, even though the shipping was already charged with the first payment (for example order total €53.46, paid €53.57). If the difference is exactly the shipping, the invoice shows the shipping that was actually charged and is for the amount paid, because the taxable amount is what the customer spends (§ 10(1) sentence 2 UStG). Shipping is split across the VAT rates by the ratio of gross values (BFH, judgment of 22.01.2025, XI R 22/22). This applies when the difference is at most 60 cents and every later payment matches items on the order exactly. The invoice page shows both amounts. Everything else stays at the order total.
If an order still adds up to a different amount than was paid (more than rounding cents), Rechnungskit doesn't issue an invoice. The payment stays linked to the order, and a task shows both amounts. Once the order has been imported again and the amounts match, the invoice is created automatically. A redeemed multi-purpose voucher counts towards the amount paid.
If the payments so far don't cover the order total, the invoice for a shipped order waits for the further payment, for 8 to 12 hours at most, since PayPal arrives by pull. Orders paid in full by one payment never wait. If the payment only comes after the invoice, the invoice stays unchanged (GoBD) and the payment settles it. The few cents' difference then shows on the payment and on the invoice page.
Limits
- The API key needs Read/Write. With a read-only key the connection deliberately fails when creating the webhooks, instead of running silently without webhooks.
- WooCommerce has no product webhooks. The catalog is imported when you connect, then updated once a day automatically and at any time through "Sync products" on the Products page. You maintain names and categories in Rechnungskit.
- If a product was sold before it reached the catalog (source "Shop" without an item ID), the next product sync links it to the WooCommerce product by its SKU. Your category and names are kept.
- WooCommerce Subscriptions is supported; each recurring payment creates its own invoice with the correct service period.
Several shops in one project
If you run two or more WooCommerce shops under one company, connect them in the same project. Once the first shop is connected, Settings → Connections → Shops and payment providers offers "Connect another WooCommerce shop". The shop address decides what happens: a new address becomes its own connection, and the address of a shop that is already connected renews that shop's keys.
- Each shop keeps its own orders. If both shops have an order #1234, they are two separate orders. Products, refunds and prepayment payments also stay with their shop.
- One PayPal connection covers all shops. So that each PayPal payment reaches the right shop, give every shop its own "Invoice prefix" in WooCommerce PayPal Payments, for example "SHOPA-" and "SHOPB-". The plugin puts the prefix in front of the order number it sends to PayPal. Rechnungskit reads the prefix from the shop when you connect and during the daily product sync. If it finds none, enter it on the shop's card under "PayPal invoice prefix".
- If no prefix fits, Rechnungskit looks for the order number in all shops. When only one shop has it, the payment is matched there. When several shops have it, you get a task to assign the payment yourself.
- If each shop has its own Stripe account, connect every account separately ("Connect another Stripe account") and pick its shop on the Stripe card under "Belongs to shop". Payments from that account then only go to that shop's orders (see stripe).
Once you have two shops, the "Shops" page (/settings/shops) lets you set what differs per shop. You reach it under Settings → Connections → Shops and payment providers on the WooCommerce connection via "Number range, template, sender and KOST1 per shop". Empty fields use the project's setting.
- Shop name: the brand, e.g. "Fundraisingtage". Rechnungskit shows it in filters and lists. It does not appear on the invoice.
- Own number range: e.g. FT-JJJJ-####. Invoices for this shop's orders then get FT-2026-0001 and so on, their cancellations FT-S-…, and in test mode TEST- comes first. The prefix must differ from every other number range in the project; Rechnungskit checks this when you save. You can set a first number as long as no invoice has come from the range yet. Issued invoices keep their numbers. If you switch the range off, new invoices use the project's range again, and a cancellation always follows the range of its invoice.
- Invoice template: under Settings → Documents → Invoice template, pick the shop under "Template for" and give it its own logo, colours and texts. The preview shows the selected shop's template. Company name, address and tax numbers stay those of your business, because every shop in a project issues invoices in the name of the same company.
- Sender name: used in the From field and as the company name placeholder in mails to this shop's buyers (invoice mail, request for invoice details). The legal details in the mail footer still name the company. The email texts themselves apply to all shops.
- DATEV cost center (KOST1): bookings for this shop's orders carry it (see datev-steuerkanzlei, cost centers).
On Orders, Invoices, Payments and Overview → Analytics, the "Shop" filter narrows the view to one shop. Counts and totals then cover only that shop, and the period, search and other filters still work alongside it. The evidence package on the Orders page then holds only that shop's orders. Invoices → Needs you still shows every task. In Analytics, payouts stay unfiltered, because one payout contains payments from several shops.
Shipping tax
Rechnungskit applies the tax rate of the goods to shipping, even if the shop reports a flat 19 %. For mixed carts, shipping is split by the gross value of the goods; the guide Shipping costs and VAT explains the background with examples. You find the setting per shop connection under Settings → Documents → Document rules, card "Shipping tax".
Where to find it in the app
Recent changes
Rechnungskit is not a tax advisory or law firm. This article explains general principles and does not replace advice from a tax advisor (Steuerberater, § 5 StBerG) or a lawyer (§ 3 RDG). Rechnungskit is built for businesses based in Germany and prepares documents, tax rates and bookings automatically. How your specific case is treated remains your decision, ideally together with your tax advisor or a lawyer.