What the file states, and what it leaves open
Put the two columns side by side and the shape of the job appears immediately.
| The file states | The file does not state | Who has to close it |
| Sterilization method — for a laser fiber accessory, normally ethylene oxide | The cycle that method implies for this load | Both parties, against the customer’s validated process |
| A shelf-life claim in months | Which samples prove it, and when they were taken | The customer’s file; we supply configuration and records |
| Pouch dimensions and pack quantity | The coil diameter a radial fiber can be wound to inside it | Us, within the geometry the drawing allows |
| Label content and language set | Which of those items print on the pouch itself | Both parties, at the print proof |
| UDI carrier to print | Whether the carrier resolves to one lot or three | Both parties, before artwork is released |
| A lot numbering convention | What a lot actually is — fiber run, pack run, or sterilization run | Us, and it has to be written down |
Nothing in the left column is negotiable by a supplier. Nothing in the right column can be closed by the customer alone, because they are not standing on the line. That asymmetry is the whole job.
The seal window is an output, not a setting
For two decades the packaging standard had two parts. One covered materials and the sterile barrier system; the other covered validation of the forming, sealing and assembly processes. What sat outside both was the question every project actually starts with: where does the process window come from in the first place?
That gap closed on 17 September 2026 with the publication of ISO 11607-3, which covers process development for forming, sealing and assembly using heat-sealing technologies, and which explicitly sits before validation. Its logic is worth stating plainly, because it changes what a supplier owes a customer. Development starts from the predetermined sterile barrier system specification — the seal requirements, the materials, the forming requirements, and where relevant the contents — and works outward to a documented process specification, inside a formal quality system, with statistically valid sampling rationales and validated test methods. Annexes support the practical work: guidance on establishing process parameters, minimum sealing equipment features needed for later validation and monitoring, and a worked FMEA on a sealing process.
Two consequences land on an OEM configuration.
The first is that a new pouch size is not a new part number. It is a new sterile barrier system specification, and under Part 3 the sealing process has to be developed from it before anyone can validate it. Any customization that touches pouch, coil or connector geometry moves the project by that much on its own; a supplier who treats the change as a print run has skipped the step the standard now names out loud.
The second is the relief clause, and it is the one that makes a project affordable. The same document accepts that a process which has already been validated under ISO 11607-2 stands as evidence that suitable development took place. So the opening question in a configuration project is not “can our sealer hold this temperature.” It is “does this configuration inherit a developed process, or does it need one?” Answering it early is the difference between a two-week pack and a two-quarter one, and it is the reason a supplier should ask to see the customer’s sealing process specification rather than a pouch catalog number.
The cycle in the file is a load-specific number
Ethylene oxide qualification under ISO 11135, using the overkill approach that most of the industry runs, has a structure worth knowing even if you never perform it. Three consecutive half-cycles must show complete kill of the biological indicators placed in the hardest-to-sterilize location. A fractional cycle with recoverable survivors is run as well, to demonstrate that the recovery method itself works. The routine exposure time is then set at at least double the half-cycle minimum.
The detail that surprises people is where complete kill actually sits. Half of a twelve-log target is not six logs. For a biological indicator carrying a million spores, complete kill in practice appears around an eight-log reduction, because at six logs you would still expect roughly one surviving spore per indicator and see growth in most of them. A project that assumes a clean six-and-six is assuming a shorter cycle than the evidence supports.
Now the part that belongs in a configuration conversation rather than a microbiology one. The standard defines the reference load as the most difficult combination of products to be sterilized, and it expects that load to be identified with the customer. Internal challenge devices go into the hardest location in the load; external devices sit on the pallet surface; and the qualification can go further and establish a relationship between the two, which is what allows routine monitoring to be performed from outside the carton instead of by opening boxes. Every one of those arrangements is tied to a physical configuration — how the pouches are oriented, how the cartons are stacked, how full the chamber is.
So when an OEM asks us to change a carton count, a pouch orientation or a pallet pattern for shipping efficiency, the honest answer is not “sure.” The loading pattern is inside the customer’s validated cycle. Change it far enough and the configuration that was qualified is no longer the configuration being shipped, which makes it a revalidation question, not a logistics one. A supplier who raises this before the change is protecting the customer’s file; one who never raises it is quietly spending the customer’s compliance margin.
Three lot numbers, one pouch
A single sterile pouch of a radial fiber is the meeting point of three runs that happened at three different times: the fiber run, the assembly and packing run, and the sterilization run. The labeling on that pouch carries one lot field, and a customer’s file assumes that field can be resolved backwards through all three.
This is not paperwork aesthetics. The reason the field matters is that a pouch defect is a lot-level event, not a unit-level one — which is why the receiving side is taught to decide by lot number and UDI rather than by inspection of the pouch in hand. A supplier whose assembly lot and sterilization lot cannot both be recovered from the printed field has produced a pack that looks complete and cannot be traced, and that failure only becomes visible during an investigation, which is the worst possible time to discover it.
Two practical consequences for the configuration:
Write the lot definition down before the first sterile run, not after. “One lot per pouch” sounds unambiguous until someone asks whether lot means the fiber that went in or the pouch that came out. Both readings are defensible; only one of them satisfies the customer’s file, and the print proof is where the wrong reading becomes expensive.
Keep the end-to-end map on the configuration sheet. If the customer’s file already defines the convention — and a file that has been through an audit usually does — the configuration simply follows it. If the file is silent, the supplier proposes a definition and the customer’s regulatory owner signs it, because the obligation to trace resolves to the legal manufacturer, not to the pack house.
Test the pack you ship, not the pack you made
The last piece of the configuration is the evidence set, and here a supplier’s habit and a customer’s file tend to disagree in a very specific way.
Package performance, seal strength and integrity testing are commonly run on samples that have been through the sterilization process the device is specified for, at the exposure that represents the worst case, in the configuration that is hardest to process. Ageing studies run on sterilized packs as well. Distribution simulation follows the actual route, whether that is an ASTM D4169 sequence or an ISTA procedure, and it covers the complete packaging configuration — not a representative pouch.
The failure modes that testing labs see most often in this area are consistent: testing at the nominal sealing settings instead of across the window, choosing an integrity method that cannot detect the defect being guarded against, and excluding the heaviest or sharpest configuration from the sample set. For a coiled fiber assembly the last one is not hypothetical, because the pack has to hold a length of glass that would rather be straight.
The configuration question to settle with your supplier is therefore short and specific: are the samples you are going to test sterilized, worst-case, and built the way my cartons will actually be built? If the answer is no for any of the three, the report is evidence about a different product.
What we ask for before building a configuration
Five items, in this order, because each one changes the answer to the ones after it.
- The sterilization method and the cycle reference the file relies on, so the pack configuration can be checked against a qualified load rather than against a preference.
- The sealing process specification, or a statement that none exists for this configuration — which turns the project into development work before it becomes a pack.
- The shelf-life claim and what supports it, so the packaging specification and the claim stay attached to each other.
- The lot convention and the UDI carrier, so the print is written once.
- The distribution route, including the carton the clinical customer will actually open, since protective packaging follows the route and not the drawing.
The six delivery forms these projects usually fall into are set out on the OEM partnerships page; the files themselves live in Downloads, and the ordering ladder is on the FAQ. If the open question is still which carton to order rather than how to configure it, the packaging comparison — sterile packed against non-sterile bulk, and what each carton’s label commits you to — is the piece to read first.
Where a configuration project actually goes wrong
Quoting the pack before reading the file. A quote built on a stock pouch and a standard cycle is a number nobody can hold you to and nobody can plan around. It survives until the first audit.
Filling in a blank field alone. A shelf-life claim, a sterilization method symbol and a lot convention are all things a supplier can print. Printing one the customer’s file does not support converts a packaging job into a claim the supplier cannot defend, and it lands on the legal manufacturer’s desk as a nonconformity.
Treating a load change as logistics. Covered above, and worth repeating because it is the one that gets discovered months later.
Matching the pouch to the fiber instead of to the developed window. The pouch has to satisfy a validated sealing process and a sterilization method, and only then fit a three-meter coil of glass inside it. Treated in the other order, a perfectly good pouch becomes a process development project.
Which brings it back to the sentence the whole project turns on. A supplier building a sterile single-pack configuration around someone else’s file is not choosing packaging. They are transcribing a set of claims into a physical object, and the professional part of that job is knowing which fields are theirs to fill in and which ones have to be handed back with a question attached.
This article describes standards, a process framework and a project timeline. It is not legal or regulatory advice, and the configuration that satisfies a given regulatory file must be confirmed with the responsible manufacturer’s own quality and regulatory functions.