¶ DB Schenker - pallet freight and B2B delivery

DB Schenker in Hummerce is a courier integration covering two carrier services: System (pallet and freight shipments, typical for B2B customers) and Paczki (parcels). The store automatically creates the shipment with the carrier after the delivery status changes, retrieves the label and waybill number, and periodically checks the delivery status.

Last updated: 2026-09-29.

¶ Benefits and use cases

Pallet shipments (System service) alongside regular parcels (Paczki service) - one integration for both retail and business (B2B) customers.
Automatic shipment and label creation once the delivery status changes to "ready to ship" - no manual re-typing of the address into the DB Schenker system.
Automatic change of the delivery status to "Delivered" once the carrier's API reports it.
Cash on delivery support.
An email to the customer with the waybill number and a tracking link, sent right after the shipment is created.

¶ How it works

¶ Two services as separate delivery methods

The panel sets up a separate delivery method for the System service and another for the Paczki service - each has its service type assigned in the module configuration.
Default parcel data (weight, packaging type, contents description, insurance) is set for the whole integration; the packaging type has a defined list of codes (e.g. carton, EUR pallet, disposable pallet, crate, barrel, bucket, reel).

¶ Creating the shipment and label

After the order's delivery status changes to "ready to ship," the store totals the parcel weight from the order lines, sends the transport order to the DB Schenker API, and saves the returned waybill number.
The shipment label (PDF) is fetched automatically once the order is created and saved on the order.
Sender, recipient and payer data (if different from the sender) is set in the module configuration; recipient data comes from the order's delivery address by default.

¶ Cash on delivery (COD)

When the payment method the customer chose is marked as cash on delivery, the transport order gets an additional COD service, with the collected amount equal to the order's final value including tax.

¶ Shipment status

A background task periodically checks (every 6 hours by default) the shipment status for orders with a waybill number and saves the carrier's messages on the order.
The delivery status "Delivered" is set automatically once the matching event arrives from the API. The event for the carrier picking up the parcel from the sender doesn't currently change the delivery status automatically.

¶ Email notification

An optional setting sends the customer an email with the waybill number and a tracking link right after it's created, independent of the general shipment tracking mechanism.

¶ Version

The DB Schenker integration is a module of the Hummerce platform, available in current versions.

¶ Dependencies

A contract with DB Schenker: a customer number and API access data (login, password) - the store obtains these on its own.
A configured sender address (and payer, if different) in the module settings.
A file storage location (VFS/FTP) configured in the store - for storing the PDF labels.
Weight set on items - needed to calculate the parcel weight correctly.
A link to payments (cash on delivery) - Payments overview.
General rules for delivery methods - Delivery methods overview.

¶ Implementation

Requires implementation - the integration doesn't work without configuration. Scope:
- enabling the module and setting up API access data (test, then production),
- configuring the sender address (and payer),
- setting up delivery methods for the chosen services (System, Paczki) and the default parcel settings,
- an email template with the waybill number,
- testing in test mode and switching to production.
Minimum estimated time:
- configuring one service (System or Paczki) in the panel and testing - from 4 h,
- the second service in parallel - an additional 1 h,
- an email template with the shipment number - from 1 h.
What the time depends on: the number of services enabled, the number of delivery methods and views, whether the default parcel data needs to be matched to the product range.

¶ Limitations

Automatic shipment statuses update periodically (every 6 hours by default) - less often than in some other courier integrations.
Only the "Delivered" status is set automatically; the carrier picking up the parcel from the sender doesn't change the delivery status automatically.
The System and Paczki services need separate delivery methods in the panel - they can't be combined into a single option with the customer choosing the service.
No management of the integration through the REST API and MCP - configuration only in the panel; the waybill number and messages are visible as order parameters.
The default parcel data (weight, packaging type) needs to be matched to the product range - otherwise the store sends default values to the carrier.
We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).

¶ Future development

Automatic detection of the carrier picking up the parcel from the sender as a separate delivery status.
Managing the integration and shipment status through the REST API and MCP.
Extending shipment tracking with the DB Schenker API.

¶ Frequently asked questions

Does DB Schenker in Hummerce support pallet shipments?
Yes. The System service covers pallet and freight shipments, and the Paczki service covers regular parcels; both are configured as separate delivery methods.

Does the store create the shipment and label with DB Schenker on its own?
Yes. Once the order's delivery status changes to "ready to ship," the store creates the transport order and fetches the PDF label.

Does the integration support cash on delivery?
Yes, for payment methods marked as cash on delivery - the collected amount is the order's final value.

Is the "delivered" status set automatically?
Yes, once the matching event arrives from the DB Schenker API; the carrier picking up the parcel from the sender doesn't change the status automatically.

How long does implementing the DB Schenker integration take?
From 4 h for one service (System or Paczki); the second service in parallel - an additional 1 h.

Does the customer get an email with the shipment number?
Yes, optionally - once the setting to send an email when the waybill number is created is enabled.

Delivery methods overview - general pricing and configuration rules for delivery methods.
shipment tracking - the general status and tracking-link mechanism.
B2B sales overview - the business sales context.
Payments overview - the link to cash on delivery.
On hummerce.com: Integrations (in Polish), B2B platform (in Polish).

Want to see how the DB Schenker integration could work in your store? Contact the Hummerce team (in Polish).

¶ Configuration details

¶ Access in the admin panel

Integration configuration: Configuration -> the Schenker tab (Module Schenker group) - Test mode, Web Service URL, Login, Password, Client No; sender data (Sender name 1/2, Street, Postal code, City, Email, Phone, Nip, Contact person); Payer data same as sender and separate payer fields when disabled; parcel settings: Default weight, Additional weight, Default parcel name, Default parcel insurance, Default parcel type; Send email when waybill number is created.
Editing a delivery method: two separate delivery methods, each assigned to one of the services (System, Paczki) in the module configuration.
Order: waybill number, messages and error codes from the carrier's system, the PDF label file, parcel weight and type - in the order details.

¶ REST API and MCP

The shipment number and messages from the Schenker system are order parameters - available through the general REST API for order properties. No dedicated MCP methods for the Schenker integration; the general MCP for deliveries and order status - see Delivery methods overview.

¶ Store messages

The email sent to the customer once the waybill number is created is edited in the message templates; the available variables are the order, the waybill number, a link to the order and a link to track it with the carrier.

¶ Parameters

Symbol	Object	Label
`_schenker_waybill`	order	Waybill number
`_schenker_courierMessage`	order	Messages from the courier system
`_schenker_trackingMessage`	order	Tracking messages
`_schenkerErrorCode`	order	Integration error codes
`_schenker_shippingLabel`	order	Shipment label (PDF)
`_grossWeight`	order	Parcel gross weight
`_packageAmount`	order	Number of parcels
`_packageType`	order	Parcel type
`_schenker_cliDelivDateSpecified`	order	Custom delivery date
`_schenker_clieDelivDateFrom`, `_schenker_clieDelivDateTo`	order	Delivery date from / to