A useful RFQ does more than ask for price and lead time. It fixes the application assumptions, identifies what the supplier must prove, and defines what will be checked before samples and production lots are accepted.
1. Begin with project identity and operating case
State the product, installation environment, destination market, project phase and target start of production. Then describe the actual operating pattern: expected energy per event, continuous and peak power, charge window, daily frequency, service life and exceptional cases. This is the context the supplier needs to challenge an unsuitable model.
If a model is already preferred, mark it as nominated or reference-only. A reference model can communicate format and performance expectations without silently blocking an alternative that better fits current supply or documentation needs.
2. Put electrical requirements into a controlled table
Do not use one undifferentiated ‘specification’ column. Mark each item as mandatory, target or supplier declaration, and identify the test condition. This prevents a typical value at room temperature from being read as a guaranteed limit across the full operating range.
Minimum electrical requirement block
| Field | What to state | Why it matters |
|---|---|---|
| Capacity and energy | Nominal/minimum, rating method, allowable tolerance | Controls cell count and acceptance |
| Voltage | Nominal, charge ceiling, discharge floor | Defines architecture and BMS protection |
| Current | Continuous and pulse charge/discharge, pulse duration | Sizes terminals, busbars and cooling |
| Efficiency / resistance | Method, temperature, state of charge | Supports heat and loss modelling |
| Life | Cycles/throughput, calendar target, end-of-life threshold | Connects design to warranty economics |
3. Mechanical and thermal details prevent late redesign
Request a controlled drawing, not only overall dimensions. The pack team needs dimensional tolerances, terminal geometry and torque, polarity, datum points, mass tolerance, vent location, compression guidance and prohibited load zones. State the planned orientation and ask the supplier to confirm it.
For thermal design, provide the ambient and coolant conditions the cell will actually see. Ask for heat-generation or resistance data at relevant rates and states of charge, together with recommended cell-temperature limits and temperature-difference guidance. A cooling concept cannot be validated from a maximum operating-temperature line alone.
4. Make the evidence package model-specific
List the documents required at quotation, sample approval and shipment. Typical requests include a current datasheet and drawing, quality-system information, material or restricted-substance declarations when relevant, transport-test summary, safety data, and any market or system-level evidence required by the project. The requested document must name or unambiguously cover the offered cell type.
A logo, a generic certificate or a report for a neighbouring model is not equivalent evidence. Record document number, revision, date, issuing body and the model mapping. Also state the language and whether a signed or independently issued copy is required.
5. Commercial and logistics fields need engineering input
Quantity should be split into samples, pilot lots and forecast production volumes. Include delivery destination, Incoterm request, target dates, packaging constraints, shelf-life or state-of-charge expectations on arrival, and the documents that must travel with each shipment. Ask the supplier to identify minimum order quantities, production lead time, capacity reservation, payment terms and quotation validity separately.
Price comparisons should use the same scope. Clarify whether terminals, fasteners, busbars, protective covers, export packaging, dangerous-goods handling, freight, duties and sample testing are included. Otherwise the lowest cell price may be the highest landed or integration cost.
6. Define validation, acceptance and change control
Before the first sample is shipped, agree what will be measured and what happens if a result is outside tolerance. A sample plan may cover identity, appearance, dimensions, mass, open-circuit voltage, AC or DC resistance, capacity and selected rate or temperature checks. Production-lot acceptance may use a smaller set with traceability to factory records.
Change control is equally important. Require notice for changes to material, design, manufacturing location, process, sub-supplier, firmware-related limits, drawing or critical documentation. State whether requalification is required. This keeps an approved model from quietly becoming a different technical risk after commercial award.
- Nominate the responsible person for technical clarifications.
- Use a requirements-compliance matrix with supplier comments and evidence links.
- Log open deviations and their owner before price approval.
- Do not convert a sample pass into volume approval until lot controls are agreed.
7. The final RFQ package
A compact package can contain four items: a one-page project and duty-cycle brief, a requirement table, a document checklist, and a commercial/logistics sheet. Add the drawing interface or pack constraints where available. Suppliers can then respond in the same structure, making deviations visible instead of burying them in email.
The U.S. DOE FEMP procurement checklist is written for BESS procurement rather than individual-cell purchasing, but its discipline is directly useful: define the use case, performance, safety, testing, commissioning, warranty and operations expectations as a connected procurement system. A cell RFQ should preserve that line of sight to the final asset.
REFERENCES
References used for this article
- U.S. DOE FEMP — Battery Energy Storage System Procurement Checklist↗Procurement structure and lifecycle context
- U.S. DOE — Grid Energy Storage Cost and Performance Assessment↗Performance and lifetime assessment context
Apply the framework to your project
Share the application, target model, quantity, destination and documents to be checked, and we can begin with the project boundary.
Send project requirements↗