Your supplier calls both lamps “DL-20”. Amazon calls one a white desk lamp; a dealer asks for the charcoal version. Before another marketplace joins the business, which record will its order actually select?
Prepare the sellable variant first, then connect each channel reference to it. A neat product title cannot rescue a mapping that sends the picker to the other colour or treats a six-pack as one individual lamp.
Give every sellable item a clear identity
For a multi-brand importer, start with brand, manufacturer reference, variant and selling unit together. The same model code from two represented brands is not enough to merge their products. Within one family, colour, size, capacity or another buying distinction may require separate sellable records.
Keep the group that helps a shopper browse separate from the item the warehouse fulfils. A parent listing can bring white and charcoal lamps together while each selection still needs an unambiguous item reference. Do not let the parent's general description replace the child's colour or size when the order reaches operations.
HyperInventory supports a connected catalogue, product variants and variant groups across its supported selling channels. That gives the team a place to maintain the items and their relationships rather than rebuilding an unrelated identity for every route. The channel's listing rules and the actual mapping still need a test with your products.
Match the buying unit before comparing quantities
Suppose the white lamp is sold individually on your website and as a sealed six-pack through a wholesale listing. An order for two six-packs means twelve lamps, not two lamps. A charcoal single is a third case, even if its supplier model text looks familiar.
Decide how those packs are represented in your supported catalogue and stock workflow. They may be separate stocked packs or a supported conversion against individual units. Writing “pack of six” in a title does not establish that the stock connection performs the conversion. Hold that listing until the implementation team can demonstrate its exact quantity treatment.
Where you use GS1 identifiers, retain the genuine identifier for the intended item. GS1 explains that product variations such as size and colour need their own GTIN. An internal SKU and a GTIN are different references; do not manufacture a barcode number to fill a missing field.
Test the order that is easiest to get wrong
Choose the similar-looking variants and awkward pack sizes before uploading the full range. In an authorised test environment, select the variant on the channel, inspect the received order line and compare the product, colour, pack and quantity with the warehouse's expected item.
Then check the agreed stock-posting event. If the supported six-pack workflow consumes individual stock, a two-pack order must ultimately account for twelve individual lamps. If packs are stocked separately, verify that pack balance instead. Do not accept a correct-looking channel title as evidence that either path worked.
Repeat the test for another selling route using the same item. Check that its remaining quantity reflects the configured stock relationship and update timing. This is a test of your setup, not a promise that every channel updates instantly or uses identical pack rules.
Keep a listing acceptance record
Copy one record per sellable variant and channel. It should explain why the listing is ready, rather than merely show that an upload completed.
- Brand, model and internal item reference: ______
- Variant attributes and genuine GTIN, where applicable: ______
- Channel, listing reference and parent/group reference: ______
- Customer buying unit and quantity per pack: ______
- Stock unit and supported conversion or separate-pack treatment: ______
- Test order reference and selected item: ______
- Expected versus received variant, unit and quantity: ______
- Expected versus observed stock change at the agreed event: ______
- Other-channel check and observed update timing: ______
- Accept / correct and retest / hold; owner and next action: ______
This is a decision record, not a universal upload template. Keep the channel's current required fields and your supported integration format with the accepted test.
Expand the range after the mapping earns confidence
In Tradexa, the useful connection is catalogue identity flowing into stock and orders through HyperInventory. Staff can work from the same intended item instead of translating a familiar-looking title every time a marketplace order arrives. They still own new-item approval, pack rules and unresolved exceptions.
That can leave more catalogue and warehouse attention for adding the next relevant product family or handling additional orders when identity checks are the bottleneck. It does not create demand on its own. Measure clarification cases and corrections during the pilot before assuming the next range will be easier.
For cleaning an old catalogue before migration, use the separate guide to product-record cleanup. This guide owns acceptance of a new channel listing against an existing sellable item. Start with the variants most likely to be confused, and keep the accepted mapping beside the next upload.
Example note: The lamps and two six-pack order are illustrative. Use your actual goods, authorised test path and demonstrated unit treatment.
