Disposable Period Underwear OEM: Size and Absorbency Specification
This page covers disposable period underwear OEM: a single-use, nonwoven pull-on brief produced on a hygiene converting line. It is not a washable knitted garment, and the two products do not share a specification sheet. Enquiries that arrive under the general phrase period underwear are checked against that boundary before any quotation work starts.
What follows is the written size and absorbency brief we ask a buyer to confirm before a sample is cut. Every line in it is a field to be filled, not a performance statement. The same table is reused at quotation, at sampling review and at print approval, so a value agreed once stays consistent through the whole project.
| Field | Unit or format | Confirmed by | When confirmed |
|---|---|---|---|
| F-01 size set | Size codes, M to XL | Buyer merchandising | Before quotation |
| F-02 absorbency tier | Tier code from the brief | Buyer technical contact | Before sampling |
| F-03 core option | Option code from the range | Both parties | Before sampling |
| F-04 topsheet | Option code from the range | Buyer technical contact | Before sampling |
| F-05 pack count | Pieces per retail pack | Buyer merchandising | Before artwork |
| F-06 carton quantity | Packs per shipping carton | Buyer logistics | Before order confirmation |
Writing the six fields before a tool is ordered
The brief carries six fields, numbered F-01 to F-06. F-01 is the size set, F-02 the absorbency tier, F-03 the core option, F-04 the topsheet, F-05 the pack count and F-06 the carton quantity. Each field has one named owner on the buyer side and one owner in our project file. A field left blank is recorded as open rather than filled by assumption.
Buyers sometimes send a retail pack image in place of a table. We transcribe the visible wording into fields, then return the table for written confirmation. That exchange takes one round and removes most later rework. The transcribed values are stored as a separate record so the original artwork wording remains available for comparison at print approval.
Grading the size set from M to XL
F-01 is written as a set, not as a single size. A set from M to XL defines how many size codes the order carries, which tooling is shared between them and how many sample pieces each code needs. Changing one size code after tooling has been ordered can affect the others, so the set is agreed as a whole before the first cut.
The grading values themselves are recorded in a separate size table, linked to this brief by the field code. We do not infer a grading from a competitor pack or from a retail label. If the buyer already has a size chart, it is attached to F-01 and used unchanged; if not, we ask for waist, hip and leg opening ranges in the buyer's own format.
Choosing an absorbency tier and a core option
F-02 and F-03 are related but not identical. The tier describes the intended use level in the buyer's range, while the core option describes the construction chosen from our available options. Two buyers may select the same tier and different core options because their shelf positions, climates or pack formats differ.
We keep both as codes rather than descriptive adjectives. A code is unambiguous across languages and survives translation into artwork, carton copy and the order sheet. Any descriptive wording used on a retail pack is reviewed separately at print approval, and it must trace back to a code in this table rather than introduce a new claim.
Steps between a confirmed brief and a first sample
Four steps run in order. Step 1 closes all six fields. Step 2 assigns a sample quantity to each size code in F-01. Step 3 books the converting slot against the agreed core and topsheet options. Step 4 issues the sample set with a record sheet listing the six field values on the first page.
A request that skips Step 1 is held rather than pushed into sampling. Samples built on open fields tend to be re-cut, and a re-cut consumes the same slot as a new project. The record sheet issued at Step 4 is the document used at review, so the sample and the brief always travel together.
- Close F-01 to F-06 in writing and mark any open field.
- Assign a sample quantity to each size code in the set.
- Book the converting slot against the selected core and topsheet options.
- Issue samples with the six field values printed on the record sheet.
Step numbers are process identifiers. They are not lead times or quantities.
Recording deviation between sample and written brief
At review, each checked item is logged as R-01 onward. A log entry names the field, the observed value, the declared value and the person who recorded it. Where the two differ, the entry states whether the brief or the sample will be corrected. No entry is closed by a verbal agreement; the corrected table version is filed with the log.
Deviations are classified by source: a field that was open, a field that was transcribed incorrectly, or a construction choice that produced a different result. The classification matters because only the second type is a transcription error. The other two are decisions, and they go back to the buyer as choices rather than as defects.
Where the same table is used again
The brief is not retired after sampling. F-05 and F-06 feed the carton plan, F-01 feeds the artwork size grid, and the tier code feeds the range structure. Reusing one table prevents the common failure where the pack shows one size set, the carton shows another and the order sheet a third.
If the buyer runs more than one market, a separate brief is opened for each rather than editing the original. Each brief keeps its own field values and its own record log. That separation is also what allows a later order to repeat an earlier specification without rebuilding it from email history.
A completed brief as the project file sees it
A finished brief for this line is a short document. The front page carries the project number, the brief version and the date of the last change. Page two holds the six fields F-01 to F-06, each with a value or the word open, and the name of the person who confirmed it. Page three holds the change notes, one line per amendment, naming the field and the version that replaced it.
The sample record sheet is issued from that document, not written separately. Its first page repeats the six field values verbatim, so a reviewer holding a specimen can see the declared build without opening the email thread. At review, each R entry refers back to a field code on page two. This is why the brief is built before a tool is ordered: a record sheet needs something to record against.
When a second range is opened for the same buyer, a new brief number is issued rather than a copy being edited. The two documents may share five of their six values, but they keep separate version histories. A later question about which pack count was built for which range is then answerable from the file, without reconstructing it from a chain of forwarded messages.