Skip to content
SAP, DATEV and Dynamics experts

Blog — Page 2

OCI and cXML Punchout: Connect Procurement to the ShopProcurement SystemSAP purchasing / e-procurementPurchase requisition (PR)Approval workflowHTTP Session HandoffHOOK_URL / return URLSession ID + authenticationStructured cart returnedB2B ShopShopware CE + catalogueCustomer-specific catalogueContract prices live1 Setup2 Call4 Cart5 ApprovalThe Punchout Roundtrip in Five Steps1Setup RequestPass HOOK_URL2Session LoginAuth + open catalogue3Shop the CataloguePrices + tiers live4Cart ReturnedNEW_ITEM fields5Order (PO)Approval in systemOCI (SAP): HTML form fieldsCart return via form POSTNEW_ITEM-DESCRIPTION / -MATNRNEW_ITEM-QUANTITY / -UNITNEW_ITEM-PRICE / -CURRENCYNEW_ITEM-VENDORMAT / -LEADTIMEcXML: XML messagesDocument-based, server-to-server POPunchOutSetupRequest (create)PunchOutSetupResponse (StartPage)PunchOutOrderMessage (cart)OrderRequest (purchase order)B2B online trade via shops and marketplaces: about EUR 476 billion (Statista)95 percent simplify the ordering process digitally (Bitkom) - 80 percent see the biggest digitalization need in supplier management (BME)

OCI Punchout: Connect Procurement Portals to Your Shop

OCI and cXML Punchout connect your B2B shop to SAP purchasing and e-procurement: HTTP session handoff, cart return, customer-specific catalogues and prices.

13 min read
Migration from API v1.0 to API v2.0 - Shop ConnectorAPI v1.0 (BC28)removed 2026 Wave 1Multipart keysREST ConnectorOAuth2 tokenMapping + queueDelta syncAPI v2.0versioned, stableGUID + SystemIdDeadline BC28April 2026Synced data - risk once v1.0 is switched offOrdersReal-time pushShop is sourceItems + stockDelta via v2.0BC is sourcePrices + variantsTiers, imagesBC is sourceNew 2026 connector featuresVariant imagessynced per variantItem attributesup to 3 optionsCheckout currencyexact multi-currencyMigration roadmap1. Auditfind v1.0 calls2. Rebuildmap GUID + fields3. Testrun in parallel4. Cut overbefore BC28

Dynamics 365 BC: API v2.0 - Save the Shop Connector 2026

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.

13 min read
E-Invoice: Data Flow and Mandate TimelineData flow per invoiceERP / ShopInvoice datafrom every orderZUGFeRD /XRechnungPDF + XMLEN 16931 compliantGoBD Archiveaudit-proof10-year retentionDATEVAccountingExport to tax advisorE-invoice mandate timeline01.01.20252025Receipt obligationAll companies must beable to receivee-invoices01.01.20272027Sending obligationTurnover above800,000 € prior year:e-invoice required01.01.20282028All B2B invoicesSending obligation forall domesticB2B invoices
Law & compliance Jul 1, 2026

E-Invoice Mandate 2027: ERP Shop Interface

E-invoice mandate 2027 for B2B merchants above 800,000 euro: generate ZUGFeRD and XRechnung from shop order data and hand them to DATEV, GoBD-compliant.

13 min read
SAP Integration Suite: Clean-Core Shop ConnectionFrom the deprecated PI/PO connector to the BTP platform layerLegacy: point-to-point (PI/PO)SAP ECCsupport ends 2027PI/POdeprecatedShopZ-code couplingbreaks at the S/4HANA cutClean core: BTP platform layerS/4HANAOData / eventsIntegration SuiteBTPShopstandard APIupgrade-safe, no core modificationconnection survives the migration cutThree BTP building blocks for shop integration1Cloud IntegrationiFlows, mapping,transformation2API ManagementSecure REST/ODataAPIs, quotas, keys3Event MeshReal-time events,async, scalableEvent-driven data flow in real timeS/4HANAevent sourceIntegration SuiteEvent Mesh / iFlowShopreal-time dataCustomer dataArticle dataStockOrders

