SKU Onboarding at a 3PL: The Item Data to Send Before Your First Inbound
Most first-week problems at a new 3PL trace back to the item master. Here is the SKU data a warehouse needs — barcodes, weights, dimensions, handling flags — and how to keep it accurate after launch.
Most first-week problems at a new 3PL are not picking problems. They are data problems that surface as picking problems: a unit that scans as the wrong product, a parcel rated at the wrong weight, a fragile item packed like a t-shirt. Nearly all of them trace back to the item master — the record the warehouse keeps for every SKU you send.
SKU onboarding is where that record gets built. Done carefully, it is a few hours of spreadsheet work before your first inbound. Skipped, it becomes weeks of exceptions and billing disputes afterward.
Why the item master drives everything downstream
A warehouse management system (WMS) does not know what your product is. It knows what the item record says it is. Every downstream decision reads from that record:
- Receiving matches the barcode on each unit to a SKU and counts against the advance shipping notice.
- Slotting uses dimensions and velocity to decide whether the SKU lives in a bin, on a shelf or on a pallet.
- Packing uses dimensions, weight and handling notes to choose the carton and dunnage.
- Rating and labeling use packed weight and dimensions to buy postage — which is where bad data turns directly into carrier adjustments on your invoice.
If one field is wrong, the error does not stay in one place. It repeats on every order that SKU appears in.
The core fields to send for every SKU
Most 3PLs provide an import template, but the substance is the same everywhere. For each sellable unit, expect to supply:
| Field | What it is used for | Common mistake |
|---|---|---|
| SKU | The ID your store and the WMS share | Different SKU strings in Shopify vs. Amazon for the same item |
| Product name and variant | Picker confirmation, packing slips | Variant (size/color) left only in the name, not in its own field |
| Unit barcode (UPC/EAN or internal) | Scan-to-verify at receiving, pick and pack | Two variants sharing one barcode |
| Unit dimensions (L × W × H) | Slotting, carton selection | Measuring the product, not the retail package |
| Unit weight | Postage rating | Using the supplier's spec sheet instead of weighing a real unit |
| Case pack quantity and case dimensions | Receiving, reserve storage | Case quantity changes between production runs |
| Handling flags | Packing rules | Fragile, liquid, battery or expiry-dated items not flagged |
| Country of origin and HS code | International and cross-border orders | Left blank until the first international order fails |
Two fields cause the most pain: barcodes and weights. Scan-to-verify is the main defense against mis-picks, and it only works if every variant has a unique, scannable code. Weight errors are quieter — the order ships, and the carrier's re-weigh shows up as a surcharge weeks later.
Measure the unit the way it actually ships
The single most useful habit in SKU onboarding is to measure and weigh a real production unit, in its final retail packaging, rather than copying numbers from a factory spec sheet. Spec sheets tend to list the product without its box, round down, or describe a pre-production sample.
A practical approach:
- Pull one unit per variant from the first production lot.
- Weigh it on a calibrated scale, to at least a tenth of a pound.
- Measure the packaged unit on its longest, widest and tallest points, rounding up.
- Record whether the unit ships in its own packaging or needs an overbox.
Many 3PLs will re-measure SKUs at first receipt anyway. That is a check, not a substitute — if their numbers differ from yours, find out why before the first order ships, not after the invoice arrives. Our guide to dimensional weight and carton selection explains how these numbers feed directly into what you pay per parcel.
Handling instructions belong in the record, not in an email
Packing instructions sent by email get read once, by one person, on one shift. Instructions stored against the SKU appear on the pack screen every time the item comes up. Anything that changes how a unit is handled should live in the item record:
- Fragile, liquid or glass contents that need specific dunnage
- Items that must ship upright or cannot be poly-bagged
- Lithium batteries or other regulated contents
- Lot or expiry tracking requirements
- Required inserts, gift wrapping or ship-alone rules
If your product line has variants that look nearly identical — shades of the same color, sizes of the same shoe — say so. Warehouses can add a secondary check, such as a photo on the pick screen, but only if they know the risk exists.
Keep the item master alive after launch
SKU onboarding is not a one-time event. Packaging changes, suppliers switch cartons, and new variants get added under old SKU numbers. A few habits keep the data honest:
- Send changes before the inventory arrives, not with it. A new case pack quantity discovered at the dock slows receiving for everyone.
- Never reuse a SKU for a materially different product. Retire it and create a new one.
- Review adjustment reports. Recurring carrier weight corrections on the same SKU usually mean the record is wrong.
- Re-verify after packaging changes, even small ones like a thicker insert.
Tight item data also makes later work easier — barcode scanning at every touchpoint depends on it, and so does accurate inventory across channels.
Before your first inbound: a short checklist
- Every sellable variant has a unique SKU and a unique scannable barcode
- Weights and dimensions come from a real, packaged production unit
- Case pack quantities and case dimensions are confirmed with your supplier
- Fragile, liquid, battery and expiry-dated items are flagged
- Bundles are defined as pre-built or virtual, with components mapped
- SKU strings match across every sales channel you connect
If you are preparing to move inventory into a new warehouse, our ecommerce fulfillment team works through the item template with you before the first container or pallet arrives, so receiving starts from clean data rather than cleaning it up afterward.