Two suppliers quote a 2 ml empty AIO. Supplier A is eight cents cheaper. Supplier B includes retail packaging, a configuration-matched battery document and an identified production sample. Supplier A lists “standard packaging,” leaves the battery model blank and reserves the right to use an “equivalent” component. Use the template whether you are quoting wholesale 510 cartridges or disposable AIO hardware.
Which quotation costs less?
At this stage, the question has no defensible answer. The quotations do not describe the same object, the same evidence package or the same commercial boundary. Comparing their unit prices would turn missing information into an imaginary saving.
A useful vape hardware RFQ does more than collect prices. It gives every bidder one controlled baseline, forces differences into visible exception fields and returns answers that procurement, product and quality teams can compare without reconstructing the offer from emails and calls.
This guide shows how to build that comparison. It applies to empty 510 cartridges and empty disposable AIO hardware. It does not prescribe one universal MOQ, lead time, sampling plan or compliance-document list. Those decisions depend on the configuration, project, destination and buyer’s own requirements. To define the project route before writing the RFQ, see how white label and OEM programs differ.
Start with the unit of comparison
Before listing questions, write one line that identifies what the supplier is being asked to quote:
RFQ EH-027, Revision A: 2 ml rechargeable empty AIO, configuration requirements attached, 5,000 units in one approved color, logo decoration and defined retail pack, quoted to the named delivery basis and destination, with declared exceptions.
That sentence serves as a control line connecting the RFQ revision, product format, quantity, customization state, packaging state and commercial basis. The detailed specification remains a separate controlled record.
Without it, one supplier may quote a blank device in a tray while another quotes decorated hardware in an individual carton. One may assume a catalog battery and another a buyer-specified cell. Both can honestly call their offer a “2 ml AIO,” yet their prices answer different questions.
Use one RFQ revision for every bidder. If the requirement changes during quotation, issue a new revision and state what changed. Do not quietly correct one supplier’s email while leaving the others on the earlier basis.

