Articles on: Others

Understanding DB Schenker Slugs in AfterShip

Overview

When using AfterShip to track shipments with DB Schenker, you might encounter several different carrier slugs (e.g., dbschenker, dbschenker-se, dbschenker-api). Although they appear related, each serves a distinct purpose. As a merchant, choosing the right slug is critical to ensure shipments are tracked correctly.

What you’ll learn

In this article, you will learn.

What are slugs?
Which DB Schenker slug to use in which scenario?
What are common mistakes and how to avoid them?
What is the internal logic behind slug mapping?

What is a slug?

In AfterShip, a slug is a unique identifier for each carrier integration. It tells AfterShip which data source or method to use when retrieving tracking updates for a shipment.

For complex carriers like DB Schenker, there are multiple slugs, each representing a different type of integration (e.g., web scraping, API connection, regional service).

DB Schenker slugs

Here’s a breakdown of the slugs you might see for DB Schenker and what they represent:

Slug	Type	Credentials required	Description
`dbschenker-se`	Public integration (child slug)	No	This is used for global tracking using DB Schenker’s public website. Data is scraped, and tracking is effective across multiple regions.
`dbschenker-api`	API integration (child slug)	Yes	This uses DB Schenker’s official API for tracking. Customers must provide valid API credentials (username/password or token).
`dbschenker`	Internal `master` slug	Not directly usable	This is an internal reference slug used by AfterShip in the UI and URLs. It is mapped internally to either dbschenker-se or dbschenker-api, but should not be used when uploading shipments.

Use either dbschenker-se or dbschenker-api in your system, depending on your integration method.
Do not use dbschenker in API requests or manual uploads; it will result in errors.

How the slug logic works internally

AfterShip uses a concept of master and child slugs:

Master slug (dbschenker): A general label representing the carrier (DB Schenker), shown in AfterShip’s UI and URLs.
Child slugs: The actual integrations that fetch tracking data (dbschenker-se, dbschenker-api, etc.)

Why this matters

When you see dbschenker in the public tracking page URL (e.g., https://www.aftership.com/couriers/dbschenker), you might assume it’s the correct slug for uploads. But in reality, AfterShip routes the tracking logic to a more specific child slug based on your integration type and region.

When to use each slug

Use case	Slug	Why
You want to track shipments with no credentials or API access	`dbschenker-se`	This integration pulls tracking data from DB Schenker’s public tracking page. Use this if you don’t have API access.
You want to use authenticated API integration	`dbschenker-api`	This requires valid credentials and pulls data from DB Schenker’s partner API. Use this if you’ve set up API credentials in AfterShip.
You copy `dbschenker` from a tracking URL and use it in the dashboard or API	Do not use	This is a master slug and not supported for direct use. Don’t use this manually. Instead, use the correct child slug based on your integration.

Troubleshooting tips

Issue: You upload tracking numbers using `dbschenker` and get an error

Resolution: The dbschenker is not a valid upload slug. We recommend using:

dbschenker-se if no credentials are available
dbschenker-api if they have API credentials

Issue: You see `dbschenker` in the tracking page URL and think it’s the right slug

Resolution: This is intentional. AfterShip displays the master slug (dbschenker) for consistency in the UI; however, the actual tracking backend uses either dbschenker-se or dbschenker-api, depending on the setup.

Technical notes for developers

If your team is using AfterShip’s API:

Always pass a child slug like dbschenker-se or dbschenker-api in the POST /trackings endpoint
Use dbschenker-api only when credentials are configured in your AfterShip account under Carrier settings.
The web scraper-based slug (dbschenker-se) is easier to use but may not always support all tracking number formats or offer as much detail.

Additional slugs

You may also encounter other DB Schenker slugs used for specific country-based integrations:

Slug	Purpose	Use?
`dbschenker-sv`	Sweden-specific	Ignore unless directed by AfterShip Support
`dbschenker-b2b`	B2B integration	Not for general use
`dbschenker-iceland-ftp`	FTP-based for Iceland	Niche use only

Unless AfterShip Support tells you otherwise, stick to dbschenker-se or dbschenker-api.

Best practices

Always validate the slug you use against the Supported couriers list.

If credentials are required but not provided, tracking with dbschenker-api will fail silently or return authentication errors.
Use dbschenker-se if you’re unsure or don’t have API credentials.
Never use dbschenker in manual uploads or API calls.

Have questions?

If you are unsure about which slug to use or encounter errors during shipment uploads, please contact the AfterShip Support team.

Updated on: 31/07/2025