Five Fields on the Product Record That Set Every Later Bill

Most disputes about a fulfilment bill start as a dispute about a product record. Charges are calculated from fields - packed size, measured mass, pack configuration, a regulatory flag - and if those were wrong at intake, every later line inherits the error. That is the case for treating a SKU record as a controlled document, argued from the side of the ledger that builds it.

Key facts

• Five fields carry the cost structure. Measured size and gross mass, billable-weight basis, regulatory flag, commodity description, pack configuration.
• Chargeable weight takes the larger figure. Each channel compares actual mass with a volumetric figure derived from the measured cube, so a packing choice can move a charge without moving goods.
• Value-added tasks are named, not bundled. Labelling, kitting, polybagging and insert handling each have a different unit of work.
• Change control has an owner. A record change is authorised by the account, dated, and applies forward rather than rewriting received stock.

Field one and two: measured size and measured mass

These two set most of what follows, from a parcel's channel eligibility to the space it occupies on a rack. The useful distinction is declared against measured. A factory list states an intent; a bench measurement states what arrived, and the two differ when a carton is substituted, inner packaging changes, goods ride loose in an oversized box, or a product gains a thicker retail carton for a new season. A channel is matched to a measured carton rather than a model name, so a carton over a ceiling moves to a different lane with a different estimate. Require the measured figure itself, not an assurance it was taken: a dated weight on a line beats a policy claiming everything is checked.

Field three: the regulatory flag

A built-in cell, a liquid, a magnet, a food-contact article, a product class under a destination rule - each changes which channels accept the unit, and several change packing. The flag is usually wrong in one of two directions: a SKU marked ordinary because an early sample was, then a production run that carries a cell; or a SKU marked restricted out of caution and routed to a slower lane for a year at no benefit. Neither error shows on a dashboard, and both show at a booking rejection or a border inspection. The control is to re-open the flag whenever a component changes and to keep the supporting document in the record.

Field four: what the goods are, in words

The description on paperwork is what a customs officer reads, and it does two jobs: it supports the commodity code chosen, and it must match what arrives if a parcel is opened. A description copied from a marketing page fails the second test, and a vague one - accessories, gift set, household items - invites a hold however accurate the rest of the file. Two fields belong to different parties, and confusing them causes friction: the description and code on the export declaration out of China, and those on the entry at destination. Both must be defensible against the same article; where they read as different products, raise it before a line-haul booking is confirmed rather than at an inspection.

Field five: pack configuration

Units per carton, whether a retail pack is polybagged, whether a bundle is pre-assembled or built at pick time, and whether a multipack has its own identifier. This field drives the labour line more than any other, because it converts a per-unit task into a per-carton task or the reverse. A pre-assembled bundle is one pick; a bundle built on demand is two picks, an assembly and a check, and it should appear as three named things rather than one unexplained item. Where a kit is assembled here, its bill of materials belongs in the record, and a change to it - insert, carton or unit count - is a change to the SKU, not a note on an order.

How a record becomes a bill, without surprises

Read a statement as three families and the arithmetic becomes legible. Storage is space and time, priced by position or pallet, driven by measured size. Handling is work, priced per order with a per-unit addition, driven by pack configuration. Pass-through items - a labelling task, an insert, a collection arranged against a factory address, a carrier accessorial - are named events, driven by instructions. None of these families needs a published price to be auditable; each needs a unit of work and a date. This site publishes operating parameters rather than a rate card because a per-unit figure moves with lane, season and destination while the structure above does not. Collection works the same way: a chargeable leg quoted against the loading conditions at a specific address, which is why it stays as its own line instead of hiding inside freight.

Frequently asked questions

Which field should I audit first on an existing catalogue?

Measured size and mass, on the SKUs that move most. Those two feed channel eligibility, billable weight and storage occupancy at once, so an error multiplies in three places, and a high-volume line with a stale figure is quietly re-pricing every shipment. Pull your top twenty by despatch count, compare the recorded cube with what a carton measures today, and ask when the record was last verified: anything verified before a packaging change is unknown.

My supplier changed the carton. Who tells you, and when?

You do, before the next delivery rather than at the dock. A changed outer carton is a changed product record: it moves measured size, protection level and sometimes the stack pattern on a pallet. The usual failure is discovering it at goods-in through a count variance, which stalls a receipt and opens an exception file - two hours to an owner, 24 to a route - a remedy rather than a plan. Ask a supplier who repacks to state new outer dimensions and gross mass on the packing list itself, so the gap is visible at intake.

Can you bill by unit instead of by order, or hold a cap during a peak?

Both are commercial structures rather than system limits, and both belong in an agreement before a peak, not in a dispute after one. What we can state is the unit of work behind a line: one pick per order, additions per extra unit or line, named charges for assembly, storage measured against the position a SKU occupies. Where a seller wants predictability through a surge, the honest route is a stated structure with a review date agreed in writing, not a figure quoted to smooth a conversation.

Reviewed 4 November 2026 (2026-11-04). The fields, measurement point and billing families above describe how our floors work on that date; account terms sit in the service agreement rather than on this page, and no figure or rate appears above. Pick quality is reported as mis-picks under 0.01 per cent, counted line by line, across three sites totalling 24,000 square metres - Dongguan 8,000, Shenzhen 3,000, Suzhou 13,000 - run under the FulfillDock by SBT brand by a Shenzhen Shibotong International Logistics Co., Ltd. registered 2011. Related: the FAQ page, the ecommerce fulfilment service and the contact page.