Wehkamp DSCO: (drop shipment) marketplace guide

About this guide

This is a ChannelEngine guide on the Netherlands-based Wehkamp marketplace, for sellers using Wehkamp’s drop shipment model. Here you can find information on how to request a Wehkamp drop shipment account, how to configure this channel on ChannelEngine, and what the specific requirements are.

Table of contents

About this channel

Commercial information

How to request an account

Associated costs

Marketplace features

Settings and configuration

Marketplace-specific requirements and exceptions

• Setup
• Product selection
• Mappings
• Pricing

Additional information

FAQs

About this channel

Wehkamp is a highly curated marketplace that partners with select brands. Wehkamp, together with kleertjes.com, the Netherlands' largest online store for new branded kids fashion, is a part of the Wehkamp Retail Group.  

Via Wehkamp’s drop shipment model, Wehkamp buys the products from the seller. Therefore, orders do not have shipping costs for sellers. To sell via its dropship model, list your products on Wehkamp via ChannelEngine and DSCO. Then, manage your offers and orders on ChannelEngine.

Commercial information

How to request an account

Wehkamp has a proactive and independent purchasing team; Wehkamp may approach you to discuss a partnership if your brand fits with its partnership criteria. If you are interested in selling on Wehkamp before receiving an invitation from Wehkamp, contact your customer success manager at ChannelEngine; your customer success manager then forwards your interest to the Wehkamp team.  

Once you become a Wehkamp brand partner, reach out to your Wehkamp contact person to set up your access to DSCO, where you store the product content for your Wehkamp listings.

Associated costs

There are no associated costs with selling on Wehkamp via its drop shipment model.

Marketplace features

1. Only pricing v2 is supported. Pricing v1 is not supported. For more information on pricing v2, check out ChannelEngine: pricing.
2. HTML formatting is only supported for the Description attribute.
3. Use the Product_group attribute to create variation families.
4. If a buyer needs to cancel an order, they must send a cancelation request directly to the seller via the marketplace. Then, the seller creates a merchant cancellation on ChannelEngine.

Settings and configuration

Setting up each channel on ChannelEngine follows the same flow, though not every channel includes the steps listed below.

1. Go through the Setup.
2. Create a Product selection.
3. Complete the Categorization.
4. Set up the Mappings: content, offers, and carriers.
5. Configure the Pricing: rules and currency conversion.
6. Fill in the Stock settings.
7. Finish the Activation.
8. Check the Listed products overview.

Marketplace-specific requirements and exceptions

The section below describes additional requirements and exceptions to the standard settings and configuration steps for setting up channel plugins on ChannelEngine.

Migrating from Wehkamp Direct Delivery

If you are an existing seller on Wehkamp, you can migrate your product data to the Wehkamp DSCO channel in a few steps. To set up your new Wehkamp DSCO channel using existing data from your Wehkamp Direct Delivery channel:

1. Request your Wehkamp DSCO production account via your Wehkamp contact.
2. Set up your API credentials and configure the new Wehkamp DSCO channel on ChannelEngine.
3. Copy your product selection from your existing Wehkamp DirectDelivery channel.
4. Categorize your products with Wehkamp's help, map your products, and run a ChannelEngine test order. For guidance on test orders, check out ChannelEngine: how to create test orders. 
5. Make sure your packing slips display the correct Wehkamp order ID — this is the Commercial order no. on ChannelEngine, not the Channel order no. as you are used to on the Wehkamp DirectDelivery channel.
6. Let your customer success advisor or the Support team know when your testing is complete. ChannelEngine coordinates the final switch with Wehkamp.

Setup

On DSCO

1. Obtain access to the DSCO platform by sending a message to ukonboarding@rithum.com. Wehkamp requires its sellers to use the DSCO platform for content creation. 
2. Retrieve your API credentials, and save these credentials for the setup process on ChannelEngine:
   1. Client ID
   2. Client secret
3. To find your credentials yourself:
   1. On DSCO, go to Automation & Reporting, Automation, API
   2. Click the Create Credentials button.
4. For more guidance on navigating the DSCO platform, check out the DSCO guide Creating new API credentials.

On ChannelEngine

Ensure that you have the pricing v2 feature enabled. Then, to set up your Wehkamp dropship integration on ChannelEngine, configure the following fields in Setup.

Connection

• Client ID and Client secret provided by your Wehkamp contact or retrieved from the DSCO platform.

Plugin-specific settings

• Warehouse code - the Code of the warehouse from the DSCO dashboard. Enter only one warehouse code. For more guidance on your warehouse code, check out the DSCO guide Warehouse management.
• Enable product content export - always keep this setting enabled.

