One integration layer.
Every carrier.
CEP One is the central middleware between SAP and your parcel carriers – standardized, secure and fully decoupled from the SAP core. Instead of integrating each carrier individually into SAP, you address every carrier at once through a single API endpoint and one unified data model.
The challenge of individual carrier integrations
Every carrier has its own APIs, data formats and requirements. That means significant development and maintenance effort — and that effort repeats with every single carrier you connect.
Divergent APIs
Every carrier has its own endpoints, authentication methods and data structures.
High Maintenance Effort
API changes by carriers require continuous adjustments in SAP.
Difficult Scaling
Adding new carriers means new development projects and long implementation times.
Ongoing Upkeep
Individual integrations must be maintained, updated and adapted whenever changes occur.
What actually changes with CEP One
Without CEP One
- A separate API, authentication and data structure for every carrier
- Every API change by a carrier triggers renewed development effort in SAP
- Every new carrier is its own integration project with a long lead time
- Maintenance costs grow with every additional point-to-point integration
With CEP One
- One data model, one central mapping for all connected carriers
- Changes to carrier interfaces are maintained centrally in CEP One — not in SAP
- Connect new carriers via standardized connectors in days instead of months
- Scales with shipping volume, no re-engineering under increased throughput
A standardized process for every carrier
No matter which carrier ultimately executes the shipment — four steps from the SAP request to the normalized response.
SAP sends the request
Your SAP system sends a standardized request to CEP One – always the same format, regardless of carrier.
CEP One maps & routes
CEP One transforms the data into the carrier-specific format and forwards it to the right provider.
Carrier processes it
The carrier creates the label, registers the shipment and sends back a confirmation.
Normalized response
CEP One normalizes the carrier's response and returns it to SAP in a unified format.
What CEP One delivers, concretely
Central Integration Layer
A unified data model and central mapping for all carriers. CEP One automatically translates SAP shipping orders into each carrier's specific format. Instead of maintaining a separate interface per carrier, you always speak the same format from within SAP — CEP One handles the translation completely and automatically.
Decoupling & Clean SAP Core
SAP and your parcel carriers are architecturally fully separated. No carrier-specific changes in the core — the SAP standard remains intact, low-maintenance and upgrade-ready. That also protects future SAP upgrades: your system stays close to standard, without individual carrier logic that would need re-checking with every release.
Security & Governance
CEP One consolidates all shipping communication between SAP and your connected carriers in one central place. That creates a single control point for authentication, data flow and traceability — instead of many scattered point-to-point connections that would each need to be secured and monitored individually.
Faster Implementation
Connect new carriers in days instead of months. Standardized connectors and predefined mappings eliminate recurring integration effort. That lets you tap into new markets or additional carriers on short notice, without setting up a dedicated development project every time.
Scalability & Performance
CEP One grows reliably with your shipping volume. No re-engineering under rising throughput – the platform carries whatever load your logistics generates. Whether seasonal peaks or sustained growth: the integration layer adapts without architecture or processes needing to be rebuilt.
Future-Proofing & Independence
Carriers change, markets evolve — CEP One stays the constant anchor. Less dependency on individual providers, more strategic flexibility. An additional market or a new contract partner can be mapped through CEP One without touching your SAP system or existing carrier connections.
Articles about the platform
CEP One Lösungspakete: API Solution vs. SAP Full Solution
API Solution oder SAP Full Solution: die zwei Lösungspakete von CEP One im Vergleich – Umfang, Abrechnungsmodell und Verfügbarkeit im Überblick.
Weiterlesen →
CEP One: Technologie-Basis mit SAP BTP und Integration Suite
CEP One läuft auf SAP BTP und der SAP Integration Suite – so ist die Integrationsschicht technisch aufgebaut und mit dem SAP-System verbunden.
Weiterlesen →
Glossar: Was ist die zentrale Integrationsschicht von CEP One?
Ein Erklärartikel darüber, wie die zentrale Integrationsschicht von SAP CEP One als Middleware zwischen SAP-System und KEP-Dienstleistern funktioniert und warum sie den SAP-Core vom Carrier-Netzwerk entkoppelt.
Weiterlesen →
POST /api/v1/shipment
{
"carrier": "DHL",
"weight": 2.5,
"address": {...}
}POST /api/v1/shipment
{
"carrier": "DPD",
"weight": 2.5,
"address": {...}
}SAP integration in detail
Our SAP add-on delivers seamless integration of all relevant functions directly into SAP ECC, SAP S/4HANA or SAP EWM — from automated data retrieval to the tracking number that's written back into SAP automatically.
All carrier-specific mapping stays entirely within CEP One — your SAP standard remains low-maintenance and upgrade-ready.
FAQ about the platform
CEP One is a central integration layer (middleware) between your SAP system and your parcel carriers. Instead of connecting each carrier individually in SAP, you address every parcel service through a single API endpoint and one unified data model. CEP One automatically translates your SAP shipping orders into each carrier's specific format.
National and international parcel carriers are reachable through a single endpoint — including DHL, UPS, DPD, FedEx, GLS, Hermes, DB Schenker, GO!, Dachser, Kühne+Nagel and many more. New carriers can be connected via standardized connectors in days rather than months.
In four steps: (1) SAP sends a standardized request to CEP One, (2) CEP One maps and routes the data into the carrier-specific format, (3) the carrier creates the label, registers the shipment and confirms it, (4) CEP One normalizes the response and returns it to SAP in a unified format — including tracking numbers and tracking data.
Because carriers are connected centrally through CEP One, you stay less dependent on any single provider. You can switch carriers or enter new markets without rebuilding your SAP system — and the platform scales with rising shipping volume without re-engineering.
CEP One is built on the SAP Business Technology Platform (SAP BTP) with SAP Integration Suite — SAP's strategic integration platform. That means CEP One runs on the most robust, future-proof integration layer available in the SAP ecosystem: cloud-native and highly available.
Ready for a central integration layer?
Let's discuss how CEP One can standardize your SAP shipping processes — no obligation, tailored to you.