Shopware sevDesk integration

What a Shopware to sevDesk integration actually does

Shopware knows everything about a sale: the line items and their tax rates, the customer and their billing country, the discount, the shipping, the payment method, the invoice document it generated, and the credit note three days later when part of the order came back. sevDesk needs all of that as clean accounting records - an invoice or voucher on the right revenue account, against the right contact, with the right tax type and date, so that when your tax advisor pulls the DATEV export at month-end everything is already correct.

The gap between a shop that thinks in orders and an accounting tool that thinks in Debitoren, tax types, and cash accounts is where the manual work lives today. A Shopware to sevDesk integration closes it: it reads each relevant order event from Shopware, applies your accounting logic, and writes the matching record into sevDesk without anyone opening a spreadsheet.

What data moves

Shopware object / event	Becomes in sevDesk	Notes
Customer (billing address)	Contact / Debitor	Matched on customer number + email; new contact only when no match exists
Paid order	Invoice (Rechnung) or revenue voucher	Line items mapped to the correct revenue account and tax type
Order line items & shipping	Invoice positions	Shipping is its own taxable position, not folded into the goods
Tax lines per country	sevDesk tax type / rate	Domestic, EU OSS distance sale, EU B2B reverse-charge, third-country export
Shopware invoice document (PDF)	Attached to the sevDesk record	Keeps booking and document on the same number
Credit note / cancellation	sevDesk credit note (Storno)	Reverses the original invoice’s accounts and tax types
Payment transaction (paid)	Payment / cash-account booking	Reconciled per payment method against the right sevDesk account

The exact revenue accounts, tax types, number ranges, and cash accounts are agreed once and encoded in the pipeline. After that, nobody maps them by hand.

The details that break naive exports

A CSV export or a generic connector gets you most of the way and leaves the expensive part on your desk:

• Contact matching. Without a stable match on customer number and email, every order risks creating a fresh Debitor. Guest checkouts and buyers who changed their email are the usual culprits, and a cluttered contact list is painful to unwind later.
• Tax type, not just tax rate. A 19 percent domestic sale, a 7 percent reduced-rate item, an EU distance sale under OSS, a B2B reverse-charge delivery, and an export to Switzerland are different tax types in sevDesk, not one rate you can hard-code. The destination country and the buyer’s status decide it.
• Invoice numbering. Shopware and sevDesk both want to assign invoice numbers. Decide which system owns the number range up front, or you get gaps, duplicates, and a tax advisor asking why two documents describe one sale.
• Credit notes reverse, not delete. A partial return has to become a sevDesk credit note that reverses the original invoice’s accounts and tax types on the return’s date - never an edit or a deletion of the original booking.
• The payout is not the revenue. PayPal, Stripe, Mollie, and Klarna settle net of fees, days later, in batches spanning many orders. The sale and the money arriving are separate events that have to reconcile against the right sevDesk cash account.
• Idempotency and delta. Re-running a naive export books a month twice. The pipeline tracks each Shopware order and document by a stable id and syncs only what actually changed, so a retry never produces a duplicate record.

How we build and run it

We treat this as a pipeline, not a nightly button someone presses. Order, document, and refund events are pulled from the Shopware Admin API on a schedule (or by webhook), validated, transformed into your agreed sevDesk coding, and written through the sevDesk API - contacts matched first, then the invoice or voucher, then the payment reconciliation, in the right order.

The pipeline is idempotent: every Shopware order and document carries a stable identifier, so a retry or a re-run never creates a duplicate contact, invoice, or booking. It runs on cloud-native, fully EU-hosted infrastructure, so order and customer data never leaves the EU - which keeps your DPA / AVV and your GDPR obligations clean.

Then we keep it running. Monitoring, alerting, incident response, and - critically - watching for Shopware and sevDesk API changes are our responsibility under contract. You get a named owner and an SLA, not a script that breaks quietly the next time an endpoint changes.

When this integration is worth building

If you process a handful of orders a month at a single domestic tax rate, sevDesk’s own import or a generic connector is genuinely fine, and we will tell you so. The integration earns its place when volume climbs, when you sell across EU borders under OSS, when returns and multiple payment providers turn reconciliation into a monthly chore, or when your tax advisor is charging you to clean up bookings that a pipeline should have delivered correctly the first time.