How Dimensions and Weight Are Provided to Forwarders in PeakWMS

INDHOLDSFORTEGNELSE

• Overview
• Weight — Where Does It Come From?
• Dimensions — Where Do They Come From?
• Packing Flows
  • Standard Packing (B2C)
  • Colli Packing
  • B2B Packing
  • Cross-Docking
  • Single-Line Packing (Pick Cart)
• Load Unit Types
• Forwarder-Specific Behaviour
• Summary
• Key Points for Clients

Overview

When PeakWMS requests a shipping label from a forwarder (carrier), it sends package weight and — for most forwarders — package dimensions (length, width, height). This document explains where those values come from across all packing flows and forwarder integrations.

Weight — Where Does It Come From?

When PeakWMS requests a label, the weight sent to the forwarder is determined by the following priority. The system checks each source in order and uses the first one that has a value:

Key point: If a weight is already stored on the pick order — whether set from the admin pick order overview before packing, or entered during packing — that value is always used. Otherwise PeakWMS calculates from product master data. If neither source is available, a safe default of 1 kg is sent to the forwarder.

Dimensions — Where Do They Come From?

When PeakWMS requests a label, dimensions (length, width, height) are determined by the following priority. The system checks each source in order and uses the first one that has a value:

Key point: Dimensions and weight can be set on a pick order at any time before the label is fetched — from the pick order overview in the admin UI using the "Set Shipping Dimensions" action. If values are present on the pick order, they always take first priority regardless of how they were set.

Packing Flows

Standard Packing (B2C)

This is the most common flow for consumer orders.

1. The operator scans a tote/container at the pack table.
2. PeakWMS automatically attempts to fetch a shipping label immediately, using calculated dimensions and weight (or values already set on the pick order).
3. If the automatic label fetch succeeds, packing proceeds — the operator confirms each item is packed and the label is printed. The operator does not need to enter any dimensions.
4. If the automatic label fetch fails(e.g. the forwarder rejects the request), a "Missing Label" dialog appears on the order overview screen. Here the operator can:
   • Enter dimensions (length, width, height) and weight manually
   • Click "Get New Shipping Label" to re-request with the entered values
5. The operator can also change the forwarder or re-request a label later during active packing via the "Change Forwarder" action in the order info panel — this also allows entering new dimensions and weight.

Setting dimensions before packing begins: From the pick order overview in the admin UI, a user can use the "Set Shipping Dimensions" action to set weight, length, width, and height on a pick order at any time before packing starts. These values will then be used automatically when the label is first requested — no manual entry during packing is needed.

If no values are set on the pick order, PeakWMS calculates them automatically from product data and load unit types (see priority table above).

Colli Packing

For business-to-business orders that ship as multiple parcels:

1. The operator splits the order into multiple parcels.
2. For each parcel, the operator specifies:
   • Which items go in that parcel
   • The load unit type — which carries predefined dimensions
   • Optionally: manual weight and/or dimensions per parcel
3. PeakWMS requests a label for each parcel individually, using that parcel's specific dimensions and weight.

B2B Packing

Similar to B2B packing but designed for shipments where one order is packed into multiple parcels that travel together:

1. The operator defines how many colli the order is split into.
2. For each colli, the operator specifies dimensions and weight.
3. PeakWMS requests labels for all colli as a single shipment, sending each load unit's specific dimensions and weight to the forwarder.

Cross-Docking

Cross-docking is used when goods are received inbound and immediately assigned to an outbound order without being stored in the warehouse.

Standard cross-docking (single label):

1. During receiving, the operator confirms that goods are cross-docked to a specific outbound order.
2. If load unit type is mandatory for the forwarder product the operator selects a load unit type — its predefined dimensions are then used.
3. The operator does not manually enter dimensions or weight in this flow.
4. PeakWMS automatically fetches the shipping label using:
   • The selected load unit type's dimensions (if one was chosen)
   • Otherwise: calculated dimensions from product data and available load unit types
   • Weight from product master data (or default 1 kg)

Multi-label cross-docking (multiple labels with optional dimensions):

When receiving larger quantities, the operator can choose to split the cross-docked goods across multiple shipping labels:

1. During receiving, the operator confirms cross-docking and specifies how many labels they want for the order line.
2. PeakWMS distributes the quantity as evenly as possible across the desired number of labels (e.g. quantity 7 with 3 labels → 3, 2, 2).
3. The system shows a row per label with the allocated quantity. For each label, the operator can optionally enter:
   • Width, length, height (in cm)
   • Weight (in kg)
4. If the operator leaves dimensions empty for a label, they are calculated automatically when the label is fetched — using the same priority rules described above.
5. PeakWMS fetches a shipping label for each split, using the entered dimensions where provided.

Key difference: In multi-label cross-docking, the operator has the option to enter dimensions per label at the time of confirmation, giving more control over what is sent to the forwarder for each package.

Single-Line Packing (Pick Cart)

Used for orders with a single item, typically packed at a pick cart rather than a pack table:

1. The operator picks and packs the item in one step.
2. No manual dimension or weight entry occurs.
3. PeakWMS resolves dimensions and weight automatically:
   • If the item is a "pick-alone" product, its own dimensions are used.
   • Otherwise, the 3D bin-packing algorithm finds the best load unit.
   • Weight is taken from product data.

Load Unit Types

PeakWMS allows you to configure load unit types with the following properties:

• Outside dimensions (length, width, height) — what is sent to the forwarder
• Inside dimensions — used by the 3D bin-packing algorithm to determine which items fit
• Empty load unit weight — can be added to the total shipment weight
• Shipping weight override — if set, this weight is used instead of the calculated weight
• Freight packaging code — carrier-specific code (e.g., for pallets vs. parcels)

When PeakWMS calculates dimensions automatically, it checks all available load unit types marked as "packing" or "both" and selects the smallest one where all items fit based on their registered dimensions.

Forwarder-Specific Behaviour

Not all forwarders receive the same data. Below is what PeakWMS sends to each:

Summary

Key Points for Clients

1. Accurate product master data matters. If your products have correct dimensions and weights registered, PeakWMS can calculate shipping data automatically — reducing manual work and errors.

2. Load unit types improve accuracy. Register your actual load unit sizes with correct inside and outside dimensions. PeakWMS will automatically pick the best-fitting load unit.

3. Manual entry always overrides. If the operator enters dimensions or weight at the pack table, those values are used regardless of what PeakWMS would calculate.

4. Some forwarders don't use dimensions. GLS, PostNord, and Danske Fragtmænd only receive weight — so dimension accuracy only matters for forwarders that use it (Bring, DAO, Shipmondo, etc.).

5. Cross-docking relies on master data (unless multi-label is used). In standard single-label cross-docking, the operator doesn't enter dimensions/weight, so it's important that product data and load unit types are configured correctly. With multi-label cross-docking, the operator can optionally enter dimensions per label, giving more control.