Latest posts Visit blog
In plain words: what is this page about?

Many online sellers look for one program that runs stock, orders and bills. When you choose it, one point matters most. The program must work well with your shop and other services. These include sales sites, shipping, payment and your tax advisor. We list the questions to ask each vendor. We also show how to test it with real orders. Ask us if you want help with the choice.

In ERP selection for online retailers, the deciding factor is rarely the screen that shines in the demo. What matters is how orders, stock levels, prices, shipments, payments and documents flow between the ERP, the online store, marketplaces, shipping and accounting. If you write these flows down before the first demo and measure every vendor against them, you compare systems by what holds up in daily work. This guide shows how to build an interface map, which questions to put to vendors, which deadlines from e-invoicing, record retention and the Data Act affect the choice, and how a test run with real data backs up the decision.

Why interfaces decide the ERP selection

ERP software is common in retail, but far from universal. In 2025, 53.8% of EU wholesale and retail companies with at least 10 employees used ERP software (Eurostat); across all sectors covered, the figure was 46.45% (Eurostat). If software for customer relationships and business intelligence is added, 53% of companies used at least one of these applications (Eurostat). Company size makes a big difference: 41% of small companies with 10 to 49 employees used an ERP, compared with 89% of large companies with 250 or more employees (Eurostat). Many online retailers are therefore right at the point where spreadsheets, the store back end and an accounting program are no longer enough and an ERP is supposed to bring the data together.

In online retail, an ERP does not stand on its own. Orders arrive from the online store and from marketplaces, stock levels and prices go back out, carriers return tracking numbers, payment providers report incoming payments and refunds, and at the end of the month the tax advisor expects documents and bookings. Each of these flows is an interface. If one of them works only halfway, this rarely shows in the demo. It shows on a sales day, when many orders come in within a short time and the stock level in the store lags behind the warehouse.

That is why it pays to reverse the usual order: describe the data flows first, then invite vendors. If you start with a feature list, you get answers such as “interface available”. If you start with the map, you ask about the specific path of an order with a voucher, a partial delivery and a return, and you get an answer you can test. There are separate tools for the requirements specification and the formal vendor comparison; how to structure a requirements specification for a store project is covered in a separate article. This article is about the part that many selection processes treat too briefly.

Use the sales weeks as a test case

The weeks around Black Friday and Cyber Monday provide particularly useful test cases for a later ERP selection: Which orders had to be fixed by hand, where was the stock level wrong, which voucher ended up wrong in accounting? If you note these cases with their order numbers, you will have a test catalog made of real data in the new year. Moving to a new system in the middle of the holiday season, on the other hand, is usually not a good idea.

The interface map: record the data flows before the demo

The map is a simple overview: Which systems are involved, which data flows between them, in which direction, how often, and which system leads for a given data object? The value is maintained in the leading system, and all other systems take it over. A price that is maintained both in the ERP and in the store exists in two versions after a few weeks, and nobody knows which one applies. The following table shows a typical split, which may differ in your own business.

Data objectLeading system (typical)DirectionFrequency in daily work
Products and variantsERP or PIMto the store and marketplaceson change
Prices and customer pricesERPto the store and marketplaceson change, bundled before sales
StockERP or warehouse systemto all sales channelspromptly, more often on sales days
OrdersStore or marketplacefrom the channel to the ERPper order
Shipments and trackingCarrierto the ERP and back to the channelper parcel
Payments and refundsPayment providerfrom the provider to the ERPper event or daily
Invoices and credit notesERPto the customer and to accountingper document
BookingsERP or accountingto the tax advisormonthly or more often

The exceptions belong on the map too, because that is where most integrations fail: partial deliveries, cancellations after shipping, vouchers across several orders, sets made of several stock items, returns with compensation for loss of value and orders with a different delivery address. Each exception gets a row with a real order number from your own store. This list later becomes the test catalog for every vendor. If you take product attributes from manufacturer documents first, add that flow to the map as well; how to extract datasheets with AI and turn them into product attributes is shown in an article from this week.

  • Data object and fields: which fields are really needed, with length and character set
  • Direction and leading system: who writes, who reads and who wins in case of conflict
  • Trigger and frequency: event, scheduled polling or file transfer, and at what interval
  • Volume on the peak day: orders and stock changes per hour on the busiest day of the year
  • Error path: where a rejected record goes and who notices it
  • Ownership: who in the company is responsible for the connection on the business side

Store integration: orders, stock and prices

