If two RC stunt cars in your supplier's catalog both say "2.4G", "double-sided" and "360 flips", treat them as two separate purchase records until the SKU proves otherwise. For an CarToySupplier distributor, the practical rule is simple: the SKU is the buying key, the product name is only a description. In CarToySupplier's scoped catalog snapshot dated 2026-10-09, two stunt models carry near-identical descriptive titles yet distinct SKUs and distinct reference prices — ctslh-c026s-3 at USD 10.35 per piece and cts1601104150049 at USD 8.71 per piece. Merging them by title similarity would corrupt your picking, costing and reporting before a single carton ships.
What the 2026-10-09 scoped snapshot actually records
This is a catalog observation of a limited snapshot, not a market survey and not category-wide sales evidence. The snapshot records four stunt and off-road RC entries, each tied to its own SKU and reference price. Everything else — material, packing, reference MOQ, units per carton, size and weight — is not recorded for these entries and has to be confirmed per project.
Read the table below as a record of what the catalog states, nothing more. A reference price is not a quote, and a descriptive title is not a specification.
| ctslh-c026s-3 — 2.4G remote control car, 360 rolling, double-side running, watch/hand control stunt | Reference price USD 10.35 per piece; material, packing, MOQ and units per carton not recorded |
|---|---|
| cts1601104150049 — 2.4GHz 1/26 stunt RC car, high speed, double-sided 360 flips, monster styling | Reference price USD 8.71 per piece; material, packing, MOQ and units per carton not recorded |
| cts1601104211077 — 1:26 2.4GHz 4WD off-road stunt RC, double-sided 360 flips | Reference price USD 8.71 per piece; material, packing, MOQ and units per carton not recorded |
| cts1601193377692 — double-sided high-speed electric RC stunt car, 360 rolling drift, 2.4GHz climbing | Reference price USD 5.80 per piece; material, packing, MOQ and units per carton not recorded |
Why title similarity breaks distributor programs
Four records, four SKUs, and at least three of them read like the CarToySupplier: 2.4GHz, double-sided, 360 flips. That overlap is normal in RC catalogs, because the descriptive vocabulary of the category is narrow — scale, frequency, stunt type, terrain. The names converge; the products and their costs do not.
Operational guidance from fulfillment and catalog-management practice is consistent on this point: every product and variant should carry a unique SKU, because similar names, sizes, colors, bundles or packaging configurations otherwise cause picking and reporting errors ChinaDivision. A second publisher frames the same risk from the catalog side — duplicate items, inconsistent names and constant SKU confusion are the predictable output of a loose catalog structure, and variants should be grouped under one parent item rather than duplicated Kladana.
For an RC program the failure mode is concrete. Your ERP receives two line items called "2.4G stunt car, double-sided 360". A warehouse picker grabs whichever carton is closer. Your margin report blends a USD 10.35 reference with a USD 8.71 reference and produces an average that matches neither. Your reorder trigger fires on the wrong record. None of this requires a defective product — only an ambiguous name.
| Duplicate-name risk | Two catalog records collapse into one internal item; the cheaper reference silently subsidises the dearer one |
|---|---|
| Picking risk | Wrong carton shipped against a correct order line because the description matches both |
| Reporting risk | Blended cost, blended sell-through and unreliable reorder points per model |
| Document risk | Test reports, warnings and age marks attached to the wrong SKU in your file set |
How to build a per-SKU decision record before you quote
Start with the fields the snapshot does not carry. Material, packing format, case pack, reference MOQ and units per carton are unrecorded for these entries, and both catalog pages state that MOQ and case pack are confirmed with the packaging and production route rather than fixed on the page. Put target quantity and destination in the RFQ, because those two variables drive the answer.
Then separate the specification questions from the commercial ones. Control method, battery route and included items belong to the specification side and should be confirmed per SKU before quotation — a watch-style hand controller and a standard handset are different products with different accessory counts, even when both say "2.4G". Packaging, case pack, MOQ, documents and shipping basis belong to the commercial side.
Keep one file per SKU. Sample comments, artwork changes and label revisions should stay attached to the same SKU throughout, or you rebuild the ambiguity you were trying to remove. If you run a periodic catalog review — monthly is a common recommendation for smaller operations, plus a pass after any major stock event — check that no two live items share a name without a distinguishing variant field.
| Specification checks per SKU | Control method (handset vs watch-style), battery route, included items, scale, terrain type |
|---|---|
| Commercial checks per SKU | Current quote at target quantity, packing format, case pack, MOQ, units per carton, shipping basis |
| Document checks per SKU | Test reports, warnings, age marks and packaging files for the selected SKU and destination market |
| Internal checks per SKU | Unique item code, parent/variant grouping, no duplicate name without a variant attribute |
Documents and age marks follow the SKU, not the catalog
A common and expensive assumption is that a supplier's certificate set covers the range. It does not. Test reports, warnings, age marks and packaging files are tied to the selected SKU and the destination market, and the current file set has to be requested with the enquiry. A file that supports one stunt model does not automatically support its neighbour, even when the two share a frequency band and a stunt description.
For US-bound shipments, the importer issues the Children's Product Certificate CarToySupplier made abroad and remains legally responsible, relying on tests from a CPSC-accepted third-party lab plus periodic testing Allied CHB. Since 8 July 2026, certificate data for CPSC-regulated products must be filed in ACE with the entry, in full or by reference to a certificate in the CPSC Product Registry. Toys classified in HTS 9503.00.00 are not on the Section 301 China lists, but since 24 July 2026 they pay a 12.5 percent Section 301 forced labor duty. Rates and CBP procedures change, so confirm them in writing per shipment rather than carrying a figure forward from an old quote.
None of that is a statement about any specific SKU in this snapshot. It is the reason your RFQ should name the SKU and the destination market together — a document request without a destination is not a document request.
A worked comparison: two stunt SKUs, two different buying decisions
Take the two records that collide most obviously on name. ctslh-c026s-3 is described as a 2.4G remote control car with 360 rolling, double-side running and watch or hand control, at a reference price of USD 10.35 per piece. cts1601104150049 is described as a 2.4GHz 1/26 stunt RC car with high speed, double-sided 360 flips and monster styling, at a reference price of USD 8.71 per piece.
The names overlap on frequency, stunt type and orientation. The records do not overlap on identity, and the reference prices differ by roughly 19 percent. If you are buying for a stunt-focused assortment, the lower reference sits on the 1/26 monster-styled model; if the watch-style controller is the feature your shelf needs, you are looking at the other record. Neither conclusion is a recommendation to buy — both prices are catalog references and must be re-quoted at your quantity, packaging and destination.
The decision rule that survives contact with a real program: never let a title similarity decide which record you order from. Decide on the SKU, then confirm the fields the snapshot leaves open.
Buyer questions on repeated RC product names
Can I use the product name as the order reference if the SKU is long?
No. Use the SKU as the order and receiving key and keep the descriptive name as a secondary label. Long or awkward codes are a formatting problem you solve in your own system with a short internal alias mapped one-to-one to the supplier SKU — not by ordering on a name that several records share.
Are the USD 10.35 and USD 8.71 figures current prices?
They are catalog reference prices recorded in the 2026-10-09 scoped snapshot. They are not quotes and not guaranteed at any quantity. Confirm the current quote per SKU with your target quantity, packaging and destination included in the request.
Why are MOQ and units per carton missing from the catalog records?
Because for these entries those values are confirmed with the packaging and production route rather than published as fixed numbers. Treat them as open fields to close in the RFQ, not as zero or as an assumed default. A carton quantity, where one is later confirmed, is a packing fact — it is not automatically an order multiple unless the supplier states a full-carton restriction.
Do the certificates for one stunt model cover the others?
No. Test reports, warnings, age marks and packaging files are tied to the selected SKU and destination market. Request the current file set for each SKU you intend to import, and keep it filed against that SKU.
How often should I re-check a distributor RC catalog for duplicate names?
A monthly catalog review is a common recommendation for smaller operations, with an additional pass after any major stock or assortment change. The check itself is quick: look for two live items whose names match without a distinguishing variant field, then either separate them or group them correctly under one parent item.
Sources
- Inventory Records: Prevent Stock Errors & Improve Fulfillment
- Organizing Your Product Catalog: Categories, Groups, and Smart Structure
- CarToySupplier: CPSC Certificates, eFiling, Testing and Duties | Allied CHB
