A force-measurement supplier lists a dedicated beverage-can opening test for a stay-on-tab closure according to ISO 17480:2015. Its application listing is a useful reminder that an opening-force number belongs to a named action, not to a can end in the abstract. A beverage can can meet a neat peak result and still have a weak accessibility specification if the pull path, sample state, intended users, and release rule were never agreed. The useful question is not “What force should every can need?” but “What controlled result and user outcome will this configured end have to meet?”
A force limit without the action, fixture, sample state, and acceptance rule is not a release specification. It is only a number another supplier, laboratory, or receiving team may not be able to reproduce. For an accessible beverage-can end, the specification must connect the result to the exact end, how the tab is pulled, the condition of the sample, and the people expected to open it.
This avoids a universal numeric target by design. A value that is appropriate for one end geometry, tab style, beverage condition, market, and intended user group may be unsuitable for another. It also prevents a procurement error: treating a supplier test result as a product promise before the buyer has defined what the test was meant to prove.
ISO describes accessible opening through opening design and instrumented and user-based evaluation. The accessible standard record therefore supports a broader specification than a standalone force number: it concerns how a package is found, understood, handled, and evaluated as well as the physical measurement. It is not a published universal pass value for every beverage can.
Write the following six fields into the buying brief, supplier test sheet, and receiving-quality record. They turn an accessibility intention into a result that two parties can compare.
| Specification field | What to write | Why it changes the decision |
|---|---|---|
| Configured end | End diameter, tab style, drawing revision, and intended can format. | A result belongs to a configuration, not to “aluminum lids” generally. |
| Opening event | The tab action and the point at which the result is recorded. | It stops different stages of opening being reported under one label. |
| Controlled method | Fixture, pull direction, rate, gauge range, and capture rule. | It lets another team repeat the same action. |
| Sample state | Fill status, temperature, dwell period, lot identity, and preparation. | It prevents a changed sample from posing as an end-design change. |
| Release range | Individual-result limits, variation review, sample plan, and escalation owner. | It defines what happens near or outside the agreed range. |
| User-opening check | Intended user group, task, success definition, and feedback to record. | It tests whether a controlled result translates into usable opening. |
The first four fields create a comparable test; the last two turn it into a release decision. If a buyer cannot set every value at the start, the brief should mark it open and name the approver. Leaving it explicitly unresolved is safer than silently inheriting a number from a different end program.
An opening event is the exact part of the tab-opening action at which the result is recorded. For a stay-on tab, a specification may need to distinguish initial tab lift, the point where the score begins to open, and the continued panel-opening action. Those actions are related, but they are not automatically one measurement. The report should name the event in plain words, identify the tab and end configuration, and show the force trace or peak rule used.
That definition protects both sides of a purchase. A buyer can reject a report that says only “opening force” with no action described; a supplier can avoid comparison against a reading generated with a different tab angle or end style. For a Baixi Cans lid inquiry, it is practical to review aluminum can lid configurations against the opening-force brief and attach the selected configuration to the test request before interpreting a sample result.
The name should show whether the reading covers tab lift, initial opening, a later tear action, or another agreed stage. The end drawing and method record should use the same wording, so that a laboratory result can be matched to the requested opening action.
A vendor ISO-referenced SOT example defines pull angle, speed, and maximum-force reading; ISO notes methods and conditioning can vary by opening mechanism and packaging type. The SOT method example and the standard’s method examples should be read as method context, not as universal customer specifications. A result becomes comparable only after the buyer and supplier lock the way force is applied and the state in which the sample is tested.
Conditioning means holding samples in the stated state before testing. A method record should state the holder, pull direction, pull rate, gauge range, sampling or peak-capture rule, and sample identification. It should also say whether the end is empty or filled and whether the test follows a stated temperature and dwell condition. Once those settings change, the result may still be useful for investigation, but it no longer proves conformity to the earlier method.
The cited beverage-end study evaluates thermal conditions and pressure/buckle strength, not tab-opening force. That research boundary matters because an end-performance result only answers the question it actually tested. Do not use opening-force data as a proxy for buckle performance, and do not use a pressure result as proof that a tab is accessible.
The same discipline applies across product formats. A method approved for one body and end combination should not travel by label alone; keep a 500 ml beverage-can configuration as a separate validation line until its end, sample state, and test method are documented in the same way.
The ISO-referenced stay-on-tab method example records a 90-degree pull, a 500 mm/min rate, and the maximum peak-force result. Those settings are not a target to copy into every purchase order, but they show why a report needs the pull path and capture rule. A manual pull, a hooked fixture, and a motorized stand may all create legitimate observations; they should not be blended into one supplier comparison unless the buyer has deliberately qualified them as the same method.
For a lot-release sheet, write one clear instruction: secure the agreed end configuration in the named fixture, apply the defined pull path at the approved rate, record the stated event, and retain the force trace or peak record. Add a change-control line requiring revalidation if the fixture, tab hook, rate, or capture setting changes. That turns an equipment setup into an auditable method rather than an operator habit.
ISO 17480 notes that test methods and conditioning can vary with the opening mechanism and packaging type. Its mechanical-evaluation examples make the boundary clear: conditioning is part of the chosen method, not a detail to reconstruct after a complaint.
The record should make the stated sample state observable: end-only or filled can, beverage type if filled, sample temperature, dwell period, transport or storage condition, and time from filling where relevant. Do not invent a generic dwell time without a product requirement. Instead, specify one condition for comparison and mark any changed condition as a revalidation trigger.
ISO calls for user-based studies alongside instrument-based evaluation; the cited older-adult study observed packaging-opening performance and strength relationships. The standard text explains why a mechanical result alone cannot establish exact limits on user ability, while a study of 40 adults over 65 observed opening performance and hand-strength relationships in hospital food and beverage packaging. That study is not a beverage-can force specification; it supports including a user-facing check when accessibility matters.
Use the instrumented pass to answer, “Did this configured end meet the agreed method?” Use the user-opening pass to answer, “Could the intended user complete the agreed opening task without an unacceptable outcome?” The second check can record completion, time, need for assistance, handling difficulty, and a predefined feedback category. It should fit the target market and user group, not become a casual office demonstration.
An acceptance envelope is the agreed range and variation rule used to release or hold a lot. It should include more than a single average: state individual-result boundaries, the rule for abnormal spread or trend shift, the sample definition, the user-check result required, and the escalation owner. This does not require an arbitrary universal sample size; it requires a plan that makes the next decision visible.
Release candidate means both passes are documented: the controlled method conforms, and the user-opening check meets the agreed outcome. A failure or unknown on either pass is a hold, a method-repair task, or an access-design review—not a result to average away.
ISO 17480 notes that test methods and conditioning can vary with opening mechanisms and packaging types. The method examples make the following pilot a controlled-method example, not a force recommendation. A beverage team is qualifying a stay-on tab for a 250 ml slim sparkling-drink launch before a 60,000-can first run. The buyer needs a release decision after pilot samples and before the first commercial lot is approved. A supplier report shows a favorable peak result, but the pilot record does not state the fixture path, sample temperature, dwell period, or a user-opening check. To keep the format visible while preparing the trial, it can compare the 250 ml slim can format before approving an end trial.
A beverage team is qualifying a stay-on tab for a 250 ml slim sparkling-drink launch before a 60,000 cans first run. The buyer needs a release decision after pilot samples and before the first commercial lot is approved. A supplier report shows a favorable peak result, but the pilot record does not state the fixture path, sample temperature, dwell period, or a user-opening check.
Illustrative only: a 24-sample comparison cannot be interpreted until its fixture and conditioning states align. Eight pilot samples were opened manually and sixteen were pulled on a fixture, giving 24 observations that are not yet comparable. The first production-lot samples arrive after a different dwell time and have no matched user-opening record. The end configuration is known, but the test system is not controlled well enough to interpret a shifted result.
The buyer therefore has 24 observations, not 24 comparable results. Combining them would hide whether a difference came from the end, the action, or the sample state. Hold the lot’s opening-force release, define one fixture and conditioning protocol, then repeat the instrumented comparison and the user-opening check. Record the tab event, fixture geometry, pull rate, peak-capture rule, sample state, lot definition, and agreed escalation path in one revision-controlled brief. Release only when the controlled instrumented result stays inside the agreed acceptance envelope and the targeted user-opening check meets the agreed outcome. Illustrative composite; it does not report a customer result, prescribe a universal sample size, or set a universal force value.
One packet should contain the configuration, controlled test, acceptance envelope, user opening check, and escalation route. Teams that need to scope the technical exchange can use the Baixi Cans service workflow to frame a technical handoff. Sending these items in one revision-controlled document reduces the risk that purchasing, quality, and a supplier work from different assumptions. It also makes the response more useful: a supplier can identify what needs clarification instead of being asked to promise that an unspecified end will be “easy open.”
Use the same packet for an initial sample request and a later receiving-quality review; only the actual lot identity and results should change. Before release, compare the submitted drawing revision against the tested configuration, make sure the report identifies the lot and approved method, and confirm that the user-opening check used the group named in the brief. If an item is unknown, list the owner and the deadline rather than interpreting the force result as a complete approval. Once the configuration, method, and decision fields are complete, teams can send the brief to Baixi Cans.
It should state the end configuration, opening event, test setup, conditioning state, sample rule, acceptance logic, and the user-opening check. The practical test is whether another party can repeat the result and reach the same release decision. Include the drawing reference, force event, fixture and pull path, sample condition, individual and variation rules, escalation owner, and change-control rule. A title such as “easy-open force” without those details is an incomplete request because it gives neither a supplier nor receiving quality a reliable way to decide whether a new result matches the approved one.
ISO 17480 describes accessible opening through both instrumented and user-based evaluation rather than a universal beverage-can pass number. The standard record and standard text can guide the structure of an accessibility review, but the buyer still has to define the configured end, method, intended users, and product boundary. It is also sensible to document how package integrity will be considered alongside opening effort, because a force reduction that ignores the end’s required function is not an accessible specification. Do not treat a value from a different tab, end size, or user group as an ISO limit for the current program.
Condition every compared sample to the same documented product state, temperature, fill state, and dwell period before pulling the tab. The correct condition is the one the buyer and quality team have approved for the comparison, not a number copied from another package. Record storage, transport, timing, fill information, and any preparation that could make two samples different. If the first lot is tested in a different state from the pilot, treat it as a revalidation question: record the delta, decide whether the earlier data still apply, and repeat the approved comparison where necessary.
No. A force gauge can show whether a controlled mechanical test is repeatable, but user-opening checks are needed to evaluate actual handling and comprehension. The gauge result remains valuable because it controls manufacturing comparison; it simply does not describe every user’s strength, grip, understanding of the tab action, or experience of opening the can. Pair the two forms of evidence, define the intended-user group before presenting the sample, and record how completion, assistance, difficulty, and feedback will be judged. That makes a user check a planned evaluation rather than an informal demonstration.
Hold the lot when the approved test method was not followed, individual results breach the agreed envelope, variation shifts unexpectedly, or the user-opening check fails. Also hold when the end configuration, fixture, sample state, or report revision cannot be matched to the approved brief. A hold is not automatic rejection; it is a controlled request to identify the changed factor, isolate the affected evidence, repeat the agreed comparison, and decide from comparable results. The release owner should record the reason for the hold and the exact evidence needed to close it.
