Smart Lock Glossary: AQL Definition for B2B Buyers
An importer often encounters AQL in a quotation, purchase order, inspection request, or supplier quality agreement. The acronym looks compact, but the commercial effect is not. For an importer, the aql definition is the point where an abstract quality threshold becomes a decision about an entire lot of goods. It can determine whether a shipment is accepted, sent back for rework, or rejected.
Direct answer. The short answer is that aql definition is not one decision. It is a sequence. This article takes aql definition from aql definition through the decision record to the record you keep. An aql definition is a reference entry. It holds definitions, options and trade-offs. aql definition is the entry point for aql definition.
The term aql definition carries one meaning throughout this article. It is the one given in aql definition. That is a working definition of aql definition, and the buyer still has to check it against the dated product page.
AQL stands for Acceptable Quality Limit. It is a quality level within a sampling plan at which a lot is judged. That short sentence needs context before it becomes useful. The applicable sampling plan must identify the lot, the defect classes, the sample, the acceptance rule, and the person authorized to release or dispose of the goods.
This guide follows the AQL decision through the full import process: requirement definition, contract wording, production readiness, pre-shipment inspection, lot disposition, arrival review, and record retention. It is a working reference for importers who need to ask precise questions rather than copy an unexplained number from another programme.
Why an Acronym Can Decide a Shipment
AQL does not describe an individual lock in isolation. It operates at lot level. A lot may contain units from one production run, one configuration, one packaging arrangement, or another agreed grouping. If those boundaries are unclear, an inspection result can appear valid while describing the wrong population of goods.
The acronym also does not work without a sampling plan. The plan determines how many units are selected, how nonconformities are classified, and how the findings map to the acceptance rule. AQL supplies a threshold within that structure. It does not create the structure by itself. The same question as aql definition, read from a different angle, is covered in Smart Lock Glossary: Anti Passback Definition for B2B Buyers.
| Buyer question | Practical meaning | Common confusion | Evidence to retain |
|---|---|---|---|
| What is AQL? | The quality level in a sampling plan at which a lot is judged | A promised maximum defect rate for the shipment | Signed sampling plan and quality agreement |
| What does it decide? | Whether the sampled lot is accepted, reworked, or rejected | A guarantee that every delivered unit is acceptable | Inspection report and signed lot disposition |
| What population does it cover? | The precisely identified inspection lot | Every item produced by the supplier | Lot definition and segregation record |
| Who applies it? | The inspector records findings against the agreed method | The supplier alone decides whether findings count | Named inspection and disposition authorities |
| When does it bite? | At the inspection gate before release or after arrival review | The order is automatically accepted once production ends | Gate checklist and release record |
The practical confusion is not usually ignorance of the acronym. It is assuming that a valid-looking AQL reference is complete. In many disputes, the missing information is not the threshold itself but the way defects are counted or the way the lot was assembled. The buyer therefore needs evidence that connects the agreement, the sample, the findings, and the decision. The second take on aql definition is Smart Lock Glossary: HS Code Definition for B2B Buyers. If the answer has to survive a supplier meeting, Smart Lock Glossary: EPD Definition for B2B Buyers is the next one to read. The comparable treatment of the same question sits in Smart Lock Glossary: Door Closer Definition for B2B Buyers. The hardware behind this is in the smart door locks.
The Five Fields That Make AQL Legible
A workable aql definition needs five connected fields. If any one is missing, an importer cannot reproduce the decision. This matters because the same physical observation can produce different outcomes under different lot boundaries or defect categories.
1. Lot definition. State what units belong together for inspection. Include configuration, finish, production batch, packaging, and any agreed shipment grouping where these affect the comparison.
2. Sampling plan. Identify the inspection level, sample-selection method, sample size, and acceptance or rejection rule. The plan also defines whether the method is single or multiple and how retesting or reinspection is handled.
3. Defect classification. Define what counts as critical, major, minor, or any other agreed category. The names alone are not enough. Each category needs observable conditions and a clear unit-counting rule.
4. AQL value by defect class. Record the agreed limit for each class that matters to the purchase. Do not leave the value implied by a catalogue note or an old inspection request.
5. Disposition rule. State what happens when the sample meets, misses, or falls between the plan’s decision points. Include who can approve rework, who can release held goods, and what record closes the decision.
| Field | Question it must answer | Why the field changes the result |
|---|---|---|
| Lot | Which units are being judged? | Findings are applied to that lot, not to every unit in the supplier’s output |
| Sampling plan | How is the sample selected and evaluated? | Different sample structures produce different decision rules |
| Defect classification | What condition counts, and in which category? | One unit may be counted differently under different definitions |
| AQL value | What quality level applies to that class? | The value is interpreted within the selected defect class |
| Disposition | What happens after the result? | A result without an authorized action does not release the shipment |
This structure is useful during quality assurance sampling planning because it keeps inspection language aligned with purchasing language. The sales team can describe the product; the quality team can describe the evidence; finance and logistics can see the gate. The agreement should make all three views point to the same lot and the same decision.
The Control Timeline from RFQ to Record Retention
The AQL process is not a single inspection event. It is a chain of gates. Each gate uses the previous record and produces the evidence needed for the next one. If a later party changes the lot, sample, or defect definitions, the original decision may no longer be reproducible.
flowchart TD
A[Capture buyer requirement] --> B[Lock agreement fields]
B --> C[Prepare the identified lot]
C --> D[Select and inspect the sample]
D --> E[Classify each nonconformance]
E --> F[Apply the acceptance rule]
F --> G[Record the lot disposition]
G --> H[Retain evidence and compare later lots]
| Stage | Control objective | Required record | Gate question |
|---|---|---|---|
| Requirement capture | Translate the purchase requirement into inspectable conditions | RFQ quality section and defect schedule | Can both parties describe the same requirement? |
| Agreement | Freeze the sampling method and decision authority | Purchase order, quality agreement, sampling plan | Is every referenced field present and internally consistent? |
| Production readiness | Confirm the goods can be presented as one identifiable lot | Production and packing record | Is the shipment physically available for selection? |
| Pre-shipment inspection | Test the agreed sample and classify findings | Inspection request and inspection report | Was the sample selected under the agreed method? |
| Disposition | Convert findings into an authorized lot decision | Signed disposition or release note | Is the action linked to the applicable acceptance rule? |
| Arrival review | Reconcile received goods with the released evidence | Receiving record and discrepancy log | Does the physical shipment match the inspected identity? |
| Retention | Preserve traceability for comparison or review | Indexed evidence set and access record | Can the decision be reconstructed without guesswork? |
A buyer can include the quality fields in What an RFQ Should Contain: Terms and Tables, but the RFQ is not the final control. The signed order and quality agreement become the controlling record. Any later change should be handled through an agreed revision route rather than informal email.
The timeline also clarifies roles. The supplier prepares and presents the lot. The inspector samples and records observations against the agreed method. The authorized disposition party applies the acceptance rule. The importer retains evidence and reconciles it to the goods received. No single role should rewrite the plan at the inspection table.
Lot Identity Before Sampling
Lot identity is the first operational control behind the term. A lot label, carton marking, packing list, and production record may use different references unless the buyer specifies how they connect. A strong lot definition ties those records together before selection begins.
For a smart-lock programme, configuration boundaries matter because a visual or hardware difference can change whether a sample represents the purchased goods. The relevant configuration should be stated through the buyer’s approved product record. If a retrofit or installation package is involved, the relationship between the product and the approved door requirement should also remain traceable.
| Lot field | Buyer question | Evidence | Consequence if missing |
|---|---|---|---|
| Product identity | Is the unit the approved configuration? | Order line, approved sample, packing record | The sample may represent another variant |
| Finish and hardware grouping | Are visibly or functionally different units separated? | Production and packing record | Mixed findings become hard to classify |
| Production or packing identifier | Can the inspected units be separated from other stock? | Internal traceability record | Selection may cross lot boundaries |
| Quantity and unit of measure | Is the stated lot quantity reconciled with the physical units? | Packing list and inventory control | The denominator of the decision is uncertain |
| Packaging state | Is the lot presented in the agreed configuration? | Packing record and photographs where agreed | Handling or packaging conditions may be hidden |
| Shipment grouping | Does the inspection lot match the shipment or receiving lot? | Shipping and receiving records | Arrival reconciliation becomes ambiguous |
The approved production reference is more than a visual comparison. The broader control is described in Pilot Order Signoff, while Pilot Order Evidence addresses the supplier evidence behind the process. Together, they help distinguish a real reference from a loose description of a similar-looking unit.
A useful rule is that the inspection request must name the same lot fields that the supplier will use to segregate the goods. If the inspector cannot locate one identifiable lot, the correct response is to resolve the identity before accepting the sample result.
Building the Sampling Plan
The sampling plan converts the AQL value into a repeatable selection and decision process. It should be readable by the inspector, the supplier, and the buyer without requiring each party to infer the missing steps from experience.
Start with the inspection level. This is a plan input that tells the inspector how much sampling to perform under the selected method. It is not the same thing as the acceptable quality limit and should not be recorded in the same field. The plan then defines the sample size and the acceptance or rejection numbers that apply to the relevant defect class.
| Plan element | What it controls | Wording that prevents ambiguity |
|---|---|---|
| Inspection level | The extent of sampling under the method | Name the exact plan field and reference used |
| Sample size | How many units are selected | State whether units or another inspection unit is counted |
| Selection method | How the sample is chosen | Identify random, sequential, or another agreed method |
| Acceptance number | The finding count that supports acceptance for the class | State the applicable defect class |
| Rejection number | The finding count that supports rejection for the class | State the applicable defect class |
| Single or multiple plan | How successive decisions are reached | Identify the plan type rather than assuming it |
| Retest or reinspection | What happens after rework or a disputed result | Define the new sample and the evidence required |
| Unit of measure | The denominator used for the lot | State how packs, cartons, and units are counted |
Avoid writing “inspect to AQL” as the entire instruction. It leaves the inspector to choose the plan, sample, defect categories, and reporting method. The more useful request states each field and identifies the agreed source for any remaining plan detail.
The buyer should also decide whether the inspection covers the finished unit only or includes packaging, accessories, labels, and included documents. A quality plan can become unreliable when the inspected item differs from the purchase item. One lock in a carton is not the same inspection object as a carton containing a defined number of locks, accessories, and installation records.
Finally, specify how sampling applies to mixed configurations. Separating visually different units may be practical, but the selection method must still reach the agreed quantity without preference for easier or more accessible units. Otherwise the sampling process is not repeatable.
Defect Classification Without Ambiguity
Defect classification turns an inspector’s observation into a count that the sampling plan can use. Labels such as critical, major, and minor are familiar, but their meaning is not universal. The buyer must define them for the programme and connect each definition to observable product conditions.
The classification schedule should not copy generic wording without adapting it to smart locks. It should explain what constitutes a critical condition, a major condition, and a minor condition, while preventing two inspectors from applying the same label to different physical issues.
| Classification control | Question the definition must answer | Evidence at inspection | Avoid |
|---|---|---|---|
| Critical classification | Which condition makes the unit unsafe, unusable, or outside the approved requirement? | Unit identifier, photographs, inspector description | Relying only on the label |
| Major classification | Which condition affects required function, configuration, or fitness for the purchase? | Observed condition and location | Treating every visible variation as major |
| Minor classification | Which condition is limited in effect and does not alter the agreed function? | Specific location and measurement where relevant | Using minor to hide an unresolved function issue |
| Counting unit | Is one nonconforming unit counted once or by each observation? | Sample sheet and report | Counting the same unit in several classes without a rule |
| Combined findings | How is one unit with several nonconformities recorded? | Multi-finding record | Double-counting without an agreed basis |
| Observation only | Which issue is recorded but excluded from the acceptance count? | Separate observation field | Mixing observations into the formal defect count |
The sampling decision may depend on which class receives a finding. That makes classification a control, not an administrative label. Inspectors should record the observed condition before selecting the category. This allows the buyer to review whether the category was applied consistently rather than merely whether the final count crossed a threshold.
The agreement should also state whether the buyer may request corrective action for findings outside the formal AQL count. An observation recorded on the inspection report may not trigger rejection under the plan, but it can still reveal a process risk worth investigation. Do not imply that the sampling result covers every concern.
Supplier Evidence Before Inspection
A supplier may understand the purchase requirement well and still be unable to present a lot that can be sampled cleanly. Before the inspector arrives, the supplier should provide evidence that the units available for selection match the order and are physically segregated from other inventory.
This preparation is separate from judging the product. The buyer is not accepting the goods at this point. The buyer is confirming that the inspection can occur against a known population and that a meaningful result can be produced.
| Preparation item | Evidence requested | Why it matters before sampling |
|---|---|---|
| Approved configuration reference | Product record linked to the purchase order | Prevents a mismatch between the order and the physical unit |
| Lot segregation record | Location and identifier for the units awaiting inspection | Keeps selection inside the agreed population |
| Packing list | Quantities, carton structure, and shipment grouping | Establishes what the shipment contains |
| Packaging condition | Packing record and agreed handling instructions | Makes packaging-related findings observable |
| Accessory and document check | Packing checklist tied to the order | Prevents omitted items from hiding inside an accepted unit sample |
| Inspection access | Confirmation that the lot is available and identifiable | Avoids an inspection that cannot be reproduced |
| Previous open actions | Disposition status for unresolved nonconformances | Prevents unresolved goods from re-entering the release path |
Supplier verification should be treated as a record review, not an assumption about capability. The relevant evidence and the limits of that evidence are covered in How a Supplier Is Actually Verified: Terms and Tables. A signed statement that goods are ready is less useful than a packing record that can be reconciled to the physical lot.
The importer should also decide who receives the inspection request, who confirms the lot definition, and who is allowed to approve a change. Informal communication around the inspection can otherwise alter the sample basis without leaving a visible revision trail.
Reading the Inspection Record
An inspection report is evidence only when the reader can connect its fields to the agreement. A report showing a sample count and a defect total may omit the lot identity, sample method, defect definitions, or acceptance rule. In that case, the number cannot be interpreted reliably.
The first check is identity. Compare the product, configuration, lot, quantity, and packaging references with the purchase order and the lot record. Then check whether the reported sample and selection method match the agreed plan. Finally, reproduce the acceptance calculation using the report’s own defect classifications.
| Report field | Reader question | Warning sign |
|---|---|---|
| Inspection identification | Can this report be connected to one shipment and lot? | Generic report with no order or lot reference |
| Product and configuration | Does the inspected item match what was purchased? | Description differs from the approved record |
| Lot quantity | Does the stated population reconcile to the packing record? | Quantity changes without a revision |
| Sampling method | Was the sample selected as agreed? | No method or unreferenced selection record |
| Sample composition | Can each inspected unit be traced to the lot? | Units appear without a selection trail |
| Findings by defect class | Are critical, major, minor, or other categories defined? | One undifferentiated defect count |
| Nonconforming unit record | Is each counted unit described and photographed where agreed? | Count without supporting observations |
| Acceptance result | Which plan rule produced the outcome? | “Pass” or “fail” without the rule |
| Disposition | Who authorized the action and what evidence supports it? | Result remains unsigned or open |
| Uninspected population | Does the report avoid implying that every unit was checked? | Sampling result described as full inspection |
The reader should also distinguish a sampling decision from a unit-level statement. A plan can support acceptance of a lot under its rules without certifying every uninspected unit. That is why the report should state the sampled population plainly and avoid implying a guarantee beyond the evidence.
Any disagreement should be handled against the agreed process. Identify the disputed field, compare it with the report and source records, and use the named authority for disposition. Informal reinterpretation after seeing the result weakens the control.
Disposition: Accept, Rework, or Reject
The sampling result becomes commercially meaningful only when it produces a documented lot disposition. The canonical outcomes are acceptance, rework, and rejection, but the authority, conditions, and evidence for each outcome must be stated before inspection.
Accept means the applicable rule supports release of the lot under the agreed plan. It does not mean the buyer waived other contractual requirements. Rework means the permitted corrective route is defined and the party authorized to approve it has accepted responsibility for the result. Reject means the lot fails the applicable decision rule and is not released through the ordinary acceptance path.
| Disposition | Trigger in the agreed plan | Required action | Closing evidence |
|---|---|---|---|
| Accept | Findings fall within the applicable acceptance condition | Release the identified lot against the inspection record | Signed release and linkage to the lot |
| Rework | The plan or agreement permits correction after a failed condition | Define the corrective scope, segregate the lot, and resubmit evidence | Corrective record and authorized resubmission result |
| Reject | Findings reach the applicable rejection condition | Hold the lot and follow the agreed replacement, return, or other remedy route | Rejection record and material disposition evidence |
| Hold for clarification | A required record is missing or disputed | Do not infer a release from silence | Signed clarification and subsequent decision |
| Conditional release | The agreement expressly allows release under stated conditions | State the condition, responsible party, and closure evidence | Conditional release record and closure |
Rework and resubmission should never be a vague instruction to “correct and resend.” The buyer needs to know what may be changed, who performs the work, how the corrected lot is identified, and what evidence demonstrates completion. If the change could affect the approved configuration, the original approval reference should travel with the disposition.
The lot disposition record should connect to the exact inspection report. If later stock is mixed with released goods, traceability can deteriorate quickly. A smart-lock importer should preserve the ability to answer which units were sampled, which disposition applied, and whether a later shipment came from the same release decision.
The Boundaries of an AQL Decision
AQL answers a narrow question: how should a defined lot be judged under a defined sampling plan? It does not answer every question about a shipment, product, installation, or commercial relationship.
| Misreading | Correct reading |
|---|---|
| AQL is the shipment’s defect rate | AQL is a threshold used within a sampling decision |
| An accepted lot is defect-free | The sampled result supports the plan’s lot decision |
| Every unit was inspected | Only the selected sample was inspected unless the plan says otherwise |
| AQL certifies the product | AQL is part of a quality-control process, not product certification |
| AQL proves fitness for a doorway | Installation suitability depends on the approved product and site requirements |
| AQL settles a disputed damage claim | The claim requires its own evidence, including condition and custody records |
| The AQL value is the inspection level | The inspection level is a separate plan field |
| Passing one lot establishes permanent supplier approval | Each release depends on its own evidence and agreed controls |
| A report with no defects proves every unit is sound | A small sample can miss defects outside the inspected units |
These boundaries protect the buyer from a false sense of certainty. AQL is useful precisely because it makes a defined sampling decision, not because it removes uncertainty from the entire supply chain.
The term should also remain separate from product-performance claims. An AQL result may show that sampled units did not exceed the agreed nonconformance threshold for the stated class. It does not create a performance figure, confirm a compliance status, or expand the evidence attached to an individual model.
Where a buyer needs broader assurance, it should define a separate evidence request. That request might concern the approved configuration, supplier verification, conformity paperwork, packaging, or site conditions. Each should have its own scope and record rather than being implied by the AQL report.
Writing the Quality Agreement
The quality agreement should make the inspection executable without a meeting immediately before dispatch. It does not need to reproduce every manual page, but it must identify the controlling documents and explain which version governs. Ambiguity often arises when a purchase order, an inspection request, and a product specification use the same term but different fields.
A practical structure follows the decision chain. First define the quality requirement. Then identify the lot and sample. Next classify defects. After that, state the AQL values and acceptance rule. Finally define the report, disposition, exception route, and evidence retention.
- Requirement scope: Identify the product configuration, order, included items, packaging, and applicable inspection boundary.
- Lot definition: State the units covered and the evidence used to segregate them.
- Sampling plan: Identify the plan, inspection level, sample-selection method, sample size, and acceptance or rejection rule.
- Defect schedule: Define each class, the unit-counting basis, and the evidence needed to support a finding.
- AQL schedule: Record the agreed value for each defect class and the plan source.
- Inspection record: List required fields, nonconformance descriptions, photographs, and references to the selected units.
- Disposition rules: State the outcome conditions, named authorities, rework limits, and rejection route.
- Change control: Require written approval for changes to the lot, sample, defect classification, or plan.
- Evidence retention: Define where the final decision and supporting records are held, who can access them, and how they connect to the shipment.
Avoid vague terms such as “to AQL” or “normal acceptable quality” without referenced fields. Those phrases may sound familiar while leaving every material input open. Use plain sentences that tell the inspector what to select, what to record, and what result follows.
The agreement may also need a precedence rule for conflicts between product specifications, drawings, purchase orders, and quality documents. State which record controls each field rather than relying on a general order of precedence that may not fit the issue.
CONFIRM-WITH-LOCAL-LEGAL: Have counsel confirm the final clause language, dispute route, document precedence, and any local regulatory effect before the supply agreement is signed.
Preparing the Pre-Shipment Inspection
The pre-shipment inspection is a control point, not a substitute for the supplier’s own process. The inspector arrives after production and packing are complete, so the supplier must have completed the actions that make the lot identifiable and presentable. The buyer should send a request that mirrors the signed agreement rather than a generic checklist.
The request should identify the contract, product, lot, expected shipment grouping, packing state, inspection boundary, and selected plan. It should also say who may act as the supplier representative during inspection and where the report must be sent.
| Preparation area | Agreed evidence | Inspection consequence |
|---|---|---|
| Product identity | Approved configuration and order reference | Prevents comparison with a different variant |
| Lot segregation | Physical location and traceability identifier | Keeps selection within the agreed population |
| Quantity reconciliation | Packing list and inventory count | Establishes the lot population |
| Sampling access | All required units available for selection | Prevents substitution or selective presentation |
| Packaging condition | Packed state and handling condition | Makes packaging findings comparable |
| Included-item controls | Accessories and documents kept with the lot | Allows completeness checks to be scoped |
| Evidence access | Previous actions and open records | Prevents unresolved findings from being hidden |
| Escalation route | Named inspector and disposition contacts | Allows clarification without changing the plan |
For office programmes, the approved product and installation requirement can be connected through an Office Smart Lock Site Survey. For retrofit work, the relevant door preparation and constraints should be visible in a Smart Lock Retrofit Site Survey. Those records do not replace the AQL plan, but they help prevent an inspection from treating an unsuitable or mismatched unit as representative of the intended application.
The inspection request should close with the rule that any change to the sample, lot, or defect interpretation is recorded as a revision. The inspector may flag a discrepancy, but only the authorized party should change the agreed basis.
Arrival Inspection and Discrepancy Handling
Shipment acceptance at origin does not eliminate the need to reconcile the goods received. A receiving team should connect the shipment to the released inspection record, then check whether the physical identity and condition remain consistent with the evidence used for the pre-shipment decision.
The arrival check is not an automatic reopening of the AQL result. It is the point at which discrepancies are identified and routed under the agreement. If the receiving condition differs from the inspected condition, the buyer should preserve the relevant evidence before goods are moved into normal inventory.
| Arrival signal | Evidence to capture | Agreed next step |
|---|---|---|
| Product or configuration mismatch | Carton marks, unit identification, order reference | Segregate and compare with the released lot record |
| Quantity difference | Received count and packing documents | Reconcile against the shipment and sampling records |
| Visible handling damage | Packaging condition, photographs, unit identity | Apply the agreed damage and claim route |
| Missing included items | Carton contents and packing checklist | Compare with the purchase configuration |
| Unresolved inspection action | Disposition status and open-action list | Hold the affected units pending closure |
| Unidentifiable stock | Carton labels and internal traceability | Do not merge it into the released lot |
| Condition not represented by the report | Receiving observations and sampling records | Request a scoped review under the agreement |
The key discipline is to preserve the chain between physical evidence and the relevant decision. If goods are mixed with other inventory, a receiving count may no longer prove which units were included in the original lot. Labeling, segregation, and record updates are therefore part of discrepancy control.
If an arrival discrepancy suggests that the sampling result did not represent the received goods, ask for a documented technical review. The review should identify the mismatch, state which evidence supports the conclusion, and avoid pretending that a new AQL calculation can repair an identity failure by itself.
Turning Lot Results Into Supplier Evidence
A single AQL result is a control record, not a complete supplier-performance score. To turn lot results into useful evidence, compare the inspection documents, corrective actions, production records, and shipment changes across multiple lots. The comparison should identify process causes without inventing benchmarks or market statistics.
A rising count in one defect class may be more informative than a combined count that mixes unrelated issues. An improving count may still require investigation if the sample plan or lot definition changed. Trend analysis therefore depends on stable definitions.
| Signal | Safe interpretation | Evidence to request | Management response |
|---|---|---|---|
| Same class appears across several lots | A recurring condition may exist in production or packing | Production records, inspection findings, corrective actions | Open a cause investigation linked to the actual evidence |
| Defect class changes between lots | The inspection scope or product grouping may have changed | Lot definitions, revisions, and packing records | Confirm comparability before drawing a trend |
| Findings cluster in particular cartons | Handling, packing, or selection conditions may warrant review | Carton mapping and inspection selection record | Check the recorded process rather than assume a cause |
| Rework repeatedly produces new findings | The corrective process may be incomplete | Rework instructions and resubmission evidence | Define closure criteria for the affected scope |
| One large mixed lot is sampled | The result may reflect greater heterogeneity than smaller lots | Lot composition and segregation record | Review how inspection lots are constructed |
| Report fields repeatedly change | Evidence quality or document control may be inconsistent | Report versions and buyer revisions | Reconfirm the required inspection record |
| Result depends on an undocumented interpretation | The acceptance rule is not reproducible | The exact plan and interpretation used | Correct the agreement before the next decision gate |
The buyer’s goal is not to turn every nonconformance into a supplier score. It is to connect evidence to action. A useful corrective record identifies the affected configuration and lot, explains the observed condition, records the action taken, and identifies the evidence that shows whether the issue is contained.
For programmes where the first shipment carries unusually high programme risk, How a Pilot Order Reduces Programme Risk: Plain Explanation provides a useful route for connecting sample approval, lot control, and shipment release. The pilot does not replace AQL; it gives the parties a defined configuration and evidence set against which the inspection plan can operate.
An Illustrative Import Decision
Consider an illustrative importer purchasing one approved smart-lock configuration. The initial request contains an AQL reference, but it does not define the inspection lot, the defect categories, or the sample-selection method. At this point, the request is not ready for inspection because the decision cannot yet be reproduced.
The supplier and buyer resolve the missing fields in a written quality agreement. The lot is defined by the approved configuration and production run. Packaging is complete. The sample plan identifies the inspection level, sample size, selection method, and acceptance rule. The defect schedule distinguishes functional nonconformities from limited cosmetic findings and explains how one unit with multiple observations is counted.
| Record | Initial gap | Completed field | Why it matters |
|---|---|---|---|
| Purchase request | AQL named without a complete plan | Controlled reference to the signed sampling plan | Prevents the inspector from choosing missing inputs |
| Lot definition | No segregation basis | Approved configuration and production-run identifier | Connects the sample to a physical population |
| Defect schedule | Labels without observable conditions | Definition and counting rule for each class | Makes findings comparable |
| Inspection request | General request for inspection | Request mirroring the signed plan | Keeps selection and reporting aligned |
| Disposition route | No named authority | Acceptance, rework, and rejection routes assigned | Prevents an open result from becoming an informal release |
During the pre-shipment inspection, the selected sample is recorded against the lot. The inspector identifies several units with conditions that fall into the agreed defect classes and describes each observed condition. A count is then compared with the applicable acceptance rule for each class.
One class falls within the acceptance condition, while another reaches the rejection condition. The inspector does not average the classes together, because the agreement applies a separate rule to each one. The recorded result therefore does not support acceptance of the lot.
The authorized disposition party applies the rejection route and holds the identified goods. The importer does not describe the shipment as “AQL passed,” “AQL failed,” or “AQL rejected” without naming the class and rule involved. The report identifies the exact outcome and the evidence that produced it.
If the agreement permits rework, the corrective scope is recorded before work begins. The reworked lot receives a new identity linked to the original lot, and resubmission evidence is evaluated under the agreed method. If the agreement does not permit the proposed change, the lot remains outside release until the contractual route is completed.
At arrival, the receiving team checks the new or corrected shipment against the final release record. This illustration shows why the acronym alone is insufficient: the useful decision is the chain from requirement, through sample and classification, to disposition and receiving reconciliation.
Importer Release Checklist
Use this checklist before authorizing a shipment against an AQL result. The importer does not need to become the inspector, but the importer must be able to confirm that the inspector had a complete and coherent instruction.
Requirement and contract
- Does the purchase order or quality agreement identify the controlled sampling plan?
- Does the plan name the inspection level, sample size, selection method, and acceptance rule?
- Is the AQL value recorded against each applicable defect class?
- Are critical, major, minor, or other classifications defined in observable terms?
- Is the counting basis clear when one unit has more than one finding?
- Does the agreement name the disposition authority for acceptance, rework, and rejection?
- Is there a written route for changing the lot, plan, or defect interpretation?
Lot and inspection readiness
- Does the lot identify one approved configuration and agreed shipment grouping?
- Can the packing list and physical inventory be reconciled to the inspection lot?
- Are units physically segregated before selection?
- Is the shipment presented in the agreed packaging and included-item state?
- Was the sample selected under the agreed method rather than chosen for convenience?
- Do the report and supporting records identify the selected units?
Result and disposition
- Does the report connect findings to the exact lot and shipment?
- Are findings separated by the agreed defect class?
- Can the acceptance result be reproduced from the plan and recorded counts?
- Does the disposition identify the rule that was applied?
- If rework occurred, is there a corrective record and authorized resubmission result?
- If goods were rejected or held, is there evidence of their physical segregation?
- Is the final release signed rather than inferred from silence?
Receiving and retention
- Do the received goods reconcile to the released shipment and lot identity?
- Are visible discrepancies photographed and recorded before stock is merged?
- Are unresolved actions linked to the affected units?
- Can the buyer retrieve the agreement, inspection request, report, disposition, and receiving record as one evidence set?
- Will later reviewers understand which document controlled each decision field?
If any answer is no, resolve the gap before release. The checklist prevents a common failure mode: treating a complete-looking PDF as complete evidence while the lot identity or decision authority remains somewhere else.
One-Page AQL Term Card
The shortest safe answer remains simple: Acceptable Quality Limit is the quality level in a sampling plan at which a lot is judged. The operational answer has to travel with five fields.
| Card field | One-line answer |
|---|---|
| What it is | A quality threshold used to judge a lot under a sampling plan |
| What it decides | Whether the lot is accepted, reworked, or rejected under the agreed rule |
| What it does not decide | The condition of every uninspected unit or the suitability of an installation |
| Required context | Lot, sampling plan, defect classification, AQL value, and disposition authority |
| Evidence to demand | Signed agreement, inspection request, report, findings, and final disposition |
| Where it applies | At the inspection and release gate, with later reconciliation to received goods |
| Main buyer risk | Treating a bare acronym as a complete inspection instruction |
For an importer, the most useful working definition is operational rather than academic. AQL is valid only when the parties can identify the population, reproduce the sample, classify the findings, apply the rule, and show what happened next. That is the difference between a threshold on a document and a control that supports a shipment decision.
The build-up behind that decision is in how to find a reliable smart lock supplier. That is the same question aql definition has to answer here.Ready to move from glossary to a usable smart-lock purchase file? Request a quote with the approved configuration, destination, packaging plan, and draft AQL fields. Keep the commercial request, quality agreement, and inspection plan linked so that each party describes the same shipment in the same terms.