Product selection

Mappings

To update content and offers for products that already exist on the DSCO platform, ensure that you use the same SKU that you use on DSCO for that item in Mappings. 

For guidance on how to map the attributes below, contact Wehkamp directly.

To learn how to leverage advanced rules or use ChannelEngine and custom fields for mapping the attributes below, contact ChannelEngine.

Content

All products (required)

• Afbeelding 1 (Image) - the product's main image. This image requires a neutral, white background. Main images contain a white background; extra images can contain other backgrounds.
• Brand - the manufacturer or brand name of the product (e.g.: "Nike", "Philips"). 
• Country_of_origin  - the country where the product was manufactured or assembled (ISO code or full name, e.g., "CN" or "China"). Important for customs, EU regulations, and display in product details.
• Hazmat_flag - indicates if the product is classified as hazardous material (true/false). Critical for shipping restrictions; hazmat items may require special handling or be restricted.
• Images.image_primary - the URL or reference to the main/primary product image. Required main image; high-quality, white-background preferred.
• Kleur___KLE - color of the item.
• Long_text_description_i18n.nl-NL - detailed, long-form product description in Dutch (Netherlands locale). Omschrijving (Description) is the full Dutch description; no HTML, plain text required for product page.
• Package_dimension_units - units for package dimensions (e.g.: "cm"). 
• Package_height - height of the packaged product. 
• Package_length - length of the packaged product. 
• Package_weight - weight of the packaged product (including packaging). 
• Package_weight_units - units for package weight (e.g.: "kg", "g"). 
• Package_width - width of the packaged product. 
• Product_title_i18n.nl-NL - the full product title/name in Dutch. Main product name shown in search/listings; must be Dutch, descriptive, and SEO-friendly.
• Title_i18n.nl-NL - short or display title in Dutch (may overlap with product_title). Used for headings; concise Dutch title required.
• Weight - product weight (usually net/item weight, without packaging). For product specs display and sometimes shipping base.
• Weight_units - units for product weight (e.g. :"kg", "g"). 

All products (optional)

• Air_carrier_service_flag - flag indicating if the product can be shipped via air carrier services (true/false). Relevant for logistics compliance; certain items (e.g., hazmat or oversized) may restrict air shipping.
• Description - general or short product description. Basic product summary in Dutch; used in listings and search snippets. HTML is allowed.
• EAN - European Article Number (barcode), typically 13 digits. Ensures unique product matching and catalog integration.
• Filterkleur___QBF - filter color, used for specific categories.
• Freight_carrier_service_flag - flag indicating if freight/less-than-truckload (LTL) shipping is allowed (true/false). For bulky/heavy items; determines if freight options are available in shipping.
• Ground_carrier_service_flag - flag for ground/standard parcel carrier eligibility (true/false). Default for most items; impacts carrier selection and costs.
• GTIN - Global Trade Item Number (umbrella for EAN/UPC/JAN etc.). Global identifier; used for product validation.
• Hazmat_class_code - specific hazardous material classification code (e.g.: UN number or class like "1.4"). Required for hazmat items; ensures regulatory compliance and restricted shipping.
• Images.image_extra_01-05 - URL/reference to additional/extra product images. 
• Images.image_model_01-05 - URL/reference to specialized images for model shots. Preferred for fashion/apparel to show fit and styling. Additional images do not require a neutral, white background.
• Max_business_days_to_ship - maximum business days allowed to ship the product after the order.
• Min_business_days_to_ship - minimum business days to ship (for handling time range). 
• Multi_Trend___J41 - multi-trend or trend classification attribute, e.g.: a reference to a season.
• Postal_carrier_service_flag - flag for postal/standard mail carrier eligibility (true/false). For lightweight/small items; affects low-cost shipping options.
• Product_group - (required for variants) grouping identifier for variants (e.g.: parent product for colors/sizes). Use the parent SKU as the grouping identifier. Only child products are exported to the channel.
• UPC - universal Product Code (barcode, typically 12 digits). Alternative/global barcode; used alongside EAN.
• USP1___US1-5 - unique selling points one through five (key benefit/feature highlight). Bullet points in product description; Dutch. Up to 5 USPs for detailed benefit listing.

Offer

There are no offer mappings in this plugin.

Carrier

Carrier mapping is required on this channel. Only the standard carriers from the DSCO platform are supported in the carrier mappings. Any customization to the supported carriers that you have created on the DSCO platform does not appear in the carrier mappings. 

Pricing

In Pricing, Price rules, map your selling price and the following additional price attributes:

