How to choose shipping box sizes for ecommerce WMS
Wrong box sizes quietly turn a good warehouse day into higher parcel costs, slower packing and damaged orders. This guide shows online sellers how to create a practical shipping-box range, connect it to product dimensions and use ChannelDock’s Picking & Packing workflow so packers choose the right carton before the label is printed.
starter range, not a carton zoo
printed on every carton shelf
dimensions + packer scan
Why this matters: Shopify Community threads show sellers struggling with one default box size for different products, while Picqer, ShipBob, NetSuite and cartonization vendors all frame packaging choice as a WMS-level decision. The operational gap is usually not the algorithm; it is missing dimensions, too many box options and packers making decisions under carrier cut-off pressure.
Before you start: box-size prerequisites
Do not start by buying ten carton sizes. Start by proving what you ship, what carriers charge for, and what packers can recognise quickly at the bench.
Export 30–90 days of orders by SKU count, item size, weight, channel and carrier service. Separate single-line orders from bundles and multi-line baskets.
Record length, width, height, weight, fragile status and “ships alone” rules for high-volume SKUs. Missing dimensions should create a data task, not a bench guess.
Give every carton a short code, shelf location and barcode. Keep void fill, labels and exception packaging reachable without blocking the main pack flow.
Step-by-step: choose shipping box sizes
Use this workflow when your ecommerce warehouse ships from its own stock, combines marketplace orders and needs a box range that works for barcode pick-pack, shipping labels and returns.
Audit what actually shipped
Pull real orders, not product-team assumptions. Group orders by one item, two-to-four items, bulky single items, fragile products, apparel, liquids, marketplace bundles and return-prone SKUs. Your first box range should fit the orders you ship every week, not the rare outlier.
Measure your top SKUs and awkward SKUs
Prioritise fast movers, high-margin products, fragile items, heavy units and products that often ship together. Enter product dimensions and weights in the product record or WMS data source. If dimensions are unknown, mark the SKU as “packing review” so the first shipment produces real data.
Choose a small starter carton range
Most growing sellers should start with envelopes or mailers, a small carton, a medium carton, a large carton and one exception size. Too many options slow down packing; too few options create wasted space and damaged goods. Name each carton with a short code such as M1, B2 or L3.
Map product rules to carton rules
Create simple rules: ships alone, no heavy-on-fragile, liquid upright, apparel can use mailer, bundle uses medium carton, gift packaging requires box not bag. Link the rules to the same order data used by pick lists so packers see the carton before they search for materials.
Test the rules at the pack station
Run 30–50 recent orders through the carton choices. Ask packers to record three outcomes: suggestion accepted, suggestion changed, or no carton fits. A WMS suggestion is ready only when packers trust it under normal cut-off pressure.
Connect carton choice to label creation
The chosen carton should determine package dimensions before the shipping label is bought. This matters for DHL, DPD, PostNL, UPS and marketplace shipping programs because parcel dimensions can affect available services, surcharge risk and customer delivery promises.
Create an exception path for odd orders
Some orders need split parcels, custom packaging or manual review. Do not hide those in normal packing. Route them to a separate bench, reason-code the override and keep the original order connected to the final label and parcel count.
Review box performance every month
Measure carton override rate, void-fill usage, damage claims, DIM-weight surcharges, pack time per order and “no carton fits” cases. Retire boxes that create confusion and add a size only when data proves repeated demand.
The practical rule: reduce choices, not control
The best box range is boring. Packers should not solve geometry while a carrier van is waiting. Give them a small, labelled set of cartons, a WMS suggestion and an exception path for odd products.
Cartonization fails in small ecommerce warehouses when it becomes a black box. It works when every suggestion is backed by clean product dimensions, a visible carton code and a packer override reason.
Common shipping-box mistakes
- Using one default box for checkout rates, label purchase and packing reality.
- Buying too many carton sizes before the order profile is understood.
- Letting packers choose boxes from memory without recording overrides.
- Ignoring product dimensions until a carrier surcharge or damage claim appears.
- Forgetting split shipments and bundles when testing carton rules.
Manual box choice vs. ChannelDock Picking & Packing
Manual packing relies on judgement at the busiest point of the warehouse. A WMS-led workflow turns product data, carton presets and scan checks into a repeatable decision.
Without ChannelDock
- Packers choose boxes from memory while orders queue up.
- Product dimensions live in spreadsheets, not in the pack flow.
- Label dimensions are corrected after carrier surcharges appear.
- Exceptions are invisible, so the same bad fit repeats next week.
With ChannelDock
- Pick-pack screens guide the packer from order to carton to label.
- Barcode checks keep SKU, parcel and packing decisions connected.
- Shipping rules can use the selected parcel context before label purchase.
- Override reasons show which carton rule needs adjustment.
Shipping box size FAQ
Related how-tos to improve next
Box-size control works best when the surrounding WMS workflows are clean too.
Make packing faster, cheaper and easier to verify
Use ChannelDock to connect pick lists, barcode checks, packing decisions, shipping labels and marketplace stock in one warehouse flow.