# Shopware integrations

*3 integrations*

**In short:** A Shopware integration takes orders and the invoice and credit-note documents Shopware generates, and turns them into records in an ERP such as SAP Business One or in accounting such as DATEV or sevDesk, with item, price, and stock data flowing back. It breaks on booking the editable order instead of the invoice document, tax keys copied from rates, number ranges claimed twice, and several sales channels and currencies in one instance.

## What connects to Shopware

Shopware is a widely used shop system in Germany, and a single instance often runs several sales channels and currencies at once. It knows the basket, the customer and their billing country, the payment method, and the shipping, and it generates invoice and credit-note documents itself.

That puts Shopware upstream of two kinds of systems. An ERP receives orders as sales documents against the right business partner and items, and sends item master data, price lists, and warehouse stock back, as in [Shopware to SAP Business One](https://seamless.engineering/integrations/shopware-sap-business-one/). Accounting receives the documents as bookings, either straight into the Kanzlei's DATEV, as in [Shopware to DATEV](https://seamless.engineering/integrations/shopware-datev/), or into an accounting tool first, as in [Shopware to sevDesk](https://seamless.engineering/integrations/shopware-sevdesk/).

## Where Shopware integrations break

- **The order is not the audit record.** A Shopware order can be edited after the fact; the invoice document it generated carries the sequential Belegnummer. Book the order instead and the number range gets gaps your tax advisor will flag.
- **Cancellation and credit note are different documents.** Shopware treats them as distinct document types, and each needs its own booking logic. A partial credit note reverses the original's accounts and tax treatment on its own date, and never edits or deletes the original.
- **Shopware stores tax amounts, not tax keys.** It records the calculated tax and the customer country. The DATEV tax key, the sevDesk tax type, or the SAP tax code has to be derived from both, not copied from the percentage.
- **Two systems want the number range.** Shopware and the accounting side both assign invoice numbers. Decide the owner up front, and never force a document number into SAP.
- **One instance, many channels and currencies.** Each sales channel may post to its own revenue account or cost centre, and foreign-currency orders need a defined conversion and rounding rule so the batch balances.

## All Shopware integrations

### E-commerce → Accounting

- [Shopware ↔ DATEV](https://seamless.engineering/integrations/shopware-datev/): Shopware DATEV integration
- [Shopware ↔ sevDesk](https://seamless.engineering/integrations/shopware-sevdesk/): Shopware sevDesk integration

### E-commerce → ERP

- [Shopware ↔ SAP Business One](https://seamless.engineering/integrations/shopware-sap-business-one/): Shopware SAP Business One integration

## Common errors

- [Shopware 6: The provided value is not a valid](https://seamless.engineering/errors/shopware-provided-value-not-valid/)

## Request a scoping call

Connecting Shopware to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.

- Email: hello@seamless.engineering
- Contact form: https://seamless.engineering/#contact