The sample passes the buyer’s review. Packaging work begins, the deposit is paid, and the launch date is added to the calendar.
As production planning moves forward, a new issue appears.
The supplier proposes a different fan, coating or controller because the component used during development is unavailable, has changed in cost or is not part of the planned production configuration.
At that point, the question is no longer whether the sample was acceptable. It is whether the approved product was defined tightly enough to be repeated.
A sample is valuable evidence. It shows that one unit, with a particular combination of components, materials, software and assembly, produced an acceptable result.
It does not by itself establish that mass production will use the same construction.
Consistent production depends on three linked controls:
- an approved physical sample;
- an approved written specification and supporting records;
- an agreed process for handling changes.
The specification and supporting records may include approved component information, artwork, software records, packaging files and other project-specific documents.
Without these linked controls, “same as sample” can mean different things to the buyer, supplier, factory and inspector.
First identify what kind of sample was approved
Not every sample represents the same stage of development.
A supplier may provide:
- a stock sample;
- a sample from an earlier project;
- a hand-modified unit;
- an engineering sample;
- a pre-production sample;
- a unit made from production tooling;
- a unit selected from a pilot run.
Each type can answer different questions.
A stock sample may demonstrate product format and basic performance. It may not contain the buyer’s final panel, programme, packaging, market version or internal component set.
A pre-production sample may be closer to the intended order, but only if it is connected to the final approved documents.
Even a pilot-run sample represents a selected unit. It does not replace production controls or batch inspection.
The sample record should therefore identify:
- sample type;
- supplier model number;
- buyer project reference;
- sample label or serial reference;
- date;
- configuration;
- destination-market version;
- modifications;
- remaining open items.
Without that record, “sample approved” may refer to a unit that was never intended to represent the final production configuration.
Tie the physical sample to the approved specification
The approved sample shows what can be seen, touched and tested.
It does not fully describe everything inside the product.
The approved specification and supporting records should identify the agreed version, including where relevant:
- product format;
- capacity basis;
- basket and cavity dimensions;
- voltage and frequency;
- plug and cord;
- rated power;
- heater and fan configuration;
- control type;
- temperature and timer ranges;
- programme logic;
- basket and crisper-plate materials;
- coating;
- accessories;
- labels;
- packaging;
- manual version.
The broader product fields are set out in Air Fryer Sourcing Information.
Any difference between the physical sample and the approved specification should be resolved before production.
The specification and sample record should then be updated or annotated so that both point to the same approved version.
Leaving the two references in conflict creates avoidable uncertainty. The factory may follow the written specification while the buyer expects a visible feature from the sample, or the buyer may rely on a sample feature that was never accepted into the production specification.
What can change without changing the product’s appearance
The most difficult production differences are often those that are not immediately visible.
Internal components
Two units can look identical while using different:
- heaters;
- fan motors;
- temperature sensors;
- thermal fuses;
- relays;
- controllers;
- internal wiring;
- power cords;
- switches.
An alternative part may fit and function while still affecting noise, heating behaviour, service life, technical documentation or conformity-assessment scope.
The project record should identify:
- which components are fixed;
- which approved alternatives are permitted;
- which substitutions require notice and review.
Software and control behaviour
For digitally controlled models, software can change the user experience without changing the outer appearance.
Differences may include:
- preset temperatures;
- preset times;
- adjustment steps;
- drawer-open behaviour;
- memory after reinsertion;
- end-of-cycle sound;
- display text;
- programme sequence.
The approved programme logic and, where available, the software or firmware version should be connected to the sample and production record.
A later programme change may require a new sample, functional review or document check, depending on its scope.
Materials and coatings
A basket can appear unchanged while using a different base material, thickness or coating system.
Plastic parts may also change in resin, additive or colour masterbatch.
These differences can affect:
- heat resistance;
- odour;
- durability;
- appearance;
- food-contact documentation;
- colour consistency.
Where the construction forms part of the approved product, material declarations, component references or controlled specifications provide information that the physical sample alone cannot show.
Packaging is part of the approved product
The appliance may remain unchanged while the delivered product becomes different because of packaging.
Controlled packaging items can include:
- gift-box structure;
- master carton;
- internal protection;
- plastic bags;
- barcode;
- labels;
- warnings;
- artwork;
- manuals;
- accessories;
- packing arrangement.
A packaging change may affect:
- transit damage;
- carton dimensions;
- container loading;
- retail presentation;
- user instructions;
- model identification.
Final artwork and packing specifications should therefore be approved separately, even when the appliance sample itself has already passed review.
Model references should match or be explicitly mapped
The quotation, sample, specification, rating label, certificate or report, packaging and inspection record may not always use the same reference.
For example:
- the buyer may use an internal project code;
- the supplier may use a factory model number;
- the packaging may use a market-facing SKU;
- a certificate or report may cover a wider model family rather than only the quoted model.
Those differences can be legitimate, but their relationship must be documented.
Model references across the project should therefore either match or be explicitly mapped.
Where a certificate or report covers a wider model family, the relationship between that family and the quoted production model should be recorded rather than assumed.
A suffix may also identify a different voltage, plug, programme or market version. It should not be treated as an administrative variation until its meaning is understood.
The model and entity references recorded during quotation comparison should carry into the sample and production records.
The golden sample has a limited but important role
A golden sample provides a physical reference for appearance, assembly and selected functional checks.
For it to be useful, it should be:
- clearly identified;
- dated;
- labelled with the project reference;
- tied to the approved specification;
- stored under agreed conditions;
- available where the production or inspection method relies on physical comparison.
It should also be clear who retains each reference unit.
Possible references include:
- buyer sample;
- supplier sample;
- inspection sample.
The golden sample does not replace the specification. Its physical presence cannot reveal every internal component, material grade or software setting.
That is why the sample, approved specification and supporting records need to remain linked.
Use an approved component or construction list
For important parts, an approved list can record:
- component name;
- component manufacturer or approved source;
- part number;
- rating;
- material;
- approved alternative;
- relevant document;
- change-approval requirement.
The appropriate level of detail will vary by project. It does not need to disclose unnecessary proprietary information.
It does need to provide enough control to prevent unrestricted substitution.
When an alternative is proposed, the review may need to consider:
- technical equivalence;
- performance impact;
- testing implications;
- document scope;
- sample requirements;
- timing;
- cost.
The resulting decision should be recorded rather than left only inside an email thread.
Define what counts as a change
The third control is the change-notification process.
A project should identify which changes require notice, such as changes to:
- materials;
- coating;
- component supplier;
- component model;
- PCB or controller;
- software;
- production site;
- tooling;
- manufacturing process;
- packaging;
- test method.
The process should also state what happens after notification.
Depending on the nature of the change, the next step may be:
- document review;
- new sample;
- functional test;
- conformity-assessment review;
- pilot-run check;
- buyer review or approval, where required.
If production moves to another site, or if a controlled component or construction changes, the relevant document scope may need to be reviewed against the applicable conformity-assessment requirements.
The exact response depends on the product, destination market and nature of the change. The important point is that the change becomes visible before production continues.
Pilot production and inspection need the same references
A pilot run can reveal problems that a single development sample does not show.
It may help assess:
- assembly consistency;
- component control;
- control programming;
- appearance;
- packaging;
- work instructions;
- test stations;
- recurring defects.
The pilot run does not replace later inspection. It provides another opportunity to check whether the approved product has been transferred into the production process.
Pre-shipment inspection should then refer to the final approved versions of:
- specification;
- golden sample;
- artwork;
- packing requirements;
- defect criteria;
- functional checks;
- labels;
- accessories.
Otherwise, an inspector may compare the order with an outdated sample or an incomplete specification.
Component traceability also supports after-sales work. When production parts change without a clear record, spare-part compatibility, fault diagnosis and complaint handling become harder to manage.
What public information cannot establish
A supplier website may describe testing equipment, production systems or quality processes.
That information can provide useful context.
It does not normally establish:
- the component set used in the buyer’s order;
- the firmware in the approved model;
- the coating system applied to production;
- the final packaging version;
- the specific production line;
- the agreed change-notification process;
- the inspection basis.
Those points belong to the project record and require model-specific supplier confirmation.
Keep the approved reference connected to production
A good sample matters because it gives the project a physical reference.
Consistent production requires:
- a clearly identified sample;
- an approved specification and supporting records;
- mapped model references;
- controlled components and materials;
- recorded digital behaviour, where relevant;
- approved packaging;
- a defined golden sample;
- a change-notification process;
- a production and inspection basis.
Without those controls, production may diverge from the approved reference even though the original sample itself has not changed.
The Air Fryer Sample-to-Production Checklist keeps the approved sample, specification, supporting records, component references, packaging versions and change-control requirements connected before mass production begins.