A catalog price is a hypothesis, not a quotation. Before you build a baby toy FOB price quotation checklist and send an RFQ, test every price line against two things: does it state a valid basis, and does it say what the price excludes? If either is missing, the number is not quotable — it is a starting argument.
This matters more in 2026 because the price conversation has moved. Buyers are comparing more SKUs across more packaging formats, and the compliance questions that used to arrive after the order now arrive before it. A price that cannot survive an Incoterms question or a variant question will not survive a purchase order. The worksheet below takes one catalog page and turns it into confirmed facts, labelled assumptions, and unresolved checks you can actually send to a supplier.
Key Takeaways
- A price line without a named place and a stated Incoterms version is not a basis — "FOB" alone is a category, not a location, and it is the single most common source of freight disputes after production.
- Write variant exclusions in the worksheet before you ask for a quote: packaging format, accessory count, colourway, and tooling are separate cost lines, not details to settle later.
- Button-cell toys are a compartment and warning question, not a price line. Ask about closure type, whether a tool is needed to open it, and which warning is applied — before you discuss the toy's function.
- A tooling fee does not automatically transfer the mold. Fee, ownership, storage period, and what happens if the tool sits idle belong in writing, not in a handshake.
- Label every cell confirmed, assumption, or unresolved. A worksheet full of guesses is worse than a short worksheet with gaps, because gaps get asked about and guesses get ordered.
What does a catalog price actually tell you?
It tells you one number under one set of conditions the supplier chose. That is all. A catalog line usually assumes a standard carton, a standard colourway, a standard accessory count, and a shipment arranged on the supplier's terms. Change any of those and the number moves — sometimes before you have even confirmed the order quantity.
The practical move is to treat the catalog page as a prompt, not a price. Copy the SKU, the quoted unit price, and the stated basis into a row. Then leave three columns open: basis check, variant exclusions, and label. You will fill those from the supplier's answers, not from the catalog.
One caution on scope: do not read infant suitability off a catalog category, a material name, or a product photo. Age grading and intended use are SKU-specific and need SKU-specific evidence. A plastic building set and a bath toy can sit on the same catalog page and carry entirely different intended-use statements.
Worksheet columns: what to check, and the red flag
| Price basis — is the Incoterm named? | Check: the exact Incoterms version plus the named place, written as booked (for example Shantou or Shenzhen). Red flag: "FOB" with no place, or a place that changes between the catalog and the quotation. |
|---|---|
| Variant exclusions — what is not covered? | Check: packaging format, accessory count, colourway, and whether tooling is included. Red flag: a price that "includes packaging" with no format named. |
| Quantity tier — which MOQ does the price assume? | Check: the MOQ tied to that exact unit price. Red flag: a catalog price with no quantity attached, or a tier that shifts when you confirm. |
| Button-cell compartment — gating question | Check: closure type, whether a tool is required to open, and which warning is applied. Red flag: "standard battery door" as an answer with no closure detail. |
| Tooling terms — if a fee applies | Check: fee, ownership, storage period, and disposition if the tool sits idle. Red flag: a paid fee with no written transfer or storage condition. |
| QC evidence — before shipment | Check: whether pre-shipment QC photos are provided for the order. Red flag: verbal assurance only, with no photo commitment in the order terms. |
| Age and intended use — per SKU | Check: the SKU-specific age grading and intended-use statement. Red flag: suitability inferred from the catalog category or the material name. |
| Material and colourant changes | Check: whether the supplier notifies you before changing resin, colourant, mold, process, component, sub-supplier, or packaging. Red flag: no notification clause at all. |
| Cell status — confirmed / assumption / unresolved | Check: every row carries a label. Red flag: a filled cell with no source behind it. |
How do you test whether a price basis is valid?
Ask for the Incoterms version and the named place in the same sentence. "FOB Shantou, Incoterms 2020" is a basis. "FOB" is not. A freight argument that starts because the named place was never written down can outlast the production run, and it usually surfaces at the worst moment — after the goods are packed and the forwarder needs a booking.
Then check that the basis is consistent across the documents you already hold. If the catalog says one port and the draft quotation says another, stop and resolve it before you build the request. Two different named places on two different pages is not a typo; it is an unconfirmed term.
Finally, confirm which quantity tier the price belongs to. A unit price without a quantity is a reference point, not an offer. Write the MOQ next to the price in the same row so nobody downstream separates them.
Which variant exclusions should be written down before the RFQ?
Packaging first. Blister, polybag, colour box, and display carton are different cost lines and different QC checkpoints. If the catalog price does not name the format, you do not know what you are buying. A mixed-SKU order with clear blister packaging is a legitimate pattern, but only if the blister format is written into the quotation rather than assumed from a photo.
Accessories second. Count them and name them. A building set with a die-cast alloy car component and a set with the same piece count but no alloy part are not the same purchase, even if the catalog lists them at similar sizes. The same logic applies to light and music modules, which are components that can be changed by a sub-supplier.
Colourway and mould third. A colour run is not free, and a mould is not a detail. If the price depends on an existing mould, say so. If a new mould is involved, the tooling terms belong in the same worksheet row as the price, not in a separate email thread that nobody forwards to finance.
Why is the button-cell compartment a gating question, not a price line?
Because it decides whether the toy ships at all, before price becomes interesting. For any SKU that uses a button cell, ask three questions: what is the closure type, is a tool required to open it, and which warning is applied. A compartment that opens with fingernails is a design problem regardless of how competitive the unit price looks.
This is not a pass/fail rule you can apply from a catalog page. It is a supplier question with a specific answer, and the answer belongs in the worksheet next to the SKU. If the supplier cannot describe the closure mechanism in plain terms, treat the cell as unresolved and keep it unresolved until they can.
Note also that US button-cell requirements and the door design are the same conversation — the compartment is where the rule and the product meet. That is why this check sits before the function discussion, not after it.
What should be frozen in writing if a tooling fee applies?
Four items, and all four go into the same document. The fee itself. Who owns the tool once the fee is paid. How long the supplier will store it. And what happens if the tool sits idle — who pays, who decides, and what the buyer's options are at that point.
A mold cannot be assumed transferable merely because a buyer paid a sample or development fee. That assumption is exactly how buyers end up with a paid-for tool they cannot move. Ownership, storage, and release conditions are contract terms, and a tooling policy is a document, not a handshake.
If the supplier resists writing storage years or release conditions, treat that as a signal about how other terms will be handled later. It is cheaper to resolve now than after the first production run.
How do packaging and QC evidence cross-check the price?
Ask what evidence arrives before shipment, and get the answer into the order terms. Pre-shipment QC photos are a reasonable expectation for a first order, and a supplier who commits to them in the quotation is easier to work with than one who mentions them verbally.
Incoming material inspection is the other half of the picture. Resin inspection should verify supplier, grade, colour, lot, packaging condition, and required material documents before molding. That is a process checkpoint, not a price line, but it tells you whether the supplier's cost structure is built on verified inputs or on whatever arrives.
When a defect does appear, sorting is containment, not correction. Corrective and preventive action should address the cause of the defect and verify effectiveness. If a quotation conversation includes a vague promise to "sort out any issues," that is containment language. Ask what the corrective process looks like.
Worked example (illustrative, not a real shipment)
A buyer is preparing a first order across two destination markets and two packaging formats. The catalog page lists a set of SKUs at unit prices with an MOQ attached to each. Nothing on the page names an Incoterms version, a named place, a packaging format, or an age grading.
The buyer builds the worksheet and labels every cell. Price basis: unresolved, because the catalog says only the trade term. Quantity tier: confirmed for two SKUs, assumption for the rest, because the catalog MOQ and the price tier are printed in different places. Packaging: unresolved — one destination wants blister, the other wants a colour box, and neither format is priced. Button-cell compartment: unresolved, because at least one SKU on the page may use a cell and the catalog does not say. Tooling: not applicable for existing moulds, assumption for any new colourway. Age and intended use: unresolved for every row until the supplier confirms per SKU.
Two things happen next. First, the RFQ goes out with the unresolved rows written as questions rather than as blanks — suppliers answer questions, they ignore blanks. Second, the buyer does not treat the catalog total as a budget figure. The gap between the catalog total and a quotable total is exactly the size of the unresolved column, and that column is where the order gets held at the loading dock.
What to ask suppliers (RFQ checklist)
Send these as numbered questions against the specific SKU list, not as a general enquiry. Numbered questions get numbered answers, and numbered answers drop straight into the worksheet.
1. What is the exact Incoterms version and named place for this quotation, written as it will be booked?
2. Which quantity tier does each unit price belong to, and what is the MOQ for that tier?
3. Which packaging formats are covered by this price — blister, polybag, colour box, display carton — and which are excluded?
4. Which variants, accessories, colourways, or components are excluded from this price?
5. For any SKU using a button cell: what is the closure type, is a tool required to open it, and which warning is applied?
6. If a tooling fee applies: what is the fee, who owns the tool, what is the storage period, and what happens if the tool sits idle?
7. Can you provide pre-shipment QC photos for this order, and will that commitment appear in the order terms?
8. What is the SKU-specific age grading and intended-use statement for each item on this list?
9. Will you notify us before changing resin, colourant, mold, process, component, sub-supplier, or packaging that can affect the released toy?
What the catalog alone cannot answer
Some worksheet cells are unanswerable from a catalog page no matter how carefully you read it. Age grading and intended use are not inferable from a category name, a material description, or a product photo. Button-cell presence is not inferable from a product image. Tooling ownership is never printed in a catalog.
That is the point of the labelling discipline. Leave those cells unresolved and send them as questions. A worksheet with honest gaps gets a better quotation than a worksheet filled with reasonable-sounding guesses, because the supplier can see exactly which assumptions you have not made.
Keep the worksheet with the quotation once it arrives. When the next catalog version lands with new prices, you will already have the column structure to compare against — and you will know which rows were confirmed last time and which ones were never closed.
A note on current compliance context
Two scope facts are stable and worth keeping in the worksheet header. According to ASTM F963, the standard covers objects designed, manufactured, or marketed as playthings for children under 14, subject to the standard's exclusions. The EU toy-safety Regulation covers products designed or intended for use in play by children under 14 years of age, subject to listed exclusions. Neither statement tells you whether a specific SKU qualifies — that is a SKU-level determination you ask the supplier to document.
Where an official source does not confirm an application date, write the timeline as not confirmed from official text rather than as a mandatory date. Digital Product Passport requirements and general product-safety rules are separate regimes and should not be collapsed into a single deadline in your RFQ notes.
Practical takeaway: keep compliance questions in the same worksheet as the price, because the answer can change which SKU is quotable at all.
FAQ
Is a catalog price the same as a quotation for baby toys?
No. A catalog price is one number under the supplier's assumed conditions; a quotation states the basis, the quantity tier, and what is excluded. Treat the catalog as a prompt to ask questions, not as a budget figure.
What does an FOB price without a named place actually mean?
It means the trade term is stated but the location is not, so the freight obligation is undefined. Ask for the Incoterms version and the named place written as it will be booked before you build the quote request.
Should I ask about button-cell compartments before or after price?
Before. The closure type, whether a tool is required to open it, and the applied warning determine whether the SKU is shippable at all. A competitive unit price on a compartment that opens with fingernails is not a usable price.
If I pay a tooling fee, do I own the mold?
Not automatically. A mold cannot be assumed transferable merely because a buyer paid a sample or development fee. Fee, ownership, storage period, and idle-tool disposition should all be written into the agreement.
How do I handle two packaging formats for the same SKU?
Price them separately. Blister, polybag, colour box, and display carton are different cost lines, and a catalog price that does not name the format does not cover either one. Write both formats into the RFQ as distinct rows.
What is the minimum I need before sending an RFQ?
A SKU list, the quantity tier you are targeting, the destination markets, and the packaging format per destination. Add a labelled worksheet with confirmed, assumption, and unresolved cells so the supplier sees exactly which terms you have not assumed.
Can I infer a baby toy's age grading from the catalog category?
No. Age grading and intended use are SKU-specific and require SKU-specific evidence. Do not infer infant suitability from a category name, a material description, or product imagery — ask for the intended-use statement per SKU.
Sources
Build the worksheet before you build the quote
Send the RFQ with the unresolved rows written as numbered questions, and keep the worksheet attached to the quotation when it comes back. The next catalog revision will land with new prices, and the column structure you build now is what lets you compare them without re-reading every page from scratch.
If you are preparing a first order across multiple destination markets, start with the columns in this article: basis, exclusions, quantity tier, gating checks, tooling terms, QC evidence, and label. Everything else can be added once the supplier answers.