SAP Integration Suite: Clean-Core Shop Link 2026

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.

13 min read
Observability Dashboard for InterfacesSync Success Rate99.4%last 24 hoursError Rate (Trend)Anomaly detected at 2:20 PMActive AlertsSAP latency elevatedQueue depth risingDLQ: 2 messagesThree Pillars of ObservabilityLogsStructured eventswith correlation IDJSON, searchableMetricsError rate, latencyQueue depth, throughputThreshold alertsTracesPath of an orderstore to ERPspan per stepEarly detection: see errors before customers doStore ordersMiddleware checksAlert on anomalyFix before customer impact

Observability for Interfaces: Detect Errors Early

Observability for ERP-store interfaces: logs, metrics and traces make sync errors visible before customers notice. Early detection instead of damage control.

12 min read
Event-Driven Architecture with a Message QueueEvent SourcesShop: orderShop: paymentERP: stockMessage Broker / Queuedecouples source and target1234Order per partition (FIFO)ACK / CommitRetry + BackoffConsumersERP orderAccountingWarehouse syncpublishsubscribeDelivery ResilienceAt-least-onceIdempotency keyOrder preservedLoad bufferFailure PathDead Letter Queueafter retries exhaustedAlerting + replayno silent data lossMarket Dynamics17.6%queue market growth p.a.90%large firms real-time 202513%mature EDA adoption

Event-Driven Architecture and Message Queues

How events and message queues enable decoupled, resilient shop integrations: retry, partitioned ordering, idempotency and the dead letter queue explained.

14 min read
API Versioning: Lifecycle of an Interfacev1 activev1 deprecatedv1 sunsetv2 releaseshutdownv2 active (parallel to migration phase)Versioning StrategiesURI Versioning/api/v2/ordersVisible, cacheableHeader VersioningAccept: v=2026-06Clean URLsDate Versioning2026-06-22Per-client pinningDeprecation Signals for ConsumersDeprecation headerSunset dateChangelogMigration guide

API Versioning: Keeping Interfaces Long-Lasting

API versioning for shop interfaces: URI and header strategies, deprecation processes and backward compatibility for maintainable, long-lasting integrations.

12 min read
Master Data Management: one Golden Record for all systemsGolden RecordCustomer 100482 . Item SKU-7710Single Source of TruthERPSAP . Dynamics . DATEVShopShopware CE . PIMCRMSales . ServicesyncsyncConflict resolution (survivorship rule)Address: ERP wins . Stock: WMS winsPrice: ERP . E-mail: CRM (latest timestamp)on a tie -> review queue instead of overwriteData quality score94 %Complete . unique . deduplicated . validData governance: ownership, validation, audit trail per attributePoor data quality costs organizations USD 12.9m per year on average (Gartner)76 % of German companies struggle with data quality and silos (Bitkom, 2025)

Master Data Synchronization: Master Data Management 2026

Master data management 2026: synchronize customers, products and prices across ERP, shop and CRM, resolve conflicts rule-based and secure data quality.

13 min read
Payment Reconciliation: Matching Payments with the ERPPayouts (Provider)Orders (Shop)Invoices (ERP)PO-2026-0481 48.90 EURSO-100481 50.40 EURINV-50481 50.40 EURmatchedPO-2026-0482 118.20 EURSO-100482 120.00 EURINV-50482 120.00 EURFee -1.80 EURPO-2026-0483 64.00 EURno matchopen / exceptionunmatched -> exception listReconciliation EngineAmount + ReferenceFee SplitChargeback RulePost to ERPAuto-match rate94 %Manual effort only remains for residual itemsChargebacks cost USD 33.79bn (Juniper Research, 2025)

Payment Reconciliation: Match Payments with the ERP

Payment reconciliation in e-commerce: automatically match payouts, orders and invoices, post fees and chargebacks, hand over cleanly to DATEV and your ERP.

12 min read