PACKAGING
a beauty company style
Compliance & Guidance // Aug 29, 2026

Child-Resistant Closures (CRC) for Concentrated Actives: Push-Turn vs. Squeeze-Turn Protocol and ASTM Limits

# Child-Resistant Closures (CRC) for Concentrated Actives: Push-Turn vs. Squeeze-Turn Protocol and ASTM Limits

TL;DR — A closure that is simply hard to open is not a child-resistant closure; the concept is a protocol: two distinct, coordinated actions before the cap opens.

The two mainstream protocol families are push-turn, where the cap is pushed down and turned, and squeeze-turn, where the cap sides are squeezed and the cap turns — both are third-party standard territory, and their limits belong to the standards bodies, not to this catalog.

The closure side is recorded — Cap family of seven models across 20/410–28/415, Cap/Closure as a component family, torque and leakage testing as quality hooks — but no child-resistant closure is recorded in the catalog; a CRC mechanism is a project-level configuration.


Why: A Cap That Should Not Open by Accident

  • Concentrated actives raise the stakes fast. A formula built around a high-concentration active carries a handling risk at the moment of opening; the packaging system that delays that moment is exactly the topic of a CRC conversation — while the active's risk profile itself is a formulation and compliance matter, per project.
  • A CRC is a protocol, not a stronger spring. The defining feature is the sequence: two distinct actions in a coordinated order. A cap that just resists harder is a stiff cap, not a child-resistant cap — the category is defined by the protocol, which is third-party standard territory.
  • The record anchors the closure, not the mechanism. Seven cap models, neck finishes 20/410–28/415, Cap/Closure as a component family — that is the program's evidence. A CRC build on any of them is a project configuration.
  • Verification has two hooks. Torque testing covers the open-and-close behavior; leakage testing covers the seal. Both exist as capabilities, both are configured per project.
  • Boundary: no child-resistant closure is recorded in the catalog; a CRC mechanism is a project-level configuration. Third-party limits are referenced as a subject, never as program data.

How: The Protocol, the Standard, and the Recorded Closure

3.1 The two-action principle

A child-resistant closure works on sequence, not resistance: it requires two independent actions — typically a push or a squeeze combined with a turn — performed in the right order, before the cap releases. One action alone, no matter how strong, does not open it. The value of the sequence is that it blocks the impulsive opener — the brief attempt — while remaining usable for the intended user. What the intended user needs is judged against third-party child-resistance frameworks, and the whole protocol subject is outsourced to those frameworks; this article describes the categories, not the limits.

3.2 Push-turn protocol

Push-turn is the protocol most people picture: the cap must be pressed down onto the neck or collar while being turned. The push loads the lugs or teeth into engagement, and the turn ratchets the cap off — release it, and the cap free-wheels or re-engages without opening. Because the action depends on the axial push, the interaction between the push depth and the thread engagement is the design surface: push too little and the cap spins without unthreading; push with the turn and it opens. The exact push geometry, lug profile, and engagement depth for a given closure are configured per project; no dimension, force, or limit is published here.

3.3 Squeeze-turn protocol

Squeeze-turn does the two-action work in the grip instead of the push: the user squeezes the cap's sides — typically against a flexible skirt or release tabs — which releases a locking catch, and with the catch released the cap turns. On its own the cap turns but the catch holds; squeezed and turned together, it opens. The design surface shifts to the skirt: its wall thickness, its flex behavior, and where the release point meets the turn torque. All of it is project geometry — the mechanism is guidance, and no flex rate, catch dimension, or torque value is a program fact.

3.4 Where the limits live: third-party standards

The acceptance limits for both protocols — the tester set, the pass conditions, the protocol administration — are published by third-party child-resistance standards (the U.S. ASTM child-resistance protocol family being the reference most names check). Those limits are the property of the standards bodies and are cited here only as a subject: no ASTM number, version, pilot-tester count, pass rate, or torque limit appears in this article, and nothing in this program is claimed to hold any child-resistance certification. Compliance is confirmed per project, per market, by the brand and its supply chain, against the standard that applies to the product's destination markets.

<pre class="language-mermaid"><code>flowchart LR

A[Closure program<br/>Cap family 7 models<br/>20/410–28/415] –> B[CRC mechanism<br/>no recorded closure<br/>project-level configuration]

