Customer Part Numbers Searchable in the B2B Shop
Making customer part numbers from the ERP searchable in a B2B shop: data model, BMEcat elements, tenant permissions and the return path into the e-invoice.
This is page 3 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
Making customer part numbers from the ERP searchable in a B2B shop: data model, BMEcat elements, tenant permissions and the return path into the e-invoice.
On 27 September 2026 provisional importing without authorisation runs out. Which import data the ERP has to carry, and how the 50-tonne total adds up.
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.