A fictional example: two complete-looking quotes
The comparison below is an editorial example. The suppliers, prices and specifications are fictional; they are not ILEVA customer, supplier or quotation records.
| Quote field | Supplier A | Supplier B | Why the row is not yet comparable |
|---|---|---|---|
| Product description | 2 ml ceramic AIO | Model B-20, 2 ml AIO, Rev. 3 | A does not identify a controlled configuration |
| Capacity | 2 ml | 2.0 ml nominal; usable-fill basis and tolerance stated | The same headline capacity may conceal a different measurement basis |
| Heater/resistance | Ceramic, 1.2 ohm | Heater construction identified; 1.2 ohm with tolerance | A nominal value without tolerance is incomplete |
| Battery | 350 mAh rechargeable | Named 350 mAh battery type mapped to the device revision | A rating alone does not identify the installed battery |
| Closure | Press-on | Press-on geometry per drawing reference | The words match; the controlled interface does not |
| Decoration | Logo included | One-color print at approved location; artwork setup separate | Scope and setup treatment differ |
| Packaging | Standard | Tray, individual carton and master-carton quantities defined | The unit prices include different packed states |
| Inspection | QC included | Inspection basis to be agreed; report reference requested | “QC included” does not define characteristics or disposition rules |
| Freight basis | FOB | FCA named place, Incoterms 2020 | The risk, cost and delivery points cannot be compared from the acronyms alone |
| Substitution | Equivalent parts may be used | Exceptions require written approval | A reserves an undefined configuration change |
The correct response is to return the unresolved rows for clarification before scoring either supplier. Supplier A may be able to supply the same controlled build. Supplier B may have included a cost the project does not need. Normalization makes those differences visible before the buyer interprets them.
Record 1: freeze a configuration baseline
The baseline should contain enough information to stop suppliers from choosing materially different interpretations. For a 510 cartridge, fields may include capacity, reservoir and oil-contact materials, center-post or postless architecture, heater, resistance and tolerance, intake geometry, thread and contact interfaces, mouthpiece and closure, finish, filling conditions, cap timing and packaging state.
An AIO adds battery and control interfaces: battery rating and identity requirements, activation method, charging interface, output or voltage settings, preheat, display behavior, housing and tank configuration.
Separate four kinds of statement:
- required value: the supplier must meet it;
- allowed option: the supplier may select from a declared set;
- target with tolerance: variation is allowed inside a defined range;
- supplier proposal: the supplier must state the offered value for review.
“Ceramic coil” is usually a supplier label, not a complete baseline. “1.2 ohm” is a nominal value unless its allowed range and measurement basis are understood. “Heavy-metal-free” is not a substitute for identifying materials, test scope, sample identity and acceptance basis.
If the buyer does not yet know a value, do not disguise the gap as standard. Mark it as supplier to propose, state the intended decision and require supporting information. Honest uncertainty is easier to control than false precision.
Buyers who need to determine whether a supplier can maintain the chosen configuration through production and reorders should continue into the vape hardware supplier qualification checklist. The RFQ makes offers comparable; it does not qualify the organization by itself.
Record 2: require a response-and-exception matrix
Do not ask a supplier to reply “confirmed” to a long specification. Give every requirement its own response field:
| Requirement ID | Buyer requirement | Supplier response | Evidence/reference | Exception or clarification | Status |
|---|---|---|---|---|---|
| CFG-04 | Resistance and tolerance | Offered value | Datasheet/drawing reference | None or stated difference | Open/accepted/rejected |
| PKG-02 | Individual carton revision | Included/not included | Packaging quote/dieline | Setup or MOQ dependency | Open/accepted/rejected |
| QLT-03 | Inspection basis | Proposed plan | Procedure/report reference | Requires buyer agreement | Open/accepted/rejected |
| CHG-01 | No material or component substitution without declared review | Confirm process | Change-control procedure | Proposed seal material differs; impact data attached | Open/accepted/rejected |
This structure prevents three common failures.
First, it separates conformity from silence. A blank cell is an unanswered requirement, not acceptance.
Second, it separates a promise from its reference. A supplier can state that a document is available while identifying the title, issuer, date, report number and configuration scope. Procurement can then see whether the evidence concerns the quoted hardware or merely a related product family.
Third, it makes substitutions reviewable. The buyer prepares the requirement and decision fields; the supplier completes the offered value, evidence and exception fields. If a supplier proposes another seal, intake, cell, finish, charge board or packaging material, the response should identify the affected field and the proposed difference. “Equivalent” is a conclusion; the matrix needs the facts behind it. The RFQ should also require the supplier to declare its engineering-change notification process, agreed notice periods and required records before any future revision is evaluated. The notice period must be negotiated for the actual program rather than copied as a universal number.
Record 3: normalize the commercial scope
Evaluate unit price inside a defined cost structure. Ask each supplier to separate:
- unit price by the exact quantity, SKU, color and decoration assumption;
- tooling, fixture, non-recurring engineering, setup or artwork charges, together with ownership, maintenance, storage and any exclusivity terms for buyer-funded molds or tools;
- sample and prototype charges;
- device decoration and custom finish;
- retail packaging, inserts, accessories and master cartons;
- inspection, third-party testing or document charges when applicable;
- freight, insurance, duties, brokerage and battery-handling assumptions;
- payment milestones, currency and quote-validity date.
Do not force every project into one “landed cost” formula if the inputs are still conditional. Instead, compare costs in layers:
| Normalization layer | Decision question |
|---|---|
| Hardware | Are the quoted devices the same approved configuration? |
| Customization | Do the prices include the same logo, finish and artwork scope? |
| Packaging | Are both suppliers quoting the same packed state and quantities? |
| Evidence and quality | Are the requested inspection and document activities included or excluded? |
| Delivery basis | Which party carries each relevant transport obligation, cost and risk, and from what named point? |
| Cash and timing | When are setup, deposits, balances and other charges due? |
For example, a quote described only as device + logo, FOB cannot yet be aligned with an offer that includes the approved device revision, printed carton, inspection activity and delivery to a named point. Normalize both responses into the same hardware, decoration, packaging, quality, delivery and payment rows first; any blank or conditional row remains open instead of being forced into an artificial total.
If an Incoterms rule is used, record the rule, named place or port and edition. ICC’s Incoterms rules allocate defined responsibilities, costs and risks between buyer and seller around delivery and transport. Hardware scope, inspection plans, payment terms and charges outside the chosen rule still require separate agreement. An isolated FOB or DDP entry leaves the offer incomplete for comparison because the named point, edition and relevant terminal, customs, insurance or ancillary-cost assumptions remain unstated.
Lead time needs the same discipline. Ask what event starts the clock and which gates are excluded: requirement freeze, artwork approval, sample approval, material availability, production scheduling, inspection, factory release and transport are different intervals. A dated estimate for one defined project is more useful than a universal promise copied into every RFQ.
Record 4: map evidence to the decision it supports
An RFQ should request a bounded evidence set, with each record answering a defined question for the quoted configuration.
For every requested record, capture:
- document or record title;
- issuer and responsible organization;
- issue date and unique identifier;
- model, component, sample or product family in scope;
- revision or effectivity where relevant;
- the question the buyer intends to answer;
- any unresolved mapping between the evidence and the offered build.
For a battery-containing AIO, a UN 38.3 test summary may be relevant to the installed lithium cell or battery type. The review must connect that identity to the quoted AIO configuration. The UN 38.3 test-summary guide for disposable AIO hardware explains that traceability check. The existence of a PDF does not establish formulation compatibility, device performance, packaged-product durability or every transport and market obligation.
If acceptance sampling will be used later, do not write only AQL inspection. ISO 2859-1 provides AQL-indexed sampling schemes for lot-by-lot inspection by attributes, but the buyer and supplier still need to define the lot, applicable standard and edition, inspection level or plan, defect catalogue, methods and disposition rule. The AQL sampling-plan guide for empty vape hardware covers that later lot-decision process.
Use decision states that preserve uncertainty
A comparison can preserve unresolved information through four decision states:
- Comparable: the suppliers answered against the same baseline and material commercial scope.
- Comparable with declared exceptions: differences are visible and can be valued or technically assessed.
- Clarification required: missing or ambiguous information prevents comparison.
- Unsuitable for the defined request: the offered configuration or terms do not meet a requirement the buyer has decided is necessary.
Keep commercial and technical decisions separate. Procurement may prefer a price structure while product or quality review keeps a configuration exception open. A total score can hide that conflict. A decision record should show what remains open, who owns it and which event blocks sample selection or the purchase order.
Do not let the RFQ approve the hardware
A supplier response is a proposal. A selected quote is a commercial and technical starting point. Neither proves that the hardware will perform with the buyer’s formulation, filling process, closure conditions, battery use, package or distribution path.
The selected configuration should move into controlled sample identification and testing. The supplier should state whether production will match that reference and declare any difference before the buyer relies on the results. The lifecycle then proceeds through separate gates: RFQ evaluation, supplier qualification, sample approval, lot acceptance and shipment release. Passing one gate does not approve the next. The purchase order, inspection records, deviations and release file should continue to use the same identity chain.
For a defined branding, White Label or factory-development requirement, buyers can use ILEVA’s empty vape hardware White Label and OEM project route after the RFQ baseline is ready. Buyers who instead need currently stocked disposable hardware for direct purchase should use the bulk disposable vape inventory collection and confirm the exact SKU, configuration and current availability rather than forcing a custom RFQ onto an inventory purchase.
The best quotation is the one you can reconstruct
A strong RFQ gives negotiation a visible baseline.
Months later, a different buyer should be able to answer: What did we request? What did the supplier offer? Which exceptions did we accept? What did the price include? Which sample and evidence supported the selection? What must remain unchanged—or be reviewed—before the reorder?
If those answers live only in inboxes and calls, the quotation was never fully normalized. When the configuration, commercial scope, evidence and exceptions share one identity, price becomes useful again: it describes a known offer instead of pricing an assumption.
Source and scope note
This article uses current ICC Incoterms resources, the official ISO 2859-1:2026 overview and the UNECE Manual of Tests and Criteria framework as bounded references for commercial terms, acceptance-sampling context and lithium-battery evidence. Where a standard applies, the buyer and supplier should identify the agreed edition in the applicable specification or contract because project and contractual references may differ from the current edition. This is a buyer-side RFQ and quotation-comparison method for empty vape hardware; it does not provide legal, customs, regulatory or dangerous-goods advice. Requirements must be confirmed for the actual configuration, contract, destination and shipment.