B –> C{Two-action protocol<br/>third-party framework}

C –>|Push-turn| D[Push down, then turn<br/>lugs engage on the push]

C –>|Squeeze-turn| E[Squeeze sides, then turn<br/>skirt releases the catch]

D –> F[Torque test<br/>open-close behavior]

E –> F

F –> G[Leakage test<br/>seal holds]

G –> H[Compliance review<br/>per project, per market]

H –> I[Release per project]

</code></pre>

3.5 The recorded closure side

None of that happens in a vacuum — the CRC conversation sits on a recorded foundation. The Cap family carries seven catalog models across neck finishes 20/410–28/415, and Cap/Closure is a recorded component family. The neck finish is the discipline point: a CRC is specified on a finish, against the bottle it must fit, and the head-to-bottle pairing on a wrong finish fails at the fill line. The neck-finish insight covers the thread system and finish pairing rules; a CRC build inherits every one of them before it adds its own protocol geometry.

3.6 Verification hooks: torque and leakage

The recorded quality hooks release the closure: the torque test, which checks the open-and-close behavior against the project's expectation — and for a CRC, the interesting question is how the two-action mechanism behaves while torque is measured, not just how much torque the cap shows; and the leakage test, which asks whether the seal holds once the cap is closed. Both are capability-level — no torque figure, no leak-rate threshold is published — and both are run against the project's actual closure, bottle finish, and fill. Neither check substitutes for the third-party protocol evaluation; the torque and leakage gates release the mechanics, and the standards review releases the compliance.

<pre class="language-mermaid"><code>flowchart LR

P[Product with<br/>concentrated actives] –> Q[Confirm the third-party<br/>protocol per market]

Q –> R[Choose closure platform from<br/>Cap family 7 models<br/>per project]

R –> S[Configure two-action interface<br/>push-turn or squeeze-turn<br/>per project]

S –> T[Torque + leakage gates<br/>capability-level]

T –> U[Compliance confirmation<br/>outside the published record]

U –> V[Release per project]

</code></pre>


What: Verified Program Data and the Verification Hooks

  • Cap family — seven catalog models, neck finishes running 20/410–28/415;
  • Component family — Cap/Closure is recorded in the component register;
  • Verification hooks (capability-level) — torque test and leakage test exist in the quality register, with pass criteria configured per project;
  • Boundary — no child-resistant closure is recorded in the catalog; a CRC mechanism is a project-level configuration. Push-turn and squeeze-turn protocol mechanics, ASTM limits and methods, and all child-resistance acceptance numbers are third-party standards cited as a subject only; this program publishes no CRC number, holds no CRC certification claim, and confirms compliance per project, per market.

Gotchas

  1. No CRC is in the catalog. No child-resistant closure is recorded in the catalog; a CRC mechanism is a project-level configuration — never present CRC as a standard offering from the Cap family.
  2. Zero ASTM numbers are published. No ASTM standard reference, version, tester count, pass rate, or torque limit appears here; the standards are a subject, not program data, and no article sentence may cross that line.
  3. No certification claim exists. Nothing delivered from this program is asserted to hold any child-resistance status; compliance is confirmed per project, per market, by the brand and its supply chain.
  4. Two-action does not mean twice the turn effort. The protocol is a sequence of distinct actions; a cap that resists hard with one action is not a CRC, and protocol choice (push-turn vs. squeeze-turn) depends on the closure platform and the destination market's framework.
  5. Torque and leakage are separate gates. A CRC can open correctly and still fail to seal, or seal perfectly and fail the protocol review; the two capability-level checks release the mechanics, and the standards review releases the compliance.
  6. The Cap family is a size window, not a mechanism claim. Seven models across 20/410–28/415 state the recorded neck-finish range; they say nothing about which cap is child-resistant.
  7. Concentrated actives are a formulation project. The active's risk profile, concentration limits, and label obligations are formulation and regulatory work done per project — the CRC addresses the opening event, not the formula's hazards.
  8. The finish pairs before the protocol. A CRC is specified on a neck finish against its bottle; the head-to-bottle pairing rules apply before any two-action geometry is added.

Related Resources

Sign Up for Our Newsletter

YOUR WISH LIST

  • Your wish list is currently empty.