A retail product data sheet supplier should provide verified product and packaging facts for each SKU and revision, while the importer or brand owner confirms identifiers, product copy, claims, and retailer-specific fields. For metal bathroom and home-storage hardware, keep the unpackaged product, sellable unit, case, and pallet as separate records where applicable. Then reconcile each measurement and description against the approved sample, drawing, packaging specification, and the retailer’s current template before item setup.
What data should importers request from a hardware factory?
Start with a controlled SKU record, not a generic product description—the practical deliverable buyers need from a retail product data sheet supplier. It should identify the exact product variant and show which evidence supports every factory-confirmable field. GS1 guidance distinguishes consumer and non-consumer trade items and treats their dimensions and weights as data for different packaging levels; the applicable retailer schema may ask for a different subset.
For each product or variant, request:
- Buyer SKU or reference, product name, model/variant, and the approved drawing or sample revision.
- Product material and finish only as confirmed in the approved specification.
- Unpackaged product dimensions, with units and the measurement points or drawing reference.
- Net product weight, separately from any packaging weight.
- Included components and mounting hardware, with a controlled bill of materials or approved pack list where available.
- Assembly or care document reference when relevant, including its revision.
- A source and date for each value: drawing, sample measurement, approved specification, or pack-out record.
Do not treat a marketing name as a controlled product identity. “Chrome basket,” for example, may not distinguish basket width, mount type, finish revision, or included accessories. Use the buyer SKU plus a clear variant description and revision reference so the data can be tied to the item that was actually approved.
For a custom shower caddy, towel rack, wire basket, or metal storage rack, a buyer should identify important differences such as dimensions, mounting method, finish, shelf count, or included hardware. Record only characteristics that are genuinely part of the product definition. Do not ask the factory to invent retailer copy, performance claims, or compliance status to fill blank spreadsheet cells.
Why must product, retail-pack, case, and pallet data stay separate?
Packaging level matters because a product can be measured and traded as an individual item, a consumer-ready pack, an inner pack, a master case, or a pallet. GS1’s packaging-level guidance distinguishes these levels; not every product uses all of them, and each level may have its own count, dimensions, weight, and identifier.
Keep at least these separate where they apply:
| Record level | Typical data to request | Evidence to retain |
|---|---|---|
| Unpackaged product | Product dimensions, net weight, material/finish as specified, included parts | Approved drawing, specification, or measured sample |
| Consumer or retail unit | Pack contents, retail-pack dimensions, gross weight, packaging revision | Approved packaging sample and measured packed unit |
| Inner pack or case | Units per pack, case dimensions, gross weight, carton style and protection | Carton specification and confirmed pack-out |
| Pallet or logistics unit | Case count, arrangement, overall dimensions and gross weight if requested | Pallet plan or shipment pack-out record |
A retailer or marketplace may use “product dimensions” to mean a fully packaged item in a particular fulfillment context. Other item-setup templates distinguish the product from its consumer package. For example, Walmart documents schema-specific item setup fields and channel differences; treat that as Walmart guidance for the applicable channel, not a universal definition for all retailers.
Do not copy the product’s width into a retail-pack field just because a portal labels both fields “width.” Record what was measured and what the receiving template asks for. If a packaging level does not exist, mark it “not applicable” rather than reusing a different level’s values.

How should buyers verify dimensions and weights?
Define the measurement basis before comparing values. Product dimensions are not automatically the same as packed dimensions, and net product weight is not the same as gross package weight. GS1 US explains dimensions and weight fields for product data and distinguishes consumer from non-consumer trade items; use a consistent method and the exact level requested by the destination system.
For a metal bathroom accessory, record the measurement orientation and units. A buyer might define width across the outermost basket rails, depth from the wall-facing support plane to the front rail, and height from the bottom wire to the top support point. Those definitions are examples, not universal conventions; drawings or the retailer’s template may specify another method. Avoid a bare three-number entry with no indication of orientation or level.
For a packaged unit, measure the package as it will be presented or shipped in the context required by the buyer’s channel. Include protrusions or protective components when the measurement rule requires them. For a master carton, measure the assembled and closed carton rather than the flat blank. For a pallet, record the complete unit only if that level is requested and the pack-out is known.
A practical verification sequence is:
- Confirm the product revision and the packaging revision being measured.
- Use a consistent unit system and record whether dimensions are nominal, drawing dimensions, or sample measurements.
- Measure the approved physical sample or a representative pack-out using the receiving partner’s stated method.
- Record net product weight separately from packaged gross weight, including what is included in each value.
- Compare the values with the current retailer or marketplace schema and note any conversions.
- Resolve mismatches before publishing item data; do not silently average conflicting sources.
If a value comes from a drawing rather than a production sample, label it accordingly. If the pack-out is still under development, mark the value provisional and name who must confirm it. A spreadsheet can organize evidence, but it does not make an unverified measurement accurate.
Which fields belong to the factory, brand, or retailer?
Assign ownership explicitly. The factory can usually confirm the product and packing facts within its approved scope; the brand or importer owns commercial identity and channel decisions; and the retailer or marketplace defines its current submission fields and validation rules.
| Field group | Likely owner to confirm | Buyer’s control |
|---|---|---|
| Product dimensions, material/finish, included components | Factory against approved specification/sample | Confirm revision, units, and evidence |
| Retail-pack contents and pack-out | Factory and brand together | Approve artwork, components, and final physical pack |
| Case quantity and carton measurements | Factory against confirmed packing plan | Approve order quantity and shipping configuration |
| GTIN or other trade-item identifier | Brand/data owner under its GS1 and channel process | Confirm assignment and packaging-level mapping |
| Product title, copy, images, claims, and category | Brand, subject to retailer rules | Check accuracy and substantiation |
| Portal fields and channel-specific definitions | Retailer or marketplace | Check the current template for the specific channel |
This is an ownership framework, not a universal assignment rule. Contract terms and retailer workflows can change who supplies a field. In particular, do not ask the factory to assign your GTIN unless that responsibility has been explicitly agreed and the brand’s identifier process allows it. Koitor can discuss custom metal bathroom and home-storage product specifications based on drawings or samples; this does not imply that Koitor provides a GDSN data pool, retailer portal integration, GTIN allocation, or product-information-management service. A retail product data sheet supplier can confirm manufacturing facts, but the importer should identify the system owner for each remaining field.
How do importers keep one source of truth across revisions?
Use one version-controlled SKU data sheet or system record, then preserve the source behind each critical value. A useful row includes the field name, value, unit, packaging level, product or pack revision, source document, owner, verification date, and status such as confirmed, provisional, or not applicable.
Tie the record to the approved sample and purchase specification. If a basket’s wire layout, finish, suction mounting, carton insert, or unit count changes, assess which item fields may be affected. Do not assume that a minor-looking change leaves every measurement, pack count, product image, or retailer submission unchanged. Equally, do not automatically trigger a new identifier or legal conclusion from a design change; follow the brand’s identifier rules and the particular trading partner’s requirements.
For each update, preserve the superseded version and record who approved the change. This helps an importer answer a practical question later: “Which product and pack configuration did this item data describe when the order was approved?” The control is especially useful when product setup, packaging artwork, and shipment preparation involve different teams.
Koitor’s private-label bathroom accessories information can help buyers frame product and packaging discussions. For a broader view of factory customization, see Fabrication de matériel de rangement pour la maison en OEM. These pages describe relevant manufacturing scope; they do not replace retailer-specific item data instructions.
What data handoff mistakes create avoidable rework?
The most common preventable issue is not a missing spreadsheet column by itself; it is a value with no defined product, packaging level, unit, revision, or evidence. That ambiguity can surface when the buyer enters item data, prepares a retail listing, books freight, or reconciles a received shipment.
Watch for these mistakes:
- Reusing unpackaged product dimensions as retail-package or master-carton dimensions.
- Mixing net product weight with gross packed weight.
- Recording a case count without confirming whether it is units per inner pack or per master carton.
- Carrying values forward after the product, insert, carton, or pack quantity changes.
- Sending a retailer a generic factory sheet without checking its current channel schema.
- Treating a GTIN, label artwork, product description, and factory SKU as interchangeable identifiers.
- Filling unknown fields with estimates that look final.
- Asking one party to own claims, origin, compliance, or product copy without agreeing on the evidence and responsibility.
When two sources disagree, do not silently choose the more convenient number. Identify the source, check the revision, remeasure the relevant item or pack, and get approval from the field owner. If the difference affects a listing, fee, carton plan, or product acceptance, resolve it before submission or shipment.

What should an importer include in a factory data request?
Ask for evidence-linked values for the exact SKU and revision, then identify fields that the factory cannot decide on the brand’s behalf. A concise request can state:
- Product/SKU and approved product revision.
- Product description and variant attributes confirmed by the specification.
- Product dimensions with orientation, units, and measurement basis.
- Net product weight and scope.
- Included parts and pack-list reference.
- Retail or consumer-unit contents, dimensions, gross weight, and packaging revision, if applicable.
- Inner-pack and case quantity, dimensions, and gross weight, if applicable.
- Pallet configuration and measurements only if needed and confirmed.
- Source document or sample used, responsible owner, date, and provisional/confirmed status.
- Separate questions for GTIN ownership, brand content, retailer category, image requirements, and channel-specific fields.
Request the retailer or marketplace template before finalizing the sheet. The required attributes may vary by program, country, fulfillment channel, category, or template revision. As one platform-specific example, Walmart’s item setup schema documents channel-dependent requirements; importers should confirm the exact workflow they use rather than generalizing a help page to every retailer.
A well-prepared buyer brief also makes the factory conversation more efficient. Koitor Hardware is a family-owned custom metal hardware factory focused on bathroom and home storage hardware. Buyers can share drawings or physical samples, explain the target product configuration, and specify which product and packaging data they need confirmed. No unsupported dimensions, test results, or retailer approvals should be inserted to make the request appear complete.
Frequently asked questions about retail product data
What should a retail product data sheet include?
It should include the fields required by the buyer’s specific channel and the verified facts needed to describe each SKU and packaging level. Common groups include product identity, dimensions, weight, material/finish where confirmed, pack contents, case configuration, evidence source, revision, owner, and status. Check the current retailer template.
Are product dimensions the same as package dimensions?
No. Product dimensions describe the item under the applicable measurement definition; package dimensions describe a defined packed level. Retailers and fulfillment channels may define their fields differently, so state exactly what was measured and follow the specific template.
Should the factory provide GTINs?
Not by default. GTIN assignment and ownership should follow the brand’s identifier process and applicable GS1 and trading-partner rules. The factory can provide verified product and packaging facts that help the responsible brand owner maintain its item record.
What if packaging is not finalized?
Mark related values as provisional, identify the packaging revision or assumption, and name who will confirm the final pack-out. Do not present estimated consumer-pack or carton dimensions as production-confirmed data.
How often should product data be updated?
Update the record when an approved product, included component, packaging configuration, identifier, or channel requirement changes. Retain the superseded version and verify whether the change affects only one field or the broader retailer submission.
Sources: GS1 US, Add Product Dimensions; GS1 US, Packaging Levels in Data Hub; Walmart Developer, Item setup schema key points.
Need a clear product and packaging data handoff?
Share the approved drawing or sample, SKU variants, target packaging levels, and the retailer fields you need to confirm. Koitor can discuss the relevant bathroom and home-storage hardware specification and packing scope.
Fabrication pour compte de tiers / Marque de distributeur
Transformez ce guide d'approvisionnement en cahier des charges
Indiquez-nous le produit souhaité, ses dimensions, sa finition, la quantité commandée et vos exigences en matière d'emballage. Votre équipe recevra une analyse pratique de la faisabilité de la fabrication avant l'établissement du devis.



