Skip to content
SAP, DATEV and Dynamics experts

Blog — Page 4

SAP - Shopware Real-Time SynchronizationSAP Business OneService Layer API (OData)Master Data, Prices, InventoryShopwareStore API / Admin APIProducts, Orders, CustomersMiddlewareTransformation, Validation, QueueEvent-based, bidirectionalData FlowsItem Master DataSAP leads, Delta SyncInventory LevelsReal-time Push, Multi-WarehousePrice ListsCustomer-specific, TieredOrdersShop leads, Real-timeChange Tracking (SAP)TimestampsChange LogEvent WebhookOnly changed records transferredError HandlingRetry QueueDead LetterAlertingAutomatic retry, escalationSynchronization IntervalsOrders: Real-timeInventory: every 2 minPrices: every 15 minMaster Data: Delta 5 min

SAP and Shopware: Real-Time Synchronization of Master Data

Connect SAP and Shopware: real-time synchronization of master data, inventory and pricing via the Service Layer API with middleware architecture.

13 min read
DATEV Connection in E-CommerceOnline StoreOrders, Invoices, ReturnsShopware / Open Source / CustomDATEVFinancial AccountingPosting Batches, Documents, DMSMiddlewareMapping, Validation, ConversionDATEV Format ConversionAutomated Document FlowsInvoicesAutomatic ExportCredit NotesReturn DocumentsPaymentsMatching and AssignmentDebtorsAutomatic CreationDATEV Export FormatsPosting BatchCSV per DATEV SchemaXML DocumentOnline Document ExchangeDATEV APIREST, Real-time SyncDMS UploadArchive Document ImagesAccount AssignmentRevenue AcctsTax AccountsDebtor AccountsTax Rate Mapping19%7%0% (EU)RC

DATEV Connection in E-Commerce: Automated Accounting

DATEV connection for online stores: automatically transfer invoices, credit notes and payments. Posting batches, XML documents and API integration.

12 min read
Integration Architectures ComparedPoint-to-Point (REST API)StoreERPStoreDATEVDirect, fastLow abstractionMiddleware ArchitectureStoreERPDATEVPIMMiddlewareTransformationRoutingQueueDecision CriteriaNumber of Systems2 systems: API direct3+ systems: MiddlewareData VolumeLow: synchronous APIHigh: asynchronous queueMaintainabilityAPI: coupled to systemsMiddleware: decoupledTechnology OverviewRESTJSON, HTTP VerbsGraphQLFlexible QueriesODataSAP, DynamicsWebhooksEvent-basedMessage QueueAsync, robust

REST API or Middleware: Which Integration Architecture Fits

REST API or middleware for shop integration: advantages and disadvantages of both architecture models compared with concrete decision criteria.

11 min read
JTL-Wawi and Online Shop: Sync Direction per Data ObjectSet the leading system, plan the direction per object, resolve conflicts cleanlyJTL-WawiInventory systemLeading system(Master)> 50.000merchants run JTL-WawiOnline shopStorefront and checkoutOrders originate hereProducts and variantsPricesStock levelsOrdersCustomersPayment/shipping statusfrom JTL-Wawi (master)back into JTL-Wawibidirectional (status)

Connecting JTL-Wawi to Your Online Shop: Sync Strategy

Synchronize JTL-Wawi with your shop without duplicates or stock discrepancies: plan data objects, sync direction and the leading system (master) properly.

13 min read
Data Mapping: ERP to StoreERP System (Source Fields)ItemCodestring(20)ART-10042ItemNamestring(100)Bolts M8x40QuantityOnStockdecimal(18,3)1542.000PriceAfterDiscountdecimal(18,6)4.250000SalesUoMEntryint3 (= Ctn)Store System (Target Fields)productNumberstringART-10042nametranslatedBolts M8x40stockint1542price.grossfloat5.06 (gross)unit.namestringCarton1:1i18nroundtax+roundlookupMiddleware: Transformation, Validation, Enrichment1:1 MappingDirect assignmentwithout transformationType Conversiondecimal to intnet to grossLookup TablesUoM codes to namesTax keysValidationCheck required fieldsEnsure value rangesMapping Configuration: JSON/YAML-based, versioned, testableMapping changes without code deployment | Audit log for every transformation | Error protocol for invalid data

