Connecting Lexware Office to the shop: vouchers and items
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.
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.
From 30 December 2026 every consignment needs a due diligence statement. Which fields the ERP has to carry and how the reference number reaches customs.
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.
Absorb an ERP outage: last valid stock and prices with an age stamp, buffered orders, conservative checkout rules and an orderly, deduplicated restart.
Why nightly catalogue and price imports fail on cloud ERP rate limits and how batching, concurrency control and Retry-After handling secure the data transfer.
Connect Dynamics 365 Finance to your online shop via OData entities and the Data Management Framework: sync items, prices and orders cleanly.