How CONTAX SAP shipping add-on (with nShift) connects to SAP ECC
SAP-certified add-on installed in ECC
The CONTAX objects live in the SAP system and hook into outbound delivery processing and shipping. Users work in SAP screens; no separate shipping client is needed for the daily flow.
nShift Ship API (outbound HTTPS)
The add-on calls nShift for carrier selection, rates, shipment booking and label content. The ECC application server therefore needs outbound HTTPS to nShift endpoints, which matters on locked-down on-prem networks.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP ECC outbound delivery | CONTAX add-on | Ship-to, weights, packages, handling units, shipping conditions | Delivery created or packed |
| CONTAX add-on | nShift | Shipment request with parcel details and service level | User or rule books the shipment |
| nShift | SAP ECC | Tracking number, carrier, label, freight cost | Booking response |
| SAP ECC | Carrier systems via nShift | Goods issue and shipment status updates | Post goods issue |
Setting it up
- 1Confirm scope and ECC levelCheck the add-on's supported ECC enhancement pack and support package level with CONTAX before planning the install.
- 2Transport the add-onInstall through the normal landscape path: development, quality, then production, with Basis owning the import.
- 3Open network accessAllow outbound HTTPS from the application servers to the nShift endpoints and set up SSL certificates in STRUST.
- 4Configure carrier accountsEnter carrier contracts and credentials in nShift, then map them to plants and shipping points in the add-on settings.
- 5Map shipping conditionsAlign SAP shipping conditions, shipping types and packaging materials with nShift service codes.
- 6Set up labels and printersPick the label format per carrier and test output to the actual spool devices at each pack station.
- 7Test end to endRun domestic, international and dangerous goods deliveries, including a cancelled and a re-booked shipment.
- 8Cut over and monitorStart with one plant, watch failed bookings daily for the first weeks, then roll out.
What usually breaks
- !Unit of measure and weight mismatches between SAP packaging data and nShift limits cause rejected bookings.
- !Ship-to addresses that fail carrier validation (long street lines, missing postcodes) stop a booking at the pack bench.
- !Cancelling or splitting a delivery after booking can leave an orphaned shipment and cost at the carrier.
- !Label printer drivers and spool settings differ per site, so a label that prints in test can fail on the shop floor.
- !Carrier credentials expire or are rotated in nShift without anyone updating the SAP-side mapping.
- !Upgrades to S/4HANA need a check of the add-on version and any custom shipping enhancements.
A private AI layer across both systems
Failed booking triage
A private assistant reads the add-on error log next to the delivery and customer master and explains in plain words why a booking failed, proposing the address or weight fix for a person to approve.
Freight cost reconciliation
Compare booked freight in nShift with carrier invoices and SAP freight accruals to surface mismatches by carrier and lane.
Plain-language shipping questions
Let planners ask which open deliveries lack a carrier or tracking number, with the underlying query shown and SAP roles respected.
Late shipment watch
Join tracking status with promised delivery dates to flag orders likely to miss a ship date, running on your own GPUs so customer data stays inside.
When something else fits better
- SAP's own shipping and transportation functions plus a single-carrier interface may be enough if you ship with one or two carriers.
- A standalone carrier-management tool next to SAP works if you do not want an add-on in the ERP, at the cost of manual data handoff.
- SAP Transportation Management is the heavier option when you need freight planning and tendering, not just parcel labels.
Frequently asked questions
Does CONTAX need custom ABAP in ECC?
According to the vendor it is a certified add-on that runs in real time without custom SAP code. You still need Basis to import it and a functional consultant to configure shipping conditions, packaging and carrier mappings for your plants.
Is nShift a separate subscription?
Yes, nShift supplies the carrier connectivity, labels and rating, so it is a separate service from the add-on. Ask both vendors how licensing is split and whether per-shipment fees apply.
Can this run in a restricted on-prem network?
It needs outbound HTTPS from the SAP application servers to nShift, since carrier calls go through the Ship API. If policy blocks that, you will need a controlled proxy or a different design.
Does it carry over to S/4HANA?
The add-on is listed for both ECC and S/4HANA, which helps a staged migration. Verify the exact add-on version against your target release before you commit.
Pairing documented at nshift.com/webinars/nshift-contax-demo-sap-integration . CONTAX SAP shipping add-on (with nShift) is a product of CONTAX; Netray is independent and not affiliated with either vendor.