DB Schenker Tracking

How to track a DB Schenker shipment

Use a route-first check:

1. Look at the current shipment evidence. If the sender, booking, paperwork, or account still identifies the shipment as DB Schenker or Schenker, treat it as a Schenker-lane job first.
2. Open the current Schenker Track & Trace action published by DSV.
3. Enter the identifier exactly as it appears in that Schenker shipment context.
4. Compare the returned record with the shipment, booking, or sender information you already have.
5. If the current record/account now identifies the shipment as DSV, switch to DSV Tracking rather than trying to make the two lanes interchangeable.

The current Schenker public action is available without a customer login. DSV's global interface labels the field simply Enter ID number.

If the number is not recognized, do not immediately assume that it is fake or invalid. First confirm whether the reference belongs to the Schenker lane, the DSV lane, or another shipment system. The tracking-number verification guide can help classify an uncertain reference.

Is DB Schenker now DSV?

At the corporate level, yes: DSV completed its acquisition of Schenker on 30 April 2025.

At the customer-system level, the transition is still more complicated. DSV states that dbschenker.com has been merged into DSV.com, while its current Self-services page still exposes:

• Track DSV shipment
• Track Schenker shipment
• myDSV
• myDSV (formerly DB Schenker Connect)

DSV also tells Schenker customers to continue using Schenker systems until their freight forwarder or account manager informs them about migration to DSV systems.

That is why this page does not treat Schenker as merely another spelling of DSV. The businesses are under the same corporate owner, but the current user-facing tracking/account routes remain partly separate.

DSV's H1 2026 report said that more than 60 countries were either fully integrated or in the integration process and that completion was still expected by the end of 2026. That is a corporate integration target, not proof that every shipment, account, country tool, or reference switches on one date.

Should I use Schenker tracking or DSV tracking?

Use the current evidence attached to the shipment:

Do not create a merged identity such as DSV Schenker to bypass this decision. The useful question is which live system currently owns the record you are trying to read.

Which shipment ID should I enter?

The global Schenker tracking field currently says Enter ID number. It does not publish an exhaustive worldwide DB Schenker number grammar beside the input.

Use the reference that is explicitly tied to the Schenker shipment, booking, sender message, or account flow you are using. Keep its provenance: knowing where the identifier came from is often more useful than guessing from its length or prefix.

Do not treat an identifier as valid or invalid solely because it matches a third-party pattern. In particular, this page does not publish a universal DB Schenker:

• prefix;
• fixed length;
• suffix;
• checksum;
• regular expression.

If the reference belongs to a different system or has not yet become searchable, see Tracking Number Not Found rather than forcing it into a guessed format.

Public tracking and former-Schenker customer systems are different

The public Schenker Track & Trace route and authenticated customer systems solve different jobs.

Use public Schenker tracking when you have a shipment identifier and need the public record. If you are an existing former-Schenker customer, DSV currently also provides myDSV (formerly DB Schenker Connect) for the transition period.

Authenticated account tools can contain customer-specific booking or shipment information that is not necessarily available in an anonymous public lookup. This page does not imply that 11Tracking can access those private systems.

Does a tracking record mean Schenker has the freight?

Not by itself.

DSV describes tracking as beginning from the point an order is placed. That means a booking or tracking record can exist before a shipment-specific event proves physical pickup or acceptance.

Use the strongest event you actually have:

booking/reference exists
→ shipment-specific acceptance or pickup evidence
→ movement evidence
→ later delivery evidence

The first step confirms a record exists in the relevant system. It does not, by itself, establish physical possession.

If your problem is specifically that a valid reference exists but no searchable carrier record appears yet, use the Tracking Number Not Found guide.

What if another carrier appears?

A multi-leg shipment can expose another carrier or tracking identity. When that happens, do not treat a carrier name in one record as automatic proof that the second carrier has physically accepted the freight.

Check whether the other carrier's own system recognizes the shipment and shows an acceptance or movement event. Once that happens, its record is normally the stronger source for that carrier's leg.

For an international handoff where you need to identify the destination carrier or local number, use How to Find the Last-Mile Carrier and Local Tracking Number.

What does Delivered prove?

A Delivered event is important delivery evidence, but it is not the same question as whether the named recipient personally received the shipment.

If the tracking record says Delivered and you do not have the shipment, move to the evidence and recovery workflow in Package Says Delivered but I Did Not Receive It. Check any available delivery location, signature, photo, recipient/agent information, or other proof in the system that actually recorded delivery.

A delivery status also does not decide a seller, marketplace, replacement, or refund outcome. Those commercial decisions belong to the transaction process that controls the order.

How do I get help with a DB Schenker shipment?

Use the current route that owns the problem:

• Public tracking: use the current Schenker Track & Trace action published by DSV.
• Former-Schenker customer account or migration: use the DSV Self-services path for myDSV (formerly DB Schenker Connect).
• Claim workflow: DSV's current eClaims service supports claim submission, existing-claim status, document upload, and communication with local claims adjusters. Eligibility and deadlines can depend on the shipment and claimant role.
• Local organization routing: use DSV's current office finder. A nearby office is not automatically the actor controlling a specific shipment.
• Order, replacement, or refund: use the seller or marketplace process that controls the commercial transaction.

11Tracking can help interpret public tracking evidence and route the next step. It cannot access private myDSV/Connect accounts, create scans, make a carrier recognize an identifier, contact DSV or Schenker, reroute freight, clear customs, file a claim, force a refund, or guarantee delivery.

What may change as DSV completes the integration?

This is a transition page, not a claim that DB Schenker will remain a separate tracking lane indefinitely.

DSV is actively integrating Schenker. The separate Schenker tracking choice, former-Schenker login path, and migration guidance can change as that work progresses.

For now, the practical rule is simple:

If the active shipment evidence still says DB Schenker or Schenker, use the current Schenker lane. If the active record or account has migrated to DSV, use DSV Tracking.

Do not use the acquisition date alone as proof that a particular shipment has already moved from one tracking system to the other.