B2B wholesale fulfilment from a European 3PL

Separate wholesale from DTC

Direct-to-consumer parcels usually focus on individual units, branded inserts, customer tracking and return convenience. Wholesale orders may involve full cases, mixed pallets, retailer labels, ASN files, booking windows and proof that routing instructions were followed. Treating them as the same workflow creates avoidable errors.

The first scoping step is to list every wholesale customer type: retailer, distributor, marketplace vendor, corporate buyer or internal transfer. Each type may need a different order template, packing standard and evidence file.

• Create wholesale order types
• Keep DTC and B2B service rules separate
• Record customer-specific requirements

Case packs and pallet rules

Wholesale picking depends on accurate case-pack master data. The warehouse needs units per inner, units per case, case dimensions, pallet configuration where used and whether cases may be broken. If the sales team sells in cases but the system only knows eaches, errors are likely.

Pallet rules should cover stacking, mixed-SKU limits, carton sequence, weight data, wrap requirements if agreed, and whether the customer permits substitutions or shortages. Do not invent a universal pallet standard; follow the customer's routing guide and the 3PL's agreed capability.

• Maintain case-pack master data
• Define whether cases can be split
• Capture pallet and carton dimensions

Routing guides

A retailer routing guide turns into warehouse tasks: label placement, carton content rules, carrier choice, appointment booking, ASN timing, document upload and exception contacts. The brand should provide the guide early enough for the 3PL to confirm what is possible.

If a requirement cannot be met, the seller should resolve it with the buyer before the order is accepted. The warehouse should not discover a routing guide after picking has started.

• Store the current guide by customer
• Confirm feasibility before first order
• Escalate guide changes promptly

EDI and file exchange

Some wholesale customers expect EDI or structured files for orders, ASNs, invoices or confirmations. Others work with portal downloads or spreadsheets. The fulfilment design should say which files the 3PL handles, which fields are mandatory and who fixes rejected messages.

Testing matters because a file can be technically received but still fail the buyer's business rules. Test order, pick, pack, ASN and cancellation cases before the first live wholesale shipment.

Keep a simple message log for each wholesale customer, including file name, transmission time, acknowledgement, rejection reason and correction owner. When a buyer portal changes a field or code list, the log helps separate system faults from missing master data before the next release cycle or routing review. Share recurring failures in the weekly operations review before new orders are accepted for that account or buyer group in scope.

Appointments and delivery evidence

Wholesale deliveries may need appointment booking, dock references, delivery windows or carrier instructions. The brand should define who books appointments, who receives changes and what happens if a slot is missed or refused at receiving.

Evidence protects the brand when a buyer questions compliance. Keep label copies, carton counts, pallet photos where agreed, shipment references, ASN confirmations and exception notes. Evidence requirements should be realistic and written into the service scope.

• Assign appointment ownership
• Store shipment and ASN confirmations
• Photograph outbound pallets when required

Chargebacks and improvement

Retail chargebacks can come from label errors, late appointments, incorrect carton contents, missing ASNs or document mismatches. This article does not assess whether a chargeback is commercially valid. Operationally, the brand and 3PL need evidence and a correction process.

A useful review looks at chargeback reason, customer, order type, root cause and prevention step. If the cause is unclear master data or late routing-guide changes, fix the upstream process rather than only disputing the invoice.

• Track chargeback reasons
• Separate warehouse errors from customer-data issues
• Update SOPs after confirmed root causes

Information to include in a fulfilment brief

• Wholesale fulfilment needs its own rules; it is not simply ecommerce picking at a larger quantity.
• Case-pack and pallet master data must be accurate before retailer orders are accepted.
• Routing guides should be reviewed before picking starts, not discovered during dispatch.
• EDI and portal files need business-rule testing, not only technical connection checks.
• Delivery evidence should match the buyer's requirements and the 3PL's agreed service scope.
• Chargeback reviews should identify root causes without turning the warehouse into a commercial judge.

VareYa can scope the warehousing and fulfilment work from a clear operating brief. Customs, tax, product and legal responsibilities should be checked with qualified advisers before inventory moves.

Questions teams often ask

Related VareYa Knowledge Center guidance

• 3PL selection checklist for Shopify brands
• Ecommerce warehousing in the Netherlands
• VareYa versus traditional warehousing: fulfilment differences
• Shopify Markets and EU fulfilment: what operations need
• Amazon Pan-European FBA versus an independent EU 3PL
• Multi-channel inventory management from one EU warehouse