Company SKU vs Factory Model Reference: Ride-On Sourcing

Which fields belong on an RFQ line item

Build the line so a purchasing clerk, a QC inspector and a customs broker can all read it without asking a question. One row per sellable variant: your company SKU, the factory model reference exactly as the factory writes it, the market variant, the configuration reference, the core size, and units per carton. Add an evidence column with the snapshot date the record came from, because factory references and configurations change and you need to know which version you quoted.

Two rules keep the row honest. Record the market variant per line rather than assuming one global spec — a quote variant captured for one region is a record of that quote, not proof the configuration ships everywhere. And never resolve a gap by inference: if the configuration string implies a battery or motor figure but the parsed fields say not supplied, leave it blank and ask. That blank is a supplier question, not a data-entry error.

If your catalog already carries a structured product record for the same vehicle — the Electric Off-Road SUV Ride-On platform is one of the SKUs in the snapshot below — compare the RFQ row against that record field by field before you send it. The comparison is what turns a quote into a purchase order.

Documents before the shipment moves

Step 1 — Quote confirmation	Document: signed quotation or PI showing company SKU and factory model reference on the same line | Who provides it: supplier, countersigned by you | Hold if missing: yes — without both identifiers, the order is not traceable to a quoted configuration
Step 2 — Order confirmation	Document: purchase order stating SKU, factory reference, market variant, configuration reference, units per carton | Who provides it: buyer | Hold if missing: yes — the PO is what the factory builds to
Step 3 — Pre-shipment inspection	Document: inspection report referencing the factory model reference and the quoted configuration | Who provides it: third-party inspector or your QC | Hold if missing: depends on your contract terms; do not treat a photo set as an inspection report
Step 4 — Customs entry	Document: commercial invoice and packing list with HS code, declared value, carton count and weights | Who provides it: supplier, checked by you or your broker | Hold if missing: yes — mismatched invoice and packing list is a classic clearance hold
Step 5 — Destination compliance	Document: the conformity documentation applicable to the destination market and product category | Who provides it: supplier, verified by you | Hold if missing: yes for markets that require it; applicability is market- and category-specific, so confirm from the official text rather than a supplier summary
Step 6 — Release to your warehouse	Document: packing list reconciled against received cartons, with SKU-level counts | Who provides it: your receiving team | Hold if missing: no, but unreconciled counts are how variant mix-ups reach your retail customers

The one gap that stops the box

The document that most often holds a container is not the certificate — it is the commercial invoice and packing list that disagree with each other. The invoice names the product under your company SKU; the packing list was generated from the factory's model reference. Carton counts or descriptions do not reconcile, the broker queries the entry, and the box sits while you email three people to explain that the factory reference and your SKU are the same vehicle.

The fix is procedural: require the supplier to print both identifiers on the invoice and the packing list, and make the carton marking match the factory reference the inspector saw. Then ask your forwarder to confirm the entry description before the container sails. Ask the supplier in writing: which model reference will appear on the invoice, which on the carton, and do they match the configuration we quoted? If the answer is vague, that is the hold, three weeks early.

Worked example (illustrative, not a real shipment)

A buyer orders a mixed container of ride-ons: roughly 300 units across three SKUs, split between two destinations with different packaging requirements — one market needs a revised carton marking and a destination-specific document set, the other does not. The RFQ rows are correct, the quote is signed, and the factory reference is written exactly as the factory gave it. During pre-shipment, the inspector reports the carton marking shows the factory model reference but not the buyer's SKU. The buyer's warehouse can receive that; the buyer's customs entry cannot describe it that way, because the invoice is issued under the company SKU.

The container is held at the document step, not the production step. Recovering it means reissuing the packing list to carry both identifiers and getting the supplier to confirm the carton marking for the second destination, where the packaging revision was never formally approved in writing. Two rules would have prevented it: the market variant belongs on the line, and no packaging revision counts until it is confirmed in writing against a specific SKU.

FAQ

Should my company SKU ever contain the factory model reference?

No. Use the factory reference as a product field on the record, not as the code itself, because buying the same product from two suppliers with different part numbers splits your inventory into two products. Keep the SKU short, consistent and readable, and store the factory string alongside it.

One factory reference lists three style variants — do I create three SKUs?

Create a separate SKU for each distinct sellable variant, because every variant needs its own code for stock control and returns tracing. If the three styles ship as one assortment under one retail listing, one SKU with the variants recorded as attributes can work, but confirm with the factory whether each style can be ordered and packed independently.

The quote says the battery and motor references are not supplied, but the configuration string shows figures. Which do I trust?

Trust neither until the supplier confirms in writing. A configuration string is a factory shorthand; a parsed field marked not supplied is an open item. Ask the supplier to state the confirmed battery and motor references for that SKU in the quote revision, and do not carry the inferred figure into your catalog record.

Does the factory reference have to appear on the commercial invoice?

The invoice must carry the identifier your customs entry describes. Print both the company SKU and the factory model reference on the invoice and packing list, so the entry description, the carton marking and your internal record reconcile without a query.

How often should I re-verify the factory reference for a SKU I already buy?

Re-verify at every quote revision, and whenever you add a market variant or approve a packaging change. Factory references and configurations change; the snapshot date on your record tells you which version the price and the specification belong to.

Can I reuse a retired SKU for a new ride-on variant?

No. Retired SKUs should stay retired, because purchase orders, returns and supplier records reference them, and reuse destroys the audit trail. Issue a new code and keep the old record closed.

Sources

• how to use sku effectively for your business
• sku vs model number
• stock keeping unit sku best practices for inventory classification
• what is a sku how to create sku codes 2026

Related Products & Categories

• Electric Cars & SUVs
• Drift Cars & Go-Karts

Next step

If you are building the RFQ for a ride-on program, start with the Electric Cars & SUVs range to fix your SKU structure against real configurations, then issue the RFQ with both identifiers on every line.

Continue the buying conversation

Compare the ride-on range, packing references and product files before requesting a quotation.

Explore the ride-on range ↗