How nShift (Delivery / Ship API) for SAP connects to SAP ECC
nShift Ship API and SAP connectors
nShift lists SAP ERP, Business One and SAP WMS connectors built on the Ship API, plus partner add-ons. In ECC this usually sits in the outbound delivery or packing step, calling nShift to get a consignment, tracking number and label.
Partner add-ons
Some customers use a partner-built SAP add-on that wraps the API. Ask which route your reseller supports, and who maintains it after an SAP upgrade.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP ECC outbound delivery | nShift | Ship-to address, weights, packages, service options | Delivery packed or goods issue prepared |
| nShift | SAP ECC | Tracking number, consignment ID, carrier and service | Carrier booking confirmed |
| nShift | Label printer | Carrier label and shipping documents | Booking confirmed |
| nShift | SAP ECC | Freight cost where returned | Shipment closed or manifested |
Setting it up
- 1List carriers and servicesDecide which carriers and service levels you use per country, and set up your carrier contracts in nShift.
- 2Choose the SAP integration routeSelect the connector or partner add-on and check its supported ECC enhancement pack and add-on prerequisites.
- 3Map delivery dataMap ship-to partner fields, package structure and weights from the outbound delivery to the API payload.
- 4Set shipping rulesDefine rules that choose the carrier and service based on destination, weight, customer or incoterm.
- 5Configure printingSet label formats and printer destinations at each packing station.
- 6Test edge casesTest multi-package shipments, returns, hazardous goods, and non-EU destinations that need customs documents.
What usually breaks
- !Delivery addresses truncated or badly formatted in SAP, causing carrier rejections.
- !Package weights missing, so the booking uses defaults and the carrier invoices differences.
- !Tracking numbers written back late, after the customer confirmation has already gone out.
- !Carrier service codes changing without anyone updating the rules.
- !Customs documents for non-EU shipments depending on commodity codes absent from the material master.
- !Connector or add-on not retested after an SAP support package.
A private AI layer across both systems
Booking failure triage
Explain why a carrier rejected a booking, using the delivery data and the API response, and suggest the address or weight fix for a clerk to approve.
Freight cost checks
Compare carrier invoices to booked services and weights to flag surcharges and wrong service levels.
Customer shipment questions
Let customer service ask where an order is and get tracking details read from SAP and nShift, without opening several screens.
When something else fits better
- A single carrier's own SAP or desktop shipping tool is enough if you ship almost entirely with one carrier.
- SAP's own parcel and transportation features can fit if you already run SAP TM.
- Another multi-carrier shipping platform with an SAP connector is a fair comparison for your countries.
Frequently asked questions
Does nShift work with SAP ECC?
nShift's SAP integrations page lists SAP ERP, Business One and SAP WMS connectors. Ask nShift or its partner for the supported ECC enhancement pack and the exact delivery or packing step where the call is made.
What does it write back to SAP?
The vendor describes writing shipment data back to SAP. Typically that means tracking number, consignment and carrier details, and sometimes freight cost. Confirm which fields and which SAP object they land in for your setup.
Which carriers are supported?
nShift describes a broad set of European carriers. Check your specific carriers and services per country with them, including returns and special services, rather than assuming coverage.
Does it cover Business One as well?
Yes, the same page lists Business One connectors. The integration technique differs from ECC, so treat them as separate projects when planning effort and testing.
Pairing documented at nshift.com/integrations/sap . nShift (Delivery / Ship API) for SAP is a product of nShift; Netray is independent and not affiliated with either vendor.