Every carrier, one connection
National and international carriers — all reachable through a single API endpoint. From classic parcel carriers to freight carriers for pallet and less-than-truckload shipping.
National & international parcel carriers
Every connected carrier runs through the same API endpoint — one contract, one technical standard, instead of a separate integration per provider.
National carriers
The established leaders for shipping within Germany — including same-day and evening delivery.
International carriers & post
Cross-border shipping with the major international players and national postal operators worldwide.
Also for freight carriers and cooperations
Neutral, anonymous shipping labels for pallet and less-than-truckload freight — including freight carriers and cooperations such as DACHSER, DSV and Kühne+Nagel. The same standardized process as classic carrier shipping, just for a different freight type.
Articles about the carrier network
Häufige Fragen zu CEP One: Wachstum, Abhängigkeit, Pakete
Vier Fragen von Logistik-IT-Entscheidern zu CEP One: Wachstum ohne Umbau, Abhängigkeit von Versanddienstleistern, Abrechnung und Verfügbarkeit der Pakete.
Weiterlesen →
CEP One: Alle Carrier über einen einzigen API-Endpunkt
Wie CEP One alle angebundenen Paketdienstleister über einen einzigen API-Endpunkt erreichbar macht, neue Carrier anbindet und Abhängigkeiten reduziert.
Weiterlesen →
CEP One und SAP: Sicherheit, Carrier-Wechsel und Tracking
Vier häufige technische Fragen zu CEP One im SAP-Umfeld: SAP-Core-Anpassung, Carrier-Wechsel, Sicherheit und Tracking-Rückfluss kompakt beantwortet.
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 →Breadth pays off operationally
One API endpoint for every carrier
Instead of maintaining a separate interface per provider, you talk to CEP One just once — we translate into the respective carrier API.
Switch carriers without touching SAP
Carrier mapping lives in CEP One, not in the SAP system. Add or switch providers without changing the SAP standard.
From parcels to freight, one process
Whether parcel or pallet — the same standardized workflow, the same integration, no special path for other freight types.
FAQ about our carrier network
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.
No. The SAP backend always sends the same standardized data structure to CEP One — regardless of which carrier ultimately handles the shipment. CEP One takes care of all carrier-specific mapping. For you, that means one data model, one request format, one unified process in SAP — whether it's DHL, UPS, DPD or any other provider.
Changes to carrier interfaces are maintained centrally in CEP One and never affect your SAP system. That eliminates the recurring development and maintenance effort that individual point-to-point integrations would otherwise require.
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.
New carriers in days, not months
Standardized connectors and predefined mappings eliminate recurring integration effort.