Data Mapping Between ERP and Store: Field Assignment Done Right

Data mapping between ERP and store system: field assignment, data transformation, validation rules and mapping strategies for successful integrations.

11 min read
Multi-Warehouse Inventory SynchronizationB2B Online StoreAggregated AvailabilityWarehouse NorthHamburg, 8,500 SKUsWarehouse CentralKassel, 12,000 SKUsWarehouse SouthMunich, 6,200 SKUsDropship PartnerExternal, API QueryMiddleware: Aggregation, Routing, Delta SyncInventory Rules | Reservations | Thresholds | Fallback LogicDelta SyncOnly transfer changes90% less data volumeEvent PushImmediate updateon every stock movementReservationsReserve stock on orderimmediatelyThresholdsSafety stockconfigurable per warehouseAvailability Display in StoreTotal Stock | Location Availability | Delivery Time per Region | Reorder Info

Inventory Synchronization Across Multiple Warehouses for B2B

Inventory synchronization across multiple warehouses: real-time availability in B2B stores through delta sync, multi-warehouse logic and intelligent routing.

10 min read
OAuth 2.0: bound, short-lived tokens for ERP APIsClient credentials flow, mTLS/DPoP and scope minimization instead of static keysShop clientMiddleware / connectorAuthorization ServerToken endpointClient credentials flowERP / Resource ServerSAP, Dynamics, ERP1. Request token3. Present token2. Issue access tokenAccess Tokenscope: orders:read (least privilege)exp: 5 minutes, short-livedcnf: mTLS certificate / DPoPsender-constrained (RFC 9700)Static API key vs. OAuth 2.0 tokenStatic API keyLifetime: unlimitedRevoke: only global rotationBinding: none, plain bearerScope: usually full accessOAuth 2.0 tokenLifetime: minutes, rotatingRevoke: per tokenBinding: mTLS or DPoPScope: narrow, per task
IT & API security May 11, 2026

OAuth 2.0 and Token Security for ERP Interfaces

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.

13 min read
ERP Migration: Legacy to APILegacy State (Before)CSV ExportDirect DB AccessFTP UploadBatch ScriptsManual, error-prone, not scalableModern State (After)REST APIEvent WebhooksMessage QueueMiddlewareAutomated, robust, scalableStrangler Fig Pattern: Gradual MigrationPhase 1: Master DataPhase 2: InventoryPhase 3: OrdersPhase 4: PricingParallel OperationOld and new active simultaneouslyComparison TestsVerify old vs. new resultsRollback OptionSwitch back to legacy anytimeRisk minimization through gradual replacement | No big bang | Each phase individually testable

ERP Migration: From Legacy Interfaces to Modern API Connections

ERP migration from legacy interfaces to modern API connections: strangler fig pattern, risk analysis and gradual replacement of old integrations.

14 min read
Customer-Specific Price SynchronizationERP Price Lists10 Price Lists, TiersFramework Agreements, SpecialsMiddlewarePrice MappingCaching LayerNet to Gross + TaxB2B StoreCustomer Group PricesPrice Rules, Tiered PricingPrice StructuresList PricesStandard price for allGroup PricesPer customer groupTiered PricesQuantity-dependentSpecial PricesTime-limitedCaching ArchitectureRedis CacheTTL per Price TypeCache InvalidationFallback StrategySync StrategiesFull sync: All prices periodicallyDelta sync: Only changesOn-demand: At customer loginHybrid: Combination by price typePerformance Metrics500,000 price recordsunder 50ms query time95% cache hit rateDelta sync every 15 minutes

Customer-Specific Prices from ERP: Synchronization and Caching

Customer-specific prices from SAP or Dynamics in B2B stores: synchronization strategies, caching architectures and tiered price mapping.

10 min read