In most companies the ERP or merchandise management system is the source of truth — and therefore the most demanding connection point. This category covers linking such systems to the online shop: available interfaces and export formats, mapping customer master data and individual terms, handing over orders and reporting back status and shipping information, dealing with number ranges, tax codes and payment terms. We look at the specifics of large standard systems as well as smaller solutions common in mid-sized businesses, and describe how to build test environments. The goal is integrations that run stably in daily business and stay traceable when something does not arrive. We additionally look at test operations: which records belong in an acceptance test and how a synchronisation run can be repeated safely.
On this page you will find all posts on the topic “ERP & merchandise management”. The newest posts are at the top.
Below each title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you also see the other topics. At the bottom, a link takes you back to all posts.
Black Week 2026: prepare the order flow between shop and ERP – measure the backlog, move night jobs, add a queue with alerts, freeze changes, define a fallback.
Read the payment terms code from the ERP, show it as a date at checkout, settle the early payment discount only on receipt and check the statutory limit on payment periods.
Counting method, freeze window and number ranges at year-end: how to prepare the interface between shop and ERP for the balance sheet date without downtime.
How shop orders become vouchers and shop products become master data in Lexware Office: field mapping, the limits of the interface and the pace it demands.
Batches belong to the movement, serial numbers to the single unit: data model, EU traceability rules, GS1 application identifiers and the recall as the test.
Feature axes, the variant matrix and article number logic: how colour, size and version in the ERP become a solid variant structure in the shop, with GS1 rules.
Separate base, stock, selling and purchase units, pull conversion factors from the ERP, and map stock, minimum quantities and unit prices correctly.
Corporate groups running several ERP entities and one shop: item routing, number ranges, tax codes, stock aggregation and order splitting done properly.
Connect Dynamics 365 Finance to your online shop via OData entities and the Data Management Framework: sync items, prices and orders cleanly.
SAP ECC maintenance ends on 31 Dec 2027. Every ECC-coupled shop connector must move to S/4HANA. How to plan the migration path without shop downtime.
With Business Central 2026 Wave 1 (BC28), API v1.0 is removed. Migrate your shop connector to API v2.0 in time, before order and stock sync breaks.
Connect a shop to SAP clean-core: with the Integration Suite (Cloud Integration, API Management, Event Mesh) the link survives the S/4HANA cut in 2027.
Connect Dynamics 365 Business Central to your online shop: OData and AL APIs, OAuth2, item, price, inventory and order sync plus performance tips and pitfalls.