Start with the product relationship
A parent SKU can represent one assembled product, a retail set, a practical kit, a promotional bundle, or several products placed in one shipment. Those relationships are not interchangeable. Before looking for a candidate heading, write down how the customer buys the goods, how the supplier packs them, and whether the items are imported together as one unit. The short answer on multiple HS codes explains why forcing every component into one line can create a weak review record.
The four-way decision tree
Use this first-pass decision tree: Set: different articles put together for a particular need and prepared for direct retail sale. Kit: components packaged to carry out a defined activity or complete a job. Bundle: products marketed together, but not necessarily treated as one tariff set. Separate items: products shipped together while remaining separate products for the import or invoice workflow. The label alone does not decide the treatment; the facts and destination rules do.
Collect component facts before reviewing a heading
Create one row for every child component. Record the component SKU, plain description, main material, function or use case, quantity, unit or allocated value, country of origin, and whether it is separately packaged. If one component is powered, contains a battery, touches food, or changes the product function, record that fact explicitly. The product information checklist is useful for each child row, not only the parent product.
Value allocation is a consistency check
Component values do not automatically determine classification, but they are a useful consistency check. Add the quantity and value basis used for each component, state the currency, and compare the component total with the parent product value. If the parent value is a retail price while the child values are factory costs, mark the difference instead of silently mixing the two. A value mismatch should become a review flag before an invoice is drafted.
Why essential character needs careful handling
For US tariff work, official guidance discusses General Rules of Interpretation and retail sets. A CBP ruling can examine whether goods are put up together for a specific activity and whether one material or component gives the set its essential character. That is a source-backed concept, not an automatic answer. A tool can show which facts are missing and which component has the highest supplied value, but it should not declare that component to be decisive.
Examples from ecommerce catalogs
A toiletry gift box may contain a bottle, a cream, and an accessory. A home-repair kit may contain fasteners, anchors, and a storage case. A phone bundle may contain a passive case, a cable, and a powered battery pack. A promotional gift set may contain unrelated products sold together for marketing. Each example needs a component list, packaging description, origin facts, and destination review. Use the Commercial Invoice Generator after the line structure has been checked.
Invoice wording should preserve the relationship
Avoid a single vague line such as “gift set” or “accessories.” A preparation draft can say: “Home repair kit; includes 4 steel screws, 4 polypropylene wall anchors, and 1 plastic storage box; packed for retail sale.” Keep the wording factual, preserve quantities, and do not add an HS code that has not been verified. The customs description examples guide covers the same principle for ordinary catalog lines.
Parent and child catalog fields
Keep the parent SKU, child SKU, component name, quantity, value basis, origin, and packaging relationship in separate fields. In Shopify, WooCommerce, Amazon, or a custom catalog, a parent product title is not enough to reconstruct the physical shipment. The CSV Catalog Checker can audit ordinary catalog fields, while the Amazon FBA CSV review helps identify marketplace rows that need a separate mapping pass.
Common mistakes
The most common failures are treating a marketing bundle as a tariff set, using one supplier code without checking the destination schedule, dropping child components from the invoice, mixing origin with ship-from location, using retail value for one component and factory value for another, and allowing a powered or battery component to disappear inside a generic description. Record the uncertainty and verify it rather than filling the gap with a guess.
A repeatable review workflow
Run the Composite Product / Kit HS Review with the parent facts and child rows. Review the decision path, missing facts, risk flags, value total, and invoice draft. Then use the HS Code Finder for component-level candidate preparation, check the destination tariff source, and report a correction through Corrections if a page or source note needs updating.
Source note
The US Department of Commerce explains that HS codes identify traded goods and notes that sets and composite goods can require the General Rules of Interpretation. USITC publishes the Harmonized Tariff Schedule, and CBP rulings show how a specific kit can be analyzed from its components, packaging, use, and retail presentation. These sources support the workflow; they do not make one example universal. Check Methodology and Sources before filing.