Kids ATV RFQ Template: What Wholesale Buyers Should Send

1. Start with the buying decision and destination

Describe who will import, distribute, sell, assemble, and support the product. Name the countries and channels rather than writing “worldwide.” A store program, a parcel-delivered marketplace product, and a distributor assortment can need different cartons, languages, parts, and preparation. Give the required arrival window and explain whether the request is a trial buy, replenishment, or new private-label launch.

Separate fixed conditions from preferences. If the carton must fit an existing warehouse limit, call it mandatory. If the body color is only a preference, allow a standard-color alternative with its commercial effect. This distinction lets the factory propose an efficient solution without assuming it can change an essential customer requirement.

What to confirm before approval

• List the importing entity and countries.
• State channel, intended application, and support model.
• Mark every condition mandatory, preferred, or open.

2. Define one base platform before asking for options

Identify the electric or pedal architecture, dimensions, proposed rider fit, load target, controls, wheel construction, driven-wheel arrangement, and standard functions. For electric models include battery chemistry, voltage, capacity, charger destination, connectors, controller, and relevant modes. Request the supplier’s exact model code and revision so its answer points to a traceable product.

Use a base configuration plus priced alternatives. For example, request the standard wheel construction in the base quote and a separate EVA-style wheel option. Do not allow the supplier to mix a smaller battery, different charger, or reduced accessory set into its preferred total without stating the change. Ask for actual specifications rather than accepting “premium” or “export quality” as measurable descriptions.

What to confirm before approval

• Request a complete base configuration.
• Price each alternative as a separate delta.
• Record model codes, assumptions, and exclusions.

3. Quote quantities by sellable variant

A total quantity does not tell the factory how many colors, regional plugs, manuals, cartons, decals, or controllers it must manage. Build a grid with model, color, market, battery, charger, language pack, artwork, and quantity. Ask whether minimum orders apply to the finished model, each color, a component lot, or a custom package.

Request quantity breaks only where they reflect real purchase possibilities. If the launch could be either a mixed container or a single-model container, describe both scenarios explicitly. This helps expose consolidation costs and component minimums. Avoid collecting a large set of speculative prices that will expire before the buyer has chosen the assortment or settled the design.

What to confirm before approval

• Show quantity per SKU rather than one total.
• Ask which minimum order drives each option.
• Separate trial, repeat, and mixed-order scenarios.

4. Separate recurring cost from development and services

Ask for unit price, packaging, tooling, artwork setup, sample, testing, inspections, spare parts, export handling, freight where quoted, and any required service. State currency, named delivery point, applicable trade-rule version, price validity, and exchange or material assumptions. The aim is a normalized comparison rather than a single attractive total.

For tooling or development, request ownership, deliverables, payment stages, modification scope, maintenance, and transfer assumptions. For testing, ask what is included, which configuration is represented, and who pays if the design changes. A test-report image should not be treated as evidence that every possible variant is covered. Require unresolved evidence costs to remain visible in the quote.

What to confirm before approval

• Separate one-time and recurring charges.
• Ask what happens after a failed sample or test.
• Include price validity and named delivery point.

5. Request samples and evidence that answer the right questions

Tell the supplier what the sample is intended to prove: appearance, assembly, function, performance, packaging, documentation, or production readiness. Ask whether it uses final parts and which differences remain. Request the relevant market documentation list for expert review, without assuming that a generic certificate or one similar model establishes compliance.

Schedule technical questions before commercial selection. Factory testing methods, shipment inspection, pack-out rehearsal, component identification, and report coverage can explain a price difference more effectively than another round of discount requests. Ask for the evidence already available and a separate plan for evidence that must be created for your configuration. This avoids confusing a sales attachment with a finished approval file.

What to confirm before approval

• Define sample purpose and nonproduction deviations.
• List evidence available now and evidence still needed.
• Assign buyer review and response dates.

6. Give every supplier the same response format

Use columns for requirement, quoted specification, status, evidence, cost effect, and open action. Status can be confirmed, alternative, excluded, or pending. Require each supplier to return the same format and highlight changes. This is more efficient than interpreting different catalogs and chat threads after quotations arrive.

Close the RFQ with a short decision timetable: questions due, quotation due, sample order, sample review, artwork freeze, commercial release, inspection, and target shipment. Ask the supplier to identify the assumption most likely to change its price or schedule. Treat the response as the beginning of controlled clarification, then transfer the accepted version into the purchase order and product file.

What to confirm before approval

• Use a shared comparison grid.
• Require explicit deviation and exclusion lists.
• Carry the accepted RFQ revision into the order.

7. Worked example: apply the decision to a real order

The following scenario is illustrative. It explains a decision method rather than reporting a CubRover customer project, measured test result, certification, or completed shipment.

Imagine a distributor comparing three offers for a 12V quad program. One includes a standard battery and plain carton, another includes a larger battery and branded packaging, and the third excludes the destination charger. Ranking their totals would create a misleading shortlist.

The buyer freezes a base model, battery identity, standard wheels, regional charger, manual, carton, and inspection scope. Each supplier returns that base plus separately priced options. The apparent lowest price changes after excluded items are restored. The decision then considers sample results, evidence gaps, lead time, and after-sales support alongside price.

No universal discount or minimum order follows from this example. The useful result is a comparable decision. The winning response should remain traceable to the exact configuration, and any later cost reduction should identify the technical or commercial change that makes it possible.

Questions to include in the buyer decision brief

Convert the review into questions that the supplier can answer against one named model and order. The following prompts come from the topic-specific approval checks above. They are intentionally practical: each answer should identify the responsible party, supporting record, open condition, and date by which the buyer can make the next decision.

1. Start with the buying decision and destination: List the importing entity and countries. State channel, intended application, and support model. Mark every condition mandatory, preferred, or open.
2. Define one base platform before asking for options: Request a complete base configuration. Price each alternative as a separate delta. Record model codes, assumptions, and exclusions.
3. Quote quantities by sellable variant: Show quantity per SKU rather than one total. Ask which minimum order drives each option. Separate trial, repeat, and mixed-order scenarios.
4. Separate recurring cost from development and services: Separate one-time and recurring charges. Ask what happens after a failed sample or test. Include price validity and named delivery point.
5. Request samples and evidence that answer the right questions: Define sample purpose and nonproduction deviations. List evidence available now and evidence still needed. Assign buyer review and response dates.
6. Give every supplier the same response format: Use a shared comparison grid. Require explicit deviation and exclusion lists. Carry the accepted RFQ revision into the order.

8. Turn the review into a controlled implementation plan

A useful buyer decision has three outputs: an approved requirement, evidence supporting that requirement, and a named person who can release the next activity. Keep these connected by model, configuration, market, document revision, and effective production date. If a supplier gives a conditional answer, preserve the condition in the purchasing record rather than shortening it into an unconditional product claim.

For an RFQ, the release point is the accepted comparison version. Keep each supplier response in its original form and create a normalized summary with a visible assumption log. Do not overwrite an excluded item with an estimated allowance without preserving who supplied that allowance and whether the supplier has accepted it.

1. Approve the market and base-platform brief.
2. Issue one variant and pricing grid to all shortlisted suppliers.
3. Resolve exclusions and sample deviations in writing.
4. Compare the normalized landed offer and evidence plan.
5. Attach the accepted revision to the purchase order.

Agree evidence and acceptance before work starts

Write the review method before the sample, factory testing, document check, shipment inspection, or service exercise takes place. Specify the reference, sample selection, conditions, tools, result format, acceptance boundary, and response to a failure. This makes two quotations or results comparable and prevents teams from negotiating the meaning of a pass after money and time have already been spent.

Keep a compact, traceable decision file

Retain the original requirement, dated supplier response, model and component identity, relevant photographs, calculations, reports, deviations, approvals, and release decision. A screenshot can help communication, but retain the underlying record when it matters to the decision. Distinguish a proposed target from a measured value, an engineering sample from a production reference, and an internal check from a third-party assessment.

Use one current revision where possible. Purchasing, engineering, compliance, quality, logistics, sales, and service may need different views of the information, but they should not be making decisions from different versions of the product. When a change is approved, state the first affected batch and what happens to old materials, inventory, artwork, service parts, customer instructions, and pending shipments.

Review cost and timing together with product application

The lowest visible unit price may shift cost into testing, rework, freight, storage, retail setup, support, returns, or obsolete parts. Compare the complete customer requirement and the cost of supplying it consistently. Where a number is uncertain, show the assumption and a reasonable scenario range. Do not turn an illustrative calculation into a supplier promise or a universal benchmark for the category.

Reserve time for unresolved items. A sample modification may require another review; a component change may affect evidence; a carton revision may alter loading; a late document can affect handoff. Put the owner and decision date beside each open item. A useful schedule makes these dependencies visible instead of reporting one finish date that assumes every preceding decision will happen immediately.

Close the loop after delivery

After the first shipment or implementation, compare the approved assumptions with arrival condition, assembly preparation, actual costs, receiving accuracy, customer questions, service cases, and repeat-order results. Separate an isolated event from a recurring pattern using model, batch, channel, and time in use. When a discrepancy appears, contain the affected scope, identify the cause, implement the correction, and verify the next relevant outcome.

Primary resources for the specific source facts and frameworks discussed in this guide: International Trade Administration: common export documents; CPSC toy-safety business guidance.

Continue the related CubRover buyer workflow: product specification sheet guide; quotation comparison guide; sample approval guide.

9. Conclusion and buyer handoff

The strongest RFQ makes the decision comparable. Define the buying context, freeze a base platform, show variant quantities, separate cost lines, request relevant evidence, and keep assumptions visible until the order is released.

Before requesting a quote, share the destination market, selected product platform, target quantity, required configuration, channel, timing, and the decision you need the supplier to support. Attach the current requirement and identify open questions. This gives the factory a clear starting point for discussing samples, evidence, inspection, documents, packaging, and commercial responsibilities.