B2B Customer Access: ERP-Driven Assortments
Control released items, customer groups, blocked products and login rules from the ERP in the B2B shop: visibility and assortments in real time or cache.
This is page 8 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.
Control released items, customer groups, blocked products and login rules from the ERP in the B2B shop: visibility and assortments in real time or cache.
Digital Product Passport from 2027: aggregate material, repair and origin data per ESPR from ERP and PIM and provide it DPP-compliant via QR code and API.
Connect SAP and Shopware: real-time synchronization of master data, inventory and pricing via the Service Layer API with middleware architecture.
DATEV connection for online stores: automatically transfer invoices, credit notes and payments. Posting batches, XML documents and API integration.
REST API or middleware for shop integration: advantages and disadvantages of both architecture models compared with concrete decision criteria.
Synchronize JTL-Wawi with your shop without duplicates or stock discrepancies: plan data objects, sync direction and the leading system (master) properly.
Data mapping between ERP and store system: field assignment, data transformation, validation rules and mapping strategies for successful integrations.
Inventory synchronization across multiple warehouses: real-time availability in B2B stores through delta sync, multi-warehouse logic and intelligent routing.
Many ERP-to-shop APIs still run on static keys. How the client credentials flow, mTLS, DPoP, short token lifetimes and scope minimization harden the API.