A supplier is preparing an approved empty vape hardware configuration for production. Before shipment, the supplier reports that one requirement cannot be met exactly for a limited quantity. Even when the proposal appears minor—a component finish, packaging material, process parameter, or dimension outside the agreed condition—the buyer still needs a controlled basis for deciding whether the exception is acceptable.
The buyer needs to decide what kind of event this is, what population it affects, what evidence is missing, and whether the exception can remain temporary without silently changing the approved baseline.
A supplier deviation request is useful when it turns that discussion into a controlled decision file. It should allow the buyer to reject the proposal, request more evidence, approve a tightly bounded exception, or route the proposal into formal change control. It should not become an informal shortcut around sample approval, production controls, or shipment release.
This article presents a buyer-side review method for empty 510 cartridges and empty all-in-one hardware. It is a practical quality and procurement framework, not a universal acceptance standard or legal determination.
Start with the approved state, not the supplier’s proposed substitute
Begin by reconstructing exactly what was approved. Only then can the buyer evaluate whether the proposed exception is acceptable.
The decision file should identify the baseline precisely enough that another reviewer can reconstruct it. Depending on the program, that may include:
- the product family and configuration identifier;
- the approved drawing, specification or controlled sample revision;
- relevant material, component, finish or packaging requirements;
- the purchase order and production stage;
- any linked test method, quality agreement or approval record.
This matters because words such as “same cartridge,” “equivalent material,” or “normal tolerance” can hide different assumptions. A 510 cartridge may share its outward format with another configuration while differing in reservoir material, center-post geometry, seal stack or interface dimensions. An empty AIO can retain the same shell while a change elsewhere affects assembly, identification or downstream filling.
The baseline is the reference point for the exception. If it cannot be identified, the buyer does not yet have a deviation decision; the buyer has a configuration-control problem.
When the approved state covers an AIO program, the record should name the exact approved empty AIO hardware configuration and revision rather than relying on a broad product category or informal product name.
Classify the request before reviewing its evidence
Not every reported difference belongs in a temporary deviation workflow.
A deviation is normally a bounded exception to the currently approved state. The proposed condition is temporary, the affected population can be identified, and the supplier is expected to return to the approved requirement when the exception expires.
Route the event elsewhere when the facts point to a different process:
- If the supplier wants the alternative to become the new normal, it belongs in vape hardware change control.
- If nonconforming product was already produced or the problem is recurring and needs systemic corrective action, the buyer may need containment and a supplier corrective action request.
- If all open requirements have been resolved and the remaining question is whether a completed lot can ship, use the pre-shipment release process.
- If the buyer cannot tell what commercial configuration was quoted in the first place, return to RFQ quote normalization rather than approving an undefined exception.
This classification prevents two common errors. The first is treating a permanent change as a one-time waiver that keeps repeating. The second is trying to close a broader nonconformance investigation with a narrow shipment exception.
Build the request around eight recommended decision fields
A bare email saying “please accept this lot” is not a usable deviation request. The decision file needs enough structure to show both the departure and its limits.
1. The requirement and the exact departure
Record the approved requirement and the proposed condition side by side. Use controlled references and measurable descriptions where available. Avoid vague summaries such as “small cosmetic issue” or “material is similar.”
If the supplier has not confirmed the departure precisely, the buyer cannot judge its consequence or verify the affected units later.
2. Why the departure occurred
The immediate reason helps the buyer understand whether the event is genuinely temporary. A late raw-material delivery, a damaged tool, a process excursion and a drawing misunderstanding are different problems even when they lead to a similar request.
The reason is not automatically a root-cause analysis. A one-time deviation may be reviewed before a full corrective-action investigation is complete. But the explanation should be credible enough to show why the exception has a defined end.
3. The affected population
Define the purchase order, production lot, quantity, date range and configuration. If serial, batch, pallet or carton identifiers exist, record them. The supplier should also state whether any affected units have moved, been packed, or been mixed with conforming product.
Quantity changes the exposure. A small, segregated evaluation quantity is different from the same departure across an entire production run.
4. Product and operational consequences
Map the proposed condition against the decisions the buyer actually owns. Depending on the departure, the review may consider:
- dimensional fit and assembly;
- sealing interfaces or leak paths that may require separate filled-unit qualification;
- electrical contact or activation behavior under the buyer’s approved, model-appropriate evaluation method;
- changed wetted materials or construction that must be routed to the buyer’s separate formulation-compatibility review;
- dimensional or packaging effects on filling, capping, labeling or handling operations;
- cosmetic acceptance and brand presentation;
- traceability, transport or customer-specific requirements.
This list is not a universal test plan. Its purpose is to stop a team from approving a deviation solely because the most visible feature seems unaffected.
5. Evidence supporting the proposal
Ask for evidence that matches the possible consequence. That could include inspection data, photos, controlled samples, dimensional results, material information, process records, or a focused functional check. More evidence is not automatically better; relevant evidence is better.
The supplier should identify which units were evaluated and how those units relate to the affected production population. A photo of one acceptable-looking unit does not establish the status of a full lot. A summary table without method, sample identity or revision context may be equally difficult to rely on.
6. Identification and segregation
The buyer should be able to find the affected units if the decision changes or a downstream issue appears. Record how cartons, pallets, lots or individual units will be identified, and confirm that affected product remains segregated from conforming product until disposition.
This control is especially important when the proposed departure is not visible after assembly or packaging.
7. Duration, expiry and return to standard
State when the exception ends. The boundary may be a quantity, a named purchase order, a production lot, a date, or a combination of these. Then record how the supplier will return to the approved state.
An approval without an expiry can become an uncontrolled specification change. If the alternative will continue, stop extending the deviation and evaluate it through change control.
8. Decision, authority and shipment status
The record should show who decided, what was decided, which evidence was reviewed, what conditions apply, and whether the buyer’s controlled process still places shipment on hold.
Use explicit states such as:
- rejected;
- more evidence required;
- approved for the identified quantity or lot only;
- routed to change control;
- cancelled because conforming product will be supplied.
Silence, a chat reaction or an ambiguous “looks okay” message does not create a reconstructable release record. Under a controlled supplier-quality procedure, deviating product would normally remain on hold until the buyer records an authorized written decision and confirms any separate release conditions.
A fictional example: a temporary packaging-material substitution
Assume a supplier is preparing a batch of empty AIO devices to an approved configuration. The device hardware itself is unchanged, but the supplier cannot obtain the approved inner-tray material in time and proposes a visually similar substitute for one purchase order.
The buyer does not begin by approving the substitute based on appearance. The decision file first identifies the approved packaging specification and revision. It then records the substitute material, affected PO and quantity, the reason for the shortage, and confirmation that the hardware configuration is unchanged.
The consequence review asks whether the substitute alters protection during transport, particulate exposure, fit within the carton, labeling placement, traceability or handling at the filling site. Evidence might include material information, dimensions, photographs, packed-sample inspection and a transport-focused check appropriate to the buyer’s own requirements.
The supplier identifies and segregates the affected cartons. The request expires after the named PO, and the recovery plan states when the approved tray returns. The buyer can then choose among four defensible states:
- reject the request because the risk or evidence is unacceptable;
- request missing evidence while keeping shipment on hold;
- approve the substitute for that PO only, with written conditions and identification controls; or
- open change control if the supplier intends to adopt the tray permanently.
This example is intentionally fictional. It does not describe an ILEVA order, supplier, acceptance criterion, test result or approval.
Approval does not erase the underlying requirement
A temporary deviation authorizes only the defined exception within the buyer’s approval system. It does not rewrite the drawing, qualify a permanent change, close a corrective-action case, or prove that the completed lot is ready for shipment.
It also does not resolve obligations outside the commercial decision. Applicable law, customer contracts, safety requirements, filled-product qualification and market-specific duties still need their own competent review. Approval of empty hardware is not a regulatory filing update, product-safety certification, or endorsement of the finished filled product. If the available evidence cannot support those decisions, the correct state is not “approved with caution.” It is “more evidence required” or “rejected.”
Close the exception so it cannot become the new baseline by accident
Once the affected quantity has been produced, rejected or cancelled, close the deviation record. Confirm the final disposition, actual quantity, shipment or hold status, identification method and return to the approved requirement.
At receipt, the incoming inspection process should match the lot or carton identification to the approved exception record before disposition, so the known deviation is not mistaken for an unidentified nonconformance. After the exception expires, verify that the first subsequent conforming lot has returned to the approved requirement. If the issue repeats, misses its recovery date or reveals a systemic weakness, escalate it into corrective action or change control rather than issuing another informal extension.
The strongest deviation decision is therefore not the one with the longest form. It is the one another reviewer can reconstruct: the approved baseline, the exact departure, the affected population, the evidence, the written authority, the expiry and the path back to standard.
That record protects both sides of the supply relationship. The supplier knows exactly what is and is not authorized. The buyer retains control of configuration, lot identity and shipment status without turning a temporary exception into an undocumented product change.
