Integrations in wholesale

In wholesale, the truth lives in the ERP: customer prices, discounts, framework contracts and delivery terms. A B2B shop has to show this data correctly for each customer, and orders have to get back into the ERP without retyping. Large customers often order by EDI. We connect ERP, shop and EDI directly, even when the pricing logic deviates from the standard.

Typical system landscape

The shop systems have B2B features: since version 6.7.8.0, Shopware offers the B2B component "Individual Pricing" with rule-based prices and discounts. According to the Shopify help center, Shopify B2B with company customers and catalogs is available on the Basic, Grow, Advanced and Plus plans. The prices themselves, however, usually come from the ERP and have to be translated into these structures.

Typical data flows

1. Customer prices and discounts are transferred hourly
2. Company customer is created with payment terms on change
3. Availability is reported every 15 minutes
4. Order is taken over from the shop, status is reported back on receipt

1. Order (ORDERS) is created as a sales order on receipt
2. Dispatch advice (DESADV) is sent to the customer on dispatch
3. Invoice (INVOIC) is sent to the customer on invoicing

The intervals are examples and depend on your range and order volume. For EDI, according to the GS1 recommendation as ecosio describes it, every delivery refers to an order, is announced with a dispatch advice and leads to an invoice. Anyone who maps this chain cleanly avoids queries at the customer's goods receipt. If a message is missing or a reference does not match, the delivery ends up in clarification at the customer.

Typical problems

• Pricing logic

  Tiers, customer groups, promotional prices and framework contracts sit in the ERP in a structure that no shop knows one to one.

• Volume of prices

  Many customers times many products make for large price tables. The transfer has to run incrementally, not completely every time.

• EDI per customer

  Every large customer has its own requirements for format and mandatory fields. A standard module rarely covers them all.

• E-invoicing

  Receiving e-invoices has been mandatory since 1 January 2025. Sending becomes mandatory from 1 January 2027 for companies with more than €800,000 in prior-year revenue, and from 1 January 2028 for everyone, with transitional rules.

Examples of connections

• Shopware with Business Central: B2B shop to a Microsoft ERP
• Shopware with JTL-Wawi: orders, stock, products
• Business Central with DATEV: postings to your tax advisor
• ERP with a large customer's EDI system: orders in, dispatch advice and invoice out

What we build

We read the pricing logic from your ERP and transfer only what has changed. Orders from shop and EDI land in the ERP after validation, with a log and a notification on errors. We build EDI messages to your customers' specifications. We generate e-invoices in the XRechnung or ZUGFeRD format from your invoice data, see e-invoice integration. The code belongs to you, and the price is fixed in advance. More under shop-ERP integration.

Updated: 10/20/2026