HOW-TO · Shipping

How to set up shipping rules by weight and destination

Use weight, country, carrier service and marketplace promise to route each order before the packing team prints a label. ChannelDock’s shipping automation is handled through Shipping Rules.

Segment
orders by lane
Route
by weight and country
Review
exceptions before labels
Rule decision previewRule matched
NL parcel · 1.6 kgPostNL
DE parcel · 4.2 kgDHL
BE parcel · pickup pointDPD
Hold: missing package weight

Shipping rules matter because carrier choice is rarely one-dimensional. The right rule combines destination, weight, package size, service promise, cost and warehouse cutoff before the parcel reaches the label printer.

Faster decisionsno carrier guessing
Cost controlavoid expensive lanes
Cleaner routingmatch country and weight
SLA safetyprotect delivery promises

Before you start: what you need

Prepare the operational inputs first. A rule engine only works when the order data and carrier constraints are reliable.

Accurate product and package data

Make sure SKU weights, packaging weight, dimensions and special handling flags are maintained before orders reach the shipping queue.

Carrier services and lane rules

List which carriers serve each country, pickup point, weight band, cutoff time and marketplace program such as next-day or tracked delivery.

Permission to edit shipping settings

Give operations leads access to maintain rules, while packers follow the selected service instead of choosing from memory.

Tip: start with the three lanes that create the most manual decisions: domestic parcels, cross-border EU parcels and overweight parcels. Add rare exceptions after the core rules are stable.

Step-by-step: build shipping rules by weight and destination

Use this sequence to turn informal carrier knowledge into rules your warehouse team can apply consistently.

Map your current shipping lanes

Export or list recent orders by destination country, carrier, weight band, package type and delivery promise. Look for the combinations your team repeats every day.

Common mistake: building rules from carrier price sheets only, without checking which lanes actually appear in your order history.

Define weight and dimension thresholds

Create practical bands such as letterbox, 0–2 kg, 2–10 kg, oversized and pallet. Include packaging weight so the final parcel does not exceed the carrier limit.

Common mistake: using product weight only, then discovering that the packed parcel belongs to a more expensive carrier tier.

Create the rule logic in ChannelDock

Translate each lane into conditions for destination, weight, service, marketplace promise and preferred carrier inside Shipping Rules.

Common mistake: writing one broad default rule before specific exceptions, causing special orders to match the wrong carrier.

Add holds for missing or risky data

If an order is missing package weight, destination details or a required service code, route it to a hold queue instead of creating a weak label.

Common mistake: letting incomplete orders fall through to the cheapest default carrier.

Test rules with real orders before peak volume

Run a sample from your last busy day and compare the selected carrier against what an experienced operator would choose. Adjust thresholds where the rule is too broad.

Common mistake: testing only simple domestic parcels and missing cross-border or marketplace-service exceptions.

Review performance after carrier or marketplace changes

Schedule a monthly check for new surcharges, cutoff changes, pickup-point rules and marketplace delivery promises. Rules are operational assets, not one-time settings.

Common mistake: keeping rules unchanged after peak surcharges, carrier contract updates or marketplace SLA changes.

The rule flow at a glance

A good shipping rule works like a decision path: it enriches the order with parcel data, checks the destination and chooses the approved service before label creation.

The best shipping rule is not “use the cheapest carrier.” It is “use the cheapest carrier that still meets the promise for this parcel.”

Order queue
Weight band
Destination
Carrier service

Common shipping-rule pitfalls

  • Putting a default carrier rule above more specific country, weight or marketplace exceptions.
  • Forgetting packaging weight, dimensional weight or oversized surcharges.
  • Letting packers override rules without logging why the carrier changed.
  • Routing remote areas and pickup points the same way as standard home delivery.
  • Failing to review rules after carrier contracts, seasonal surcharges or marketplace delivery promises change.

Manual carrier choices vs. ChannelDock Shipping Rules

Manual decisions can work when volume is low. They become inconsistent when orders span marketplaces, countries, weights and carrier contracts.

Without ChannelDock

  • Packers choose carriers from memory or open multiple portals to compare options.
  • Weight, destination and marketplace promises are checked too late in the workflow.
  • Exceptions depend on the operator, so service quality changes from shift to shift.

With ChannelDock

  • Shipping Rules choose the carrier by destination, weight, service promise and operational constraints.
  • Rules sit next to label printing, Pick & Pack and order workflows so exceptions are visible before dispatch.
  • Operations can review and adjust routing logic without retraining every packer.

Explore Shipping Rules →

Shipping rules by weight and destination FAQ

Start by grouping orders into lanes, define weight bands, add destination conditions, choose the preferred carrier service for each combination and test the rules with real historical orders.

At minimum you need destination country, parcel or SKU weight, package type, carrier service, delivery promise and any marketplace-specific requirements. Dimensions, pickup points and insurance rules make the setup stronger.

Not always. The best rule chooses the cheapest option that still meets the delivery promise, tracking requirement, cutoff time and parcel restrictions for that order.

Review them monthly and whenever carrier contracts, surcharges, marketplace SLAs, packaging formats or warehouse cutoff times change. Peak season deserves an extra check.

Yes. Marketplace, country and service promise can be part of the routing logic, so bol.com, Amazon, Shopify and other channels can follow different carrier rules where needed.

Route the order to a hold or exception queue. Missing weight, address or service information should be fixed before a label is created.

Related workflows to improve next

Once your routing rules are stable, tighten the surrounding shipping and packing workflows.

Compare carrier rates

Balance price with delivery promise before choosing a service.

Read the how-to

Print shipping labels

Turn routing decisions into clean labels and tracking updates.

Read the how-to

Integrate Dutch carriers

Connect PostNL, DHL and DPD in one shipping workflow.

Read the how-to

Pick & Pack

Verify the right products before the selected carrier label is attached.

Learn more

Set shipping rules once, then let every order follow them

Use ChannelDock Shipping Rules to route orders by weight, destination and delivery promise before the packing bench prints the label.