How Is Child-Resistance Testing Performed on Vape Devices and Closures?

Child resistance sits in an awkward place in hardware development, because it is a property of behaviour rather than of a drawing. A design either resists opening by a young child or it does not, and the only accepted way to find out is to test with real children and real adults under a defined protocol. That makes the requirement expensive to discover late, since a closure that fails usually needs a new tool rather than a small adjustment. The requirement also interacts with usability: a closure that is hard for a child is often hard for an older adult too, and a design that frustrates adults will be defeated by a workaround. At vapodyn, child-resistance questions arise from both design teams and buyers preparing for market entry, so this page answers the five questions asked most often about protocol, design and documentation.

What does child resistance actually require of an electronic device?

Child resistance is a defined performance outcome, not a design feature. The accepted pattern in packaging frameworks such as the ISO 8317 approach and the United States rules at 16 CFR 1700.20 is that a sample of young children is given a defined time to try to open the package, and a sample of adults is then given a defined time to open and, typically, to reseal it. A design passes when children fail to open it at the defined rate and adults succeed at the defined rate. For electronic devices the same logic applies, whether the barrier is a closure, a locking feature or a sequence requirement that must be satisfied before the device operates. The important consequence is that a device cannot be self-declared child resistant on the strength of its features; it can only be declared child resistant after a protocol test with the required panel composition.

How should a test panel be recruited, structured and supervised?

Panel composition is part of the requirement rather than an implementation detail. The protocol typically specifies an age band for the child panel and a separate adult panel, and it may define how many children must fail for the design to pass, along with whether the same children are given a second attempt after a demonstration. Recruitment should be recorded, and children must be tested under supervision with a defined instruction script so that results are comparable between sessions. Adults are usually given a written instruction because the design must be usable by adults without training, and the timing of their attempt should be recorded exactly as the protocol requires. Sessions call for an experienced test supervisor, a defined environment, and the ability to stop a session if a child becomes distressed. Recording the script as well as the outcome is what makes the test defensible.

Which design features support child resistance without harming adult usability?

Effective designs usually rely on a combination of abilities that a young child has not yet developed rather than on raw force. A requirement to perform two actions simultaneously, to align a feature while pressing, or to follow a visual sequence all raise the difficulty for a child while remaining quick for an adult who has read the instruction. Force alone is a poor barrier because a child can apply surprising force, and it is also a poor barrier for adults with reduced hand strength. Where a device uses an electronic lock, the sequence and timing should be chosen so that an adult performing the expected action is never penalised, and there should be no path that bypasses the barrier through normal handling. The design should also be reviewed for defeat by simple tools or by the packaging it arrives in, since a bypass found in the field invalidates the test result.

How should the test be documented for regulators and buyers?

Documentation should let a reviewer establish that the test was conducted as the protocol requires, not just that it passed. A useful file contains the protocol reference and revision, the panel composition and recruitment record, the instruction scripts used for children and for adults, the session records with outcomes and timings, and the identity of the sample tested with its production status. Sample identity matters because a result obtained on hand-built prototypes may not represent production parts, and a reviewer will look for that distinction. Any deviation from the protocol should be recorded and justified rather than removed. The report should also describe the design features that provide the barrier and how they are controlled in production. At vapodyn, the standard is that the file should be sufficient for an independent laboratory to reproduce the test, which is the practical definition of a complete record.

How can child resistance be preserved through manufacturing variation?

Child resistance is preserved by controlling the features that create the barrier, which means identifying them in the drawing and giving each a tolerance and a process control. Typical critical features include the engagement depth of a latch, the stiffness of a spring element, the alignment of a two-step sequence, and the fit between parts that must be manipulated together. Each should have a measured value at incoming or in-process inspection rather than a visual check, because a latch that engages by eye can still release too easily under a child’s repeated attempts. Mould wear and assembly variation are the usual sources of drift, so the control plan should include tooling maintenance intervals for the relevant features. Any mould repair, material change or tool transfer should trigger a review of whether the barrier characteristics changed, and a fresh test if they did. Sampling should reflect that this is a safety property rather than a cosmetic one.