Parcel Sizing

outline carriers price and route freight on size and weight for bulky goods, booking every return at a single default parcel size leads to under quoted consignments, rejected pickups and freight adjustments after the fact where you hold packaging dimensions per product in your ecommerce platform, refundid can use those instead of a default so a rolled 3x4 metre rug books as a 3x4 metre rug, not as a generic carton how it works when a label is requested, refundid looks up the return to see exactly which items and quantities are coming back reads the packaging dimensions and weight held against each returned variant in your product catalogue creates one carton per returned item, sized and weighed individually a return with two different items therefore books as two cartons with their own dimensions, rather than one parcel that fits neither where the dimensions come from variant level first packaging size usually differs by variant a rug in three sizes ships in three different rolls so the variant's own dimensions are always preferred product level as a fallback , for products where every variant packs the same way weight is taken from the variant's own weight in your catalogue dimensions are read from custom fields (metafields) on the variant, in a dedicated namespace with width, height and length keys values are converted to the carrier's units automatically, so it doesn't matter whether you store them in centimetres, millimetres or inches when dimensions are missing if a returned variant has no usable dimensions, the label request fails with an error naming the item and the variant, rather than booking a consignment at a guessed size this is intentional an incorrectly sized freight booking usually costs more to unwind than asking the customer to try again after the data is fixed if you'd prefer a fallback size to be used instead of the request failing, that can be configured but for bulky goods we'd generally recommend keeping the strict behaviour and filling the gaps in your catalogue what you need in your catalogue packaging width , height and length as variant custom fields, in a consistent namespace a weight on each variant your account manager will confirm the exact field names to use during setup