SAP S/4HANA ↔ Salesforce ↔ DMS across 400+ sub-distributors
Six markets, one ERP, four DMS variants and a partner network that onboarded by email. We replaced point-to-point files with a governed event backbone and a partner API contract.
Client: Regional FMCG distributor (anonymized)
−60%
Partner onboarding time
−22%
Claim-cycle time
6
Markets on one contract
Challenge
Sub-distributor onboarding took 5–7 weeks: master data was rekeyed into SAP, Salesforce and the local DMS separately.
Claims and promotions reconciled monthly in spreadsheets; disputes ran past the payment cycle.
Six markets ran four DMS variants with no shared interface contract, so every fix was local.
Interface failures were discovered by distributors calling the call centre.
Approach
Two-week assessment: interface register, ownership map, and a ranked gap list across all six markets.
Canonical partner, product and price-condition models published as versioned contracts.
Solace event mesh for order, stock and claim events; SAP as system of record, Salesforce as system of engagement.
Idempotent partner onboarding API with schema validation, dead-letter replay and per-market routing.
Claim-settlement workflow instrumented end to end, with SLA dashboards owned by the commercial team.
Architecture
flowchart LR
P[Sub-distributor DMS] -->|REST + schema check| G[Partner API Gateway]
G --> Q{{Solace Event Mesh}}
Q --> S[SAP S/4HANA]
Q --> C[Salesforce]
Q --> L[(Postgres claim ledger)]
S -->|master data events| Q
Q --> D[DLQ + replay]
L --> B[Claims + SLA dashboards]
Event-mesh topology: SAP is the record system, Solace carries domain events, the partner gateway is the only door in.
Stack
SAP S/4HANA
Salesforce
Solace
Azure
Postgres
Bring the initiative that is stuck. We will tell you what we would do in the first two weeks.
Thirty minutes, an architect on the call, no deck. You leave with a position on sequencing and risk whether or not you hire us.