Develop a custom lithium battery pack by turning the device requirements into a controlled specification, building samples against an identified revision, and approving that configuration through documented device tests before production. Voltage and capacity are starting inputs. The development decision also depends on load, charger behavior, interfaces, space, environment and the evidence required for release.
For OEM procurement, each stage should end with a defined deliverable and an approval decision. This makes it easier to compare proposals, resolve sample failures and identify which later changes affect cost or qualification.
Start with the device and the purchase stage
Identify the equipment, intended application, destination markets and project stage. Distinguish a concept study from an engineering sample, a pilot release and a repeat production order. State which quantities are approved and which are forecasts. A forecast helps planning but does not replace an agreed purchase release.
Give the supplier the operating-voltage range, measured continuous load, peak magnitude, peak duration and repetition pattern. Add the required operating time and the workload used to define it. If a value is a design target rather than a measurement, label it clearly. For an existing design, include the reference drawing and charger information that your company is authorized to share.
Freeze interfaces before building a sample
The specification should describe how the pack connects to the equipment and charger. Record the connector and mating-part identification, polarity, pin functions, cable length and routing. Additional wires may have sensing, identification or communication functions; their purpose cannot be inferred from color alone.
Define the installation envelope with tolerances and cable-exit clearance. Include mounting, retention, insulation and access needed for assembly or servicing. Review operating and charging conditions separately. The supplier needs the actual charger requirements and any host communication, rather than a nominal-voltage label alone.
Classify open items as fixed requirements, options for comparison or unresolved inputs. Keep unresolved safety, charging and pinout questions out of an unrestricted sample approval. If an early prototype uses temporary parts, identify them explicitly and state which tests cannot establish production readiness.
Use stage gates with reviewable outputs
| Stage | OEM input or decision | Deliverable to agree with the supplier |
|---|
| Requirements review | Application, load, charging, space, interfaces, markets and quantities | Requirement list with assumptions, missing inputs and feasibility questions |
| Proposed configuration | Choose between documented options and resolve fixed constraints | Proposed cell configuration, protection approach, drawing and interface definition |
| Sample build release | Approve the sample revision and any temporary construction | Sample identification, configuration record, deviations and agreed test plan |
| Device validation | Run the agreed tests and review failures with engineering | Results linked to sample, host, charger, conditions and acceptance limits |
| Pilot and production release | Approve the final revision and close relevant deviations | Production specification, inspection criteria, traceability and change-control rules |
This is a purchasing and engineering framework, not a fixed MYLION lead-time or documentation promise. Agree on the deliverables, responsibility and schedule for the particular project. Specialized compliance work may have its own sequence and must be reviewed by the person responsible for the finished equipment.
Write the sample acceptance plan before shipment
A sample request should explain what the sample is intended to prove. “Please send a battery for testing” leaves the supplier without a clear basis for construction or measurement. Ask both teams to agree on the following checks and the applicable pass limits.
- Identification: sample ID, cell and pack configuration, drawing revision and any hardware or firmware identification.
- Mechanical fit: installation in the intended housing, cable routing, connector engagement and retention.
- Operation: startup, representative duty cycle, sustained load, relevant peaks and the defined operating-time endpoint.
- Charging and host behavior: intended charger, sensing or communication, termination and relevant restart conditions.
- Conditions and records: approved temperature cases, starting battery condition, instruments, repetitions and the person approving the result.
For current delivery, use a load profile that reflects the equipment. A steady bench load does not establish every pulsed or motor-starting case. The battery pack current-validation guide addresses that review in more detail. Fault and protection testing belongs in a controlled engineering or laboratory procedure; do not improvise destructive tests on an evaluation sample.
Close failures against the same revision
If a sample fails, record the requirement, actual observation and test conditions before selecting a remedy. Keep the failed sample identifiable. Determine whether the issue concerns the battery, charger, host requirement or mechanical integration; do not assume the pack alone caused every device fault.
A revised connector, cable exit, cell, protection setting or host firmware can change the scope of the original test. Give the revision a clear identity, list affected requirements and repeat the relevant checks. “The new sample works” is less useful than a record showing which earlier failure was resolved and what remains open.
Separate sample approval from production authorization
Before a pilot or production release, link the approved drawing, specification, sample configuration and test record. Agree on incoming and outgoing inspection criteria, identification and traceability. Define which substitutions require notice and approval, and how the impact on documents and qualification will be reviewed.
A cell report or a report for an earlier assembly does not automatically cover a changed pack. Request the document identity, model scope and relevant revision. Have the responsible compliance reviewer decide what applies to the battery, equipment and intended markets. Do not use a logo list as the release decision.
Keep commercial scope tied to the same revision. Separate samples, engineering, tooling, testing and production price using the custom battery quotation comparison guide. Ask what starts the agreed lead-time clock and how a requirement change affects the quote. No universal MOQ or sample schedule applies to every custom design.
Common OEM development questions
Can we select a cell format first? You can propose one, but evaluate it against load, charging, space and installation requirements. A cell format alone does not define the pack or establish compatibility.
Does one successful sample permit mass production? It supports the tests and configuration recorded. Production release also needs the agreed specification, unresolved deviations and applicable inspection and documentation requirements addressed.
What changes when we add a second supplier? Keep the reference configuration and evaluate every proposed difference. Use the replacement-pack compatibility checklist for that comparison instead of assuming equal voltage and capacity mean interchangeability.
Avis sur MYLION Exigences personnalisées en matière de blocs-batteries pour les équipements OEM, including load, protection, wiring, structure and charging requirements. Send your development brief with the device application, current drawing revision, load profile, charger details, sample objective and planned quantities. Mark the fixed requirements and remaining options so the next step is a defined technical review.