The real work sits between the shop and the back office: articles, prices, stock levels, customers, orders, delivery notes and invoices have to flow reliably in both directions. This category collects articles on connecting these systems — from taking stock of existing data sources through choosing the leading system per data type to synchronisation methods, error handling, logging and recovery after incidents. We cover product data quality and classifications, variants and bills of materials, partial deliveries, returns and credit notes, and how to handle the special cases no standard solution anticipates. Written so that business departments and IT speak the same language and effort can be estimated realistically in advance. We also cover project organisation: who decides when systems conflict, and how are data flows documented so they remain understandable in two years?
On this page you will find all posts on the topic “Shop integration & processes”. 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.
DATEV discontinues its Rechnungsdatenservice 2.0 on 31 Dec 2026. How shops and ERP connectors check whether they are affected and move their document route.
What does connecting an ERP to your online shop cost? Six cost drivers, recurring items, 2027 deadlines and a budget frame per integration type for planning.
Shop or ERP: which system issues the invoice and assigns the number? A decision matrix for partial delivery, cancellations, marketplaces and e-invoicing.
Transferring hazard fields from section 14 of the safety data sheet into the shop: field list, quantity totals in the cart, labelling in the offer and handover to the shipping interface.
On changeover night one hour occurs twice. How timestamps, delta queries and job schedules between shop and ERP stay unambiguous, plus a test plan for October.
Blanket orders and call-offs between shop, middleware and ERP: data model, remaining quantity, contract price, contract term and the way into the document.
Partial deliveries and part invoices between shop, middleware and ERP: data model, open quantity, document references and the fields of the electronic invoice.
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.
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.
Bidirectional ERP-shop sync creates data conflicts. Field ownership per data category instead of last-write-wins prevents overwritten stock and sync loops.
Show picking, partial delivery and invoice status live from your ERP in the B2B customer account: build the status return channel without a new data silo.
Sync orders, business customers, revenue and leads from the shop into your CRM automatically: with field mapping, duplicate protection and segment triggers.
POS and online shop share one inventory and one customer history: click and collect, in-store returns and no overselling. Omnichannel done right for B2B.
iPaaS or custom development for ERP-shop coupling: a build-or-buy guide to total cost, data sovereignty, lock-in and time to go-live with clear decision criteria.
Sandbox tenants, anonymised test data and contract tests: how to test ERP shop interfaces safely before go-live instead of flying blind into production.
Automate drop shipping cleanly: read supplier feeds via EDI, CSV/SFTP or REST API, mirror availability and split orders by supplier – with the ERP leading.
Manage return requests, RMA numbers, inspection, restocking and credit notes bidirectionally between shop and ERP – without double entry of returns.
Check credit limit, open items and payment terms in real time from SAP, Dynamics or DATEV in the B2B checkout to control invoice purchase and order release.
OCI and cXML Punchout connect your B2B shop to SAP purchasing and e-procurement: HTTP session handoff, cart return, customer-specific catalogues and prices.
Observability for ERP-store interfaces: logs, metrics and traces make sync errors visible before customers notice. Early detection instead of damage control.
API versioning for shop interfaces: URI and header strategies, deprecation processes and backward compatibility for maintainable, long-lasting integrations.
Master data management 2026: synchronize customers, products and prices across ERP, shop and CRM, resolve conflicts rule-based and secure data quality.
Payment reconciliation in e-commerce: automatically match payouts, orders and invoices, post fees and chargebacks, hand over cleanly to DATEV and your ERP.
Connect shop and ERP to marketplaces through middleware: synchronise listing, order, stock and price, with mapping per channel and clear status in practice.
Connect carrier APIs for label, tracking and returns to your shop: multi-carrier selection, webhook tracking, returns handling and warehouse sync in practice.
Build PIM integration: a product data pipeline from PIM through enrichment to store, marketplace and print – with channel mapping, delta sync and API design.
Couple EDIFACT messages such as ORDERS, INVOIC and DESADV between trading partners and your shop: converter, AS2, SFTP, mapping and receipts in practice.
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.
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.
ERP migration from legacy interfaces to modern API connections: strangler fig pattern, risk analysis and gradual replacement of old integrations.
Customer-specific prices from SAP or Dynamics in B2B shops: synchronisation strategies, caching architectures, tiered price mapping and validity periods.
Error handling in shop interfaces: retry logic with exponential backoff, dead letter queues, circuit breakers and monitoring that reports before customers do.