Schenker deliveries implementation overview

Schenker's direct EDI integration generates address cards from AI Commerce without a separate Shipit solution. The implementation consists of two parts: the IDs received from Schenker are saved in the store settings and the correct function code and label type are selected for each delivery method using Schenker.

The configuration supports Schenker Parcel B2B delivery to a business address and Schenker Pickup Point B2C order for a consumer. You can configure multiple delivery methods for the same store to Schenker.

Collect the necessary information from Schenker

Schenker implementation requires a web service username and interface key. In addition, you will need a customer number for at least the delivery type you are implementing:

• SCHENKER_WS_USER : Schenker web service username
• SCHENKER_ACCESS_KEY : Schenker interface key
• SCHENKER_CUSTOMER_PARCEL : B2B customer number for the business parcel
• SCHENKER_CUSTOMER_CP : B2C customer number of the consumer pickup point

Request the values from Schenker. AI Commerce uses a pre-defined interface, so there is no need to enter a separate interface address or version in the settings.

Save credentials in Settings

Schenker IDs are stored in the Settings view of the Control Panel. Find each of the four configuration keys by its exact code and fill in the value received from Schenker. The interface key is a secret value; only reveal it if you are editing an already stored value.

Changes will be saved automatically after a short delay. For each field, check that the save status changes to successful before moving on to the next step.

Check integration status

The status of the Schenker integration can be checked in the Integrations view of the Dashboard. The DB Schenker card brings together the username, interface key, and customer codes in one view, so you can see which required information has already been configured.

In the Integrations view of the dashboard, you can check the DB Schenker integration fields, but the view is read-only. Therefore, edit the IDs in the Settings view, not in the integration data card.

Configure Schenker for each shipping method

The Schenker delivery method is configured in the Deliveries view of the Control Panel. Open the settings for the delivery method using Schenker and find its Schenker code and Schenker label type.

1. Select createOrderParcel as the action code when the delivery method takes the package directly to the company address using Schenker's B2B service.
2. Select createOrder as the action code when the delivery method is Schenker B2C pickup point order.
3. Select the label type for the delivery method according to the Schenker contract. A5 is usually used for business packages. At the pick-up point, the option is typically CP or Long, but verify the value in your own Schenker contract.
4. Wait for each field to complete auto-saving.

The Schenker specification for a delivery method can be left blank if that delivery method is not shipped with Schenker. Do not copy the same function code to all delivery methods without checking whether it is a business address or a pickup point. The usual combination for a business parcel is createOrderParcel and A5. A5 is a label type, not a function code.

Check when the Schenker feature will be available

The Schenker function is only available when the web service username and interface key have been saved, at least one Schenker customer number exists, and the Schenker code for at least one delivery method matches the customer number type in question.

A B2B business parcel requires a business parcel customer number and createOrderParcel specification. A B2C pickup point requires a pickup point customer number and createOrder specification. A pickup point order must also have a pickup point identifier ready in the order's delivery information so that an address card can be generated.

Print a single Schenker address card

The address card for an individual Schenker order is printed from the Schenker order function. The order must have a delivery method with the correct Schenker code stored, as well as the recipient and delivery information required by Schenker.

If an individual Schenker function is not visible on a supported order, first check the IDs in Settings , the delivery method function code in Deliveries , and the pickup point ID for the pickup point order.

Print multiple Schenker address cards

Batch printing of Schenker address cards is opened from the Orders view in the Control Panel using the Batch PDF Schenker function.

Batch printing processes orders assigned to Schenker and combines successful address cards into a single PDF file. Before running, check that the delivery method and pickup point information for each order matches the selected Schenker service.

Find out the missing Schenker function

If Schenker does not appear or the address card does not appear, check the settings in this order:

1. SCHENKER_WS_USER and SCHENKER_ACCESS_KEY are saved.
2. The customer number of the service in use is stored: the B2B business parcel needs SCHENKER_CUSTOMER_PARCEL value and the pick-up point service needs the SCHENKER_CUSTOMER_CP value.
3. The Schenker code for the order delivery method is exactly createOrderParcel or createOrder depending on the service.
4. The label type corresponds to the Schenker agreement.
5. The order has the recipient's delivery information, and the pickup point order has the pickup point identifier.

When you correct the setting in the Control Panel, wait for the auto-save to complete and then open the print function again. If all conditions are met but Schenker is still not available, record the order ID, shipping method code, and Schenker service used in the support request. Do not attach the interface key to the support request.