• Price - (required) the cost price.
• List price - (required) the price of the product when this product is sold under a marketplace retail model. Adjust this price to set up a discounted price/promotion.
• MSRP - (required) Manufacturer’s Retail Price. When the MSRP is higher than List price, then a discounted price is created on Wehkamp.
• MAP - Minimum Advertised Price. Not used.

All price attributes include VAT.

Additional information

Orders

ChannelEngine imports all orders as purchase orders and then verifies the order import with Wehkamp, via DSCO.

All incoming orders contain the following order number fields:

• Channel order no. - the DSCO order ID.
• Commercial order no. - the purchase order number.
• Order date - the date on which the order was created on DSCO.

Order extra data items

When an order is imported to ChannelEngine, ChannelEngine also retrieves extra data items related to the order itself – or to order lines. This extra data is specific to this marketplace. An explanation of each can be found below: 

Order extra data

* Conditional fields are only displayed if the marketplace provides a value.

Order notifications

If ChannelEngine cannot confirm with Wehkamp that the order was imported into ChannelEngine, then you can receive an email notification about it.

The information in the email notification enables you to directly check the order status with Wehkamp. Use the IDs within the notification and the PO number in the order's Extra data to discuss the order with Wehkamp. To opt into receiving the failed order import notifications, enable the Failed order import notification at Account settings, Notifications, Orders.

If you receive a failed order notification, it is still possible to create the shipment for the order. However, it is recommended that you enable the Failed order import notification to clarify with Wehkamp any possible issues with the order.

Shipments 

When sending shipments via the Merchant API, sellers must use a shipment method that specifies a carrier from DSCO's list of standard carriers. If you have created a customized list of carriers on the DSCO platform, you must still use the carriers from the standard list when creating your shipment via the Merchant API. 

Shipment methods and tracking codes are required on all shipments.

• Return tracking codes are not required on shipments.

• Lead times/delivery promises are not mappable on ChannelEngine; you must request changes to lead times directly with Wehkamp.

Shipment carriers

Carriers are not available via the API.

For carrier mapping to work on ChannelEngine, ensure that the Customize checkbox in the Service Code column on DSCO is unticked because ChannelEngine does not support a customized list of service codes. Carrier mapping only works with the default list of carriers/service codes on DSCO.

Merchant cancelations

When you send a cancelation via the Merchant API, you must send a cancelation reason code. Choose a code from the list below. If you send any other reason than the below codes, the cancelation reason gets mapped to CXSO on the DSCO platform. 

Merchant cancelation reason

• NOT_IN_STOCK
• DAMAGED
• INCOMPLETE
• CLIENT_CANCELLED
• INVALID_ADDRESS
• Any other reason

Do not customize the list of cancelation codes on DSCO.

Returns

You must accept or reject an incoming marketplace return. Partial acceptance/rejection is not supported on the line level. E.g.: Return has one line with qty. = 3. Either accept all three items in the return or reject all three items in the return.

Marketplace returns are imported as In progress and with a return reason. The return reason is based on DSCO’s default set of return reasons:

Return reason

• WRONG_PRODUCT
• PRODUCT_UNSATISFACTORY
• NOT_COLLECTED
• PRODUCT_DEFECT
• REFUSED_DAMAGED
• REFUSED
• TOO_MANY_PRODUCTS
• WRONG_ADDRESS
• WRONG_SIZE
• OTHER

Do not customize the list of return reason codes on DSCO. You create merchant returns using the same codes as in the above list; these codes are based on the default return reason codes that are found on DSCO.

FAQs

My stock levels and selling prices are incorrect on the DSCO platform. What should I do?
When your stock and price data are sent to DSCO, DSCO matches the SKU that is associated with the data to the SKUs that exist on its platform. If the SKU-selling price combination in Mappings is different than the SKU-selling price combination on DSCO, first check if you have correctly mapped the item on ChannelEngine. Make changes to the SKU if necessary. If this doesn't resolve the problem, then contact the ChannelEngine Support team. If the error is still not resolved, please contact the DSCO Support team.

Why am I not receiving feedback on my content and/or offer exports?
Error reports are not generated for DSCO marketplaces. 

My order acknowledgement was not sent to the marketplace. What should I do?
When your order acknowledgement is prevented from being sent to the marketplace, you receive a notification. The request ID of this notification appears in the Extra data of the order. Use the request ID of the notification to discuss the order acknowledgement issue with the marketplace directly. If this scenario occurs, you can still create the shipment for the order, even if the acknowledgment issue is not resolved.

How often does each task run on DSCO-based marketplaces?
By default, DSCO-based marketplaces follow the schedule below: