Gummy manufacturer RFQ template with an Excel comparison workbook.

Before and after: “5,000 gummies” is not an order basis

A useful request for quotation tells suppliers which assumptions should stay the same and which questions are still open. It does not require you to pretend the whole product is already defined.

Here is a fictional first message:

We need 5,000 magnesium gummies, pectin, best price, bottles included, quick samples and delivery to New York.

This is not a real customer message. The problem is not its length; several ordinary words allow very different proposals.

A revised non-confidential brief

The values below are fictional planning inputs, not a minimum order quantity, product offer or promised commercial term.

Project: Fictional magnesium gummy concept for supplier discussion.

Quantity basis:
5,000 finished bottles, each containing 60 gummies.
Proposed serving: 2 gummies; 30 servings per bottle.
Total nominal requirement: 300,000 pieces / 150,000 servings,
before any separately stated overfill, sampling or loss assumptions.

Product scope:
Pectin direction requested. Material form, elemental amount per serving,
piece weight and full specification are not yet approved.
Please identify the exact assumptions behind any proposed option.
Do not treat this brief as approval of a formula or label.

Package scope:
60-count bottle concept. Identify proposed container, closure, seal,
label scope and any additional components separately.
Artwork is in development; state what is included or excluded.

Quality/document scope:
Identify proposed finished-product testing, specification and document
scope. Separate these from incoming-material documentation.
State what remains to be agreed before a final quotation.

Destination and timing:
New York receiving destination; exact delivery details to be confirmed
through the appropriate commercial process.
Separate sample, production and delivery assumptions.
State the event that starts each estimate and any exclusions.

Requested response:
Distinguish a budgetary estimate from a firm scoped quotation.
List assumptions, missing inputs, option differences, validity and
events that would require re-quotation.

The revised message is still not a final manufacturing specification. Its improvement is that missing facts are visible. A supplier can propose an option without silently redefining the unit, serving or package for the buyer.

Before sending: six decisions to prepare on your side

Use these prompts to prepare for the next discussion. An undecided answer is useful; an invented answer can produce a quotation for the wrong project. Keep private budgets, agreements and underlying documents out of an initial public-form message.

Check the quantity before comparing a price

Five thousand individual pieces and five thousand 60-piece bottles differ by a factor of 60. The revised example means 300,000 pieces, not 5,000. At two pieces per serving, it represents 150,000 nominal servings.

Do not translate those quantities into an available factory capacity or a delivery promise. Keep proposed overfill, sampling and yield assumptions separate rather than hiding them inside “about 5,000.”

Keep replies side by side without ranking too early

When replies arrive, first mark each as same stated basis, different option, or basis unresolved. A proposal using a different material form, amount per serving, test scope or package is an alternative concept—not automatically a cheaper quotation for the same thing.

Use the existing template below and its workbook to keep references organized. Follow the quote comparison resource only once the relevant inputs are known, and use the magnesium product page for material-basis questions. Do not fill unknown charges with invented zeros to produce a reassuring total.

Planning a U.S.-market gummy project from another country

A brand team's location, the intended retail market and the shipment destination can be different. An RFQ that says only “we are based overseas” leaves the project scope unclear. Separate these inputs before asking suppliers to compare the same request.

1. Project team: where the team is based and the working language.
2. Retail market: the intended country or countries of sale for this product version.
3. Destinations: proposed sample delivery and commercial delivery, recorded separately.
4. Responsibilities: decisions already assigned and those still requiring agreement.

A sample address does not establish the retail market. A coordination office does not identify the production location.

A clearer project brief

Fictional planning example—not a customer case or a service offer:

Our team is based outside the United States and is evaluating an English-language gummy product for U.S. retail sale. Sample delivery is proposed to our project team; the commercial shipment destination is not yet confirmed. We have a preliminary serving concept and bottle-count preference. Formula feasibility, label review, production location and delivery responsibilities remain to be agreed. Please identify your quotation assumptions and any requested work outside your scope.

Keep a market-version record

Create one row per proposed product version, not automatically one per office location. Record the version identifier, intended retail market, language/artwork version, serving, pack count, sample destination, commercial destination and unresolved decisions.

Before reusing the first specification or artwork for another market, compare the versions. Mark unknown differences “review pending,” not “same as U.S.” This is a planning aid, not a determination that a label is suitable in another country. Use the label-artwork checklist for version questions and the supplier-qualification checklist for evidence requests.

Sucotond USA handles U.S. sales and project coordination. This does not establish U.S. manufacturing, U.S. inventory or approval for a particular market. For an initial discussion, share the non-confidential product concept, intended market, serving and package preferences, project stage and open questions. Feasibility, evidence availability, commercial terms and responsibilities need project-specific agreement.

Discuss a U.S.-Market Project Brief

Identify the FSVP importer before comparing delivery terms

For food subject to FDA's Foreign Supplier Verification Program, the importer is determined under 21 CFR 1.500. The U.S. owner or consignee means a person in the United States who, at entry, owns the food, has purchased it, or has agreed in writing to purchase it. Physical receipt alone is not this definition.

If there is no such U.S. owner or consignee at entry, the importer is the U.S. agent or representative of the foreign owner or consignee, with a signed statement consenting to serve in that role. The foreign party must designate that representative before import or offering for import under 21 CFR 1.509(b). A foreign-based brand should resolve these facts, not assume that a delivery term or a U.S. delivery address identifies the responsible party.

Dietary supplements also require checking the applicable pathway in 21 CFR 1.511. Paragraph (c) applies when neither paragraph (a) nor (b) applies. It does not require the hazard analysis under § 1.504, but still requires the specified supplier evaluation and verification focused on part 111 compliance, along with the other applicable duties. It is not a blanket exemption from supplier verification or supplement manufacturing requirements. Have the responsible regulatory reviewer determine the pathway for the actual arrangement.

In the RFQ, identify the proposed importer and the facts supporting that role, who will maintain the applicable FSVP records, and who will supply the entry information required by § 1.509(a). This section does not designate Sucotond USA as the importer or replace a transaction-specific regulatory determination.

Preparing a launch before your brand details are final?

Keep your project stage separate from your product requirements. If your brand name, website or delivery address is still being finalized, mark it as pending in your initial outline. Use a working project name rather than inventing a registered business name. This planning outline is not order acceptance or a substitute for details that may be needed later.

For a launch involving more than one product, complete the product block separately for each concept. Make clear whether the pilot quantity is per product or shared across the launch.

Working project name and current stage:
Intended retail market and sales channel:

Product A / Product B (complete separately):
Ingredient direction and open choices:
Requested amount per serving; pieces per serving:
Proposed piece weight, if known:
Pilot quantity in finished containers; pieces per container:
Is the quantity per product or shared across the launch?
Packaging direction and unresolved decisions:
Texture or storage targets, clearly marked as requests:
Evidence available versus evidence still requested:

Launch dependencies and decisions needed next:
Fixed inputs versus alternatives open for discussion:

A requested temperature alone does not describe a storage evaluation: record exposure duration, packaging, conditions and acceptance criteria still to be agreed. A target amount per serving is not evidence that it can be delivered in the proposed number of pieces. Keep requests separate from measured results.

If the intended channel is Amazon US, identify it as project context; it does not establish listing eligibility or approval. Keep confidential formulas, private commercial documents and customer records out of an initial public-form message.

Use the high-load gummy project page for feasibility questions and the product specification checklist to organize open inputs. Share a non-confidential project outline for discussion with Sucotond USA, which handles U.S. sales and project coordination.