The path between the store and the ERP carries the most records. In the selection, what counts is not whether a vendor names a connector for a store system, but what that connector does with a difficult order. Three questions separate the options quickly: Do discounts, vouchers and shipping costs arrive in the ERP in a way that makes the invoice match the store to the cent? Are stock levels reported after every warehouse movement or at fixed intervals? And what happens if the ERP cannot be reached for a few minutes: Are orders lost, are they created twice, or do they wait in an orderly queue until the connection is back?

Modern store systems report events via webhook, older integrations poll at intervals. Both can work. What matters is that every order arrives exactly once, even if a message is delivered more than once. How an event-driven store integration with webhooks is built and why every message needs a unique identifier is covered in a separate article. The same applies to stock in the other direction: an ERP that publishes stock only at long intervals sells goods on a sales day that are long gone. The consequences of overselling are described in the article on real-time inventory sync between ERP, store and marketplaces.

One technical detail is worth asking about. Many programming interfaces limit how many requests a system may send within a period of time. If the limit is exceeded, the server usually answers with status code 429 (RFC 6585). A good connector then waits and tries again; a weak one gives up and reports nothing. So ask about the limits of the interface and about how the connector reacts to this response. For Shopware stores, we usually check this as part of the job when we take over or rebuild an existing integration as a Shopware agency.

Marketplaces: their own rules per channel

For many retailers, the marketplace is not a side channel. 56.7% of online sales in Germany went through online marketplaces in 2025 (HDE). In the EU, among companies with 10 or more employees that sell via the web, 45% sold through an online marketplace and 85.65% through their own websites or apps in 2024 (Eurostat). If you run only one store today, check during the ERP selection whether a second or third channel can be added later without rebuilding.

Marketplaces bring their own identifiers: an order number of the channel, their own product identifiers, their own shipping and return rules, fees per sale and bundled payouts. An ERP has to store these identifiers next to its own order number; otherwise a query from the marketplace can no longer be matched. Booking the payout is just as important: the marketplace does not pay per order, but in bundles and minus fees. Without matching at order level, accounting is left with a difference that someone has to resolve by hand. Which channels we connect to store and ERP is shown in the overview of marketplace integrations.

One stock level for all channels

If a retailer sells the same item in the store and on two marketplaces, it needs one stock level that all channels read from, plus a rule for the last units. Whether the ERP supports reservations per channel or safety stock belongs in the test run, not in a verbal promise.

Accounting and DATEV: what the tax advisor needs

Every order ends in a booking. Many online retailers hand their data over to a tax advisor who works with DATEV. For the ERP selection, this means that documents, customer accounts and bookings must come out in a form the tax advisor can take over without rework. How a DATEV integration in e-commerce is built is described in a separate article. For the selection, one question to the tax advisor is enough at first: In what form and at what frequency do they want the data?

Record retention matters as well. Books and records must be kept for ten years, accounting documents for eight years and other documents relevant for tax purposes for six years (Section 147(3) AO). If the records were created with a data processing system, the tax authority may inspect the data during a tax audit or request it in a machine-evaluable format (Section 147(6) AO). For a change of ERP, the same subsection contains a relief: if no tax audit has started yet, it is sufficient after the end of the fifth calendar year following the changeover to keep the data on a machine-readable and machine-evaluable data carrier (Section 147(6) AO). For the years before that, the selection should clarify how the old data can still be inspected and evaluated, for example through read access to the old system or a complete export.

The selection therefore includes a question that is rarely asked in demos: How does the data get out again? A complete export of all documents, bookings and master data in a documented format matters not only for a tax audit, but also for the next change of system. How we connect the handover to the tax advisor technically is shown on the page on the DATEV integration.

E-invoicing: the ERP must handle structured invoices

For supplies between businesses in Germany, the electronic invoice is the standard case: it is issued in a structured format that complies with the European standard on electronic invoicing (EN 16931) or is interoperable with it (Section 14 UStG). Relief applies during the transition period. For sales in 2027, only companies whose total turnover in the previous year did not exceed €800,000 may still send invoices on paper or in another electronic format (Section 27(38) UStG). Until the end of 2027, exchange via EDI also remains permitted with the recipient’s consent. After that, this relief expires.

This leads to a clear test question for the ERP selection: Does the system create invoices and credit notes as XRechnung or ZUGFeRD, and can it read and check incoming e-invoices and assign them to the right transaction? If you supply business customers with their own requirements, also ask about the customer’s order number, a different billing address and the routing ID (Leitweg-ID) for public-sector buyers. What distinguishes ZUGFeRD from XRechnung and how we implement both formats is explained on the page on ZUGFeRD and XRechnung.

If you create invoices in the store today, you also need to clarify where the invoice will be created in the future: in the store, in the ERP or in a separate service. Two number ranges for the same invoice are a typical source of errors when changing ERPs. How invoices in Shopware can be prepared for the new document generation is shown in the article on document generation v2 in Shopware; for down payments in B2B, there is a separate article on the advance payment invoice at the turn of the year.

Shipping, payments and selling abroad

Shipping: In many businesses, the ERP creates the shipping label or hands the shipment over to a shipping system. What comes back is the tracking number and delivery status, which the store should show to the customer. Check whether the ERP handles several parcels per order, several carriers and return labels. Incorrect addresses show up at this step, but they are created in the checkout; how to design address fields to avoid delivery errors is described in an article from this week. Our integrations with parcel carriers are presented on the page on shipping integrations.

Payments: Payment providers report incoming payment, partial refund, chargeback and payout each as a separate event. The ERP must assign each of them to the right order, even if a refund arrives weeks later. The more payment methods a store offers, the more important automatic matching becomes, because otherwise open items remain that have long been paid.

Abroad: For retailers established in only one EU country, the following applies: if distance sales to private customers in other EU countries, together with certain services, exceed €10,000 in the previous year or the current year, tax is due in the country of destination (Section 3c(4) UStG). The ERP must then know the tax rates of the destination countries, apply them correctly on each invoice and evaluate sales per country. Ask how tax rates are maintained and who updates them when a country changes its rate.

Test questions for every vendor

With the map in hand, vendors can be questioned on equal terms. The following questions target the interface itself, not the range of ERP features:

  1. Is the interface documentation public or fully available before signing, and does it describe fields, mandatory data and error codes?
  2. Is there a test environment with its own credentials in which real orders can be run through without touching live operations?
  3. How is the interface versioned, and how far in advance does the vendor announce changes that break existing integrations?
  4. Which request limits apply, and how does the connector behave when they are reached?
  5. Does the ERP report changes as events, or do other systems have to poll regularly?
  6. Can custom fields be created and read and written via the interface without an update overwriting them?
  7. Where do rejected records end up, who is notified, and can a record be sent again after correction?
  8. Is there a complete export of all data in a documented format, even after the contract ends?

The answers belong in the offer in writing. A promise in the demo helps little in a dispute; a described service in the contract does. If an ERP lacks an integration, that need not rule it out: an integration layer between the systems can translate data, buffer it and collect errors. When this pays off and why many direct point-to-point connections become hard to maintain over time is described in the article on middleware in e-commerce.

EDI in business with corporate customers

If you sell to business customers, ask one more question: Can the ERP exchange orders and invoices via EDI? In 2024, 17.99% of EU companies with 10 or more employees received electronic orders only via websites or apps, 2.9% only via EDI and 2.7% through both channels (Eurostat). Measured by turnover, EDI was nevertheless the larger channel: 11.07% of total turnover came from EDI messages and 8.39% from websites and apps (Eurostat). How orders get into the system automatically via EDI is described in the article on EDI integration in e-commerce.

Cloud ERP: negotiate the exit up front

ERP software can also be obtained as a service from the vendor’s data center. In Germany, 54% of companies with at least 10 employees used paid cloud services in 2025 (Destatis). ERP is still among the less common applications: of the companies that buy cloud services, 23% used ERP software from the cloud (Destatis).

For such services, the EU Data Act, Regulation (EU) 2023/2854, sets rules for switching providers that have applied since September 12, 2025 (Data Act, Art. 50). Among other things, the contract must state a notice period of no more than two months for initiating the switch (Data Act, Art. 25), a transition period of no more than 30 calendar days for transferring the data (Data Act, Art. 25) and a period of at least 30 calendar days during which the data can still be retrieved afterward (Data Act, Art. 25). If the transition period is technically not feasible, the provider may set up to seven months, with a justification (Data Act, Art. 25). From January 12, 2027, providers may no longer charge switching fees for carrying out the switch (Data Act, Art. 29).

The rules do not apply equally to every service. If most of the main features have been tailored to a single customer and the service is not offered through the provider’s general catalog, the rules on switching fees, among others, do not apply (Data Act, Art. 31). For the selection, this means: read the switching clauses before signing, ask for the list of exportable data and check in the test account whether the export is complete. The legal assessment belongs with your legal advisor.

Test the export, do not just accept a promise

An export that contains products and customers but no documents, bookings or change history helps neither in a tax audit nor in the next change of system. Ask for a complete export during the test run and open it yourself.

The test run with real data

At the end of the shortlist, there are usually two or three systems left. Before a contract is signed, a test run in the vendor’s test environment with data from your own business is worthwhile. It usually takes a few days and clarifies more than any demo. These steps have proven useful:

  1. Prepare data: a sample of products, customers and prices plus a selection of real orders from the last sales week with all the special cases you noted
  2. Import orders: through the store and marketplace integration, not through an import by the vendor
  3. Move stock: book goods receipt, ship orders, record a return and watch when the store shows the new stock level
  4. Create documents: create an invoice, a credit note and an e-invoice and check them against the rules for XRechnung or ZUGFeRD
  5. Hand over to the tax advisor: create a booking batch and have the tax advisor import it on a trial basis
  6. Simulate a failure: briefly cut the connection and check whether orders then arrive completely and exactly once
  7. Pull the export: export all data and check whether the stock level can be traced from it

Each step gets a result: passed, passed with rework or failed, each with the order number of the test case. These records later also serve as acceptance criteria for the implementation project. If you also want to move customer accounts from the ERP into a B2B store, you will find the steps in the article on how to onboard existing customers into the B2B store.

Schedule: selection and changeover outside the peak season

Introducing an ERP touches almost every process in the business. A sensible schedule places the changeover in a quiet phase and uses the peak season as a data source:

  • During the sales weeks: note special cases and failures with their order numbers
  • January and February: finish the interface map and test catalog, involve the tax advisor
  • Spring: shortlist, test run with two or three systems, decision
  • Summer: implementation, data migration and parallel operation with reconciliation
  • Fall: changeover completed before the holiday season starts

The duration depends on the number of channels, the quality of the data and the share of processes specific to your business. Deadlines such as the end of the e-invoicing transition rules or the end of switching fees for cloud services belong in this plan as fixed points.

How we support your ERP selection

In our consulting and concept work, we support the ERP selection from the interface side. Our recommendations are vendor-independent. We map the data flows between the store, marketplaces, shipping, payment and accounting, write the test questions, support the test run and then build the chosen integration.

Interface map

Recording of all data flows with the leading system, frequency and the special cases from your business.

Test run

Test cases from real orders, a record per step and an assessment of the connectors.

Integration

Implementation of the integrations with the store, marketplaces, shipping and DATEV after the decision.

Sources and studies

This article is based on Eurostat (news item “Larger enterprises used more e-business apps in 2025” of May 20, 2026, and the Statistics Explained articles “E-business integration” and “E-commerce statistics”), on the HDE Online Monitor 2026 of the German Retail Federation (press release of June 3, 2026), on the Federal Statistical Office of Germany (Destatis, press release no. 416 of November 24, 2025, and the table on cloud use by size class), on the German Fiscal Code (Section 147 AO) and the German VAT Act (Sections 3c, 14 and 27(38) UStG) as published on gesetze-im-internet.de, on Regulation (EU) 2023/2854 (Data Act) and on RFC 6585 of the IETF. All information retrieved on November 3, 2026. This article does not replace tax or legal advice.

Typically when stock, orders and documents are reconciled by hand across several programs, another sales channel is added or accounting regularly has to rework data. In the EU in 2025, 41% of small companies with 10 to 49 employees used ERP software, compared with 89% of large companies (Eurostat). There is no fixed size threshold; what matters is the effort at the handovers between systems.

Every demo shows features, but not the data flow on a sales day. Errors in the integration with the store, marketplace or accounting usually cost more time in daily work than a missing screen. If you describe the data flows first, you can measure vendors against specific cases.

An overview of all systems and data flows: which data flows, in which direction, how often and which system leads. Special cases such as partial deliveries or vouchers are added with real order numbers. The map is the basis for test questions and the test run.

For supplies to businesses in Germany, the e-invoice is the standard case (Section 14 UStG). For sales in 2027, only companies with a prior-year total turnover of no more than €800,000 may still use paper invoices; after that, this relief ends (Section 27(38) UStG). An ERP should therefore create XRechnung or ZUGFeRD and be able to process incoming e-invoices. Your tax advisor can clarify what applies to your business in detail.

Data relevant for tax purposes must remain evaluable, accounting documents for eight years and books for ten years (Section 147(3) AO). After the end of the fifth calendar year following the changeover, it is sufficient to keep the data on a machine-evaluable data carrier, provided no tax audit has started yet (Section 147(6) AO). Plan the export before the old system is switched off.

For such services, the Data Act requires, among other things, a notice period of no more than two months for the switch, a transition period of no more than 30 calendar days, or up to seven months where technically justified, and data retrieval of at least 30 calendar days (Data Act, Art. 25). From January 12, 2027, switching fees are no longer allowed; exceptions include services tailored to an individual customer (Data Act, Art. 29 and Art. 31). Read the switching clauses before signing.