Buying Guide
How sellers should handle HS code conversations with buyers
By Cusket Editorial · Published · Updated
A seller guide to discussing HS codes carefully with B2B buyers without overstating import certainty.
HS code conversations can become sensitive because buyers use them for import planning, landed cost estimates, and internal approvals. Sellers often know how similar products have been described before, but final classification can depend on product details, destination rules, and the importer's responsibility. A careful seller helps the buyer evaluate the product without presenting classification as a universal guarantee.
This guide is for practical communication on Cusket. It is not legal or customs advice. Sellers should provide accurate product information and avoid promising that a specific HS code will be accepted in every destination.
Understand what the buyer is really asking
When a buyer asks for an HS code, they may be asking several different questions at once: What is the product made of? What function does it serve? Has it shipped before? What documents can the seller provide? What duty rate should they expect? Only some of these are seller-controlled.
Your first response should clarify the product and intended destination. If the buyer found the item through Cusket search, restate the exact listing and variant. Similar products can have different classifications when material, function, or component mix changes.
Provide product facts before code certainty
A seller can usually provide product descriptions, material composition, function, dimensions, packaging, and prior export description if accurate. These facts help the buyer or their import partner classify the product.
Avoid saying: This HS code is guaranteed. Prefer: For previous shipments of this product, we have used this description and code, but please confirm final classification with your import broker for your destination. This wording is honest and still useful.
Use an HS conversation table
A structured table keeps the discussion from drifting.
| Topic | Seller can provide | Buyer should confirm |
|---|---|---|
| Product identity | Listing title, SKU, variant | The exact item being imported |
| Material | Main materials and components | Whether local rules need more detail |
| Function | Intended product use | Import treatment for that use case |
| Prior shipment code | Historical code if available | Whether it applies in destination market |
| Documents | Invoice, packing list, specification | Broker or customs requirements |
| Changes | Custom material or packaging | Whether changes affect classification |
This table also helps your internal team answer consistently when several buyers ask similar questions.
Do not classify custom orders casually
Customization can affect classification. A buyer may request a different material, a bundled accessory, a kit, private label packaging, or a modified function. If the product changes, old HS code references may no longer be appropriate. Review the custom scope before repeating a previous code.
When managing custom conversations in Cusket seller products, keep the base listing separate from the custom order notes. The listing may describe the standard product, while the order thread should record the exact custom details.
Build a seller response checklist
Before replying to an HS code request, check:
- The buyer is asking about the exact listed product, not a similar item.
- Variant, material, and function are confirmed.
- Any custom changes are recorded.
- Historical code use is labeled as historical, not guaranteed.
- The buyer is encouraged to confirm final classification with their broker or import partner.
- Any document you mention is actually available.
This checklist is especially important if traffic comes from Cusket seller ads. Advertising can bring buyers from more markets, which means more variation in classification expectations.
Keep listing language classification-friendly
Listings should describe products clearly enough for buyers to evaluate them. Include material, function, dimensions, intended use, and included components where relevant. Buyers browsing Cusket categories may compare products that look similar but classify differently. Clear product facts reduce avoidable questions.
Do not stuff listings with a single HS code as if it solves every market. If you include one, label it carefully, such as Typical export reference; buyer should confirm final import classification. For many sellers, it is better to provide classification discussion in the buyer thread rather than as a universal listing claim.
Handle disagreement professionally
Sometimes a buyer's broker suggests a different code from the one you used previously. Treat that as a classification difference, not a conflict. Ask which product fact or document they need from you. You may provide photos, specifications, material details, or packing information. Avoid arguing about local customs interpretation unless you have qualified support.
If the buyer needs help using the platform, direct them to Cusket support. If they need general marketplace education, Cusket guides may help. If they need classification certainty, they likely need their import partner.
Turn repeated questions into better product data
If buyers ask about HS codes often, improve the listing data that supports classification: material, function, dimensions, components, and product photos. Stronger product data helps buyers from Cusket products make faster decisions and helps your team answer with less repetition.
A careful HS conversation protects both sides. It gives buyers useful facts while making clear who must confirm destination-specific classification.