Disposable Period Panties OEM: Building a Size Set
Disposable period panties OEM is US retail wording that often appears in enquiries for a single-use nonwoven brief. It can also mean a washable knitted garment, so we confirm the product boundary before quoting. On this page the phrase refers only to the disposable line, and the subject is how a size set is graded.
A size set here is not one measurement repeated at several scales. Waist, hip and leg opening are graded together, in one table, before tooling is ordered. Treating them as three separate decisions is the most common source of a sample that fits in one dimension and not the others.
| Size code | Waist field | Hip field | Leg opening field |
|---|---|---|---|
| S-M | W-1 declared range | H-1 declared range | L-1 declared range |
| M | W-2 declared range | H-2 declared range | L-2 declared range |
| L | W-3 declared range | H-3 declared range | L-3 declared range |
| XL | W-4 declared range | H-4 declared range | L-4 declared range |
| XL+ | W-5 declared range | H-5 declared range | L-5 declared range |
Why waist, hip and leg opening are agreed as one table
The three columns are read as a row. A row defines one size code, and the tooling for that code is cut against all three values at once. If a buyer approves the waist column first and returns to the other two later, the table is not yet complete and no tooling is booked.
We ask for the buyer's own size chart wherever one exists. It is attached to the brief as a single document and transcribed into W, H and L fields without reinterpretation. Where no chart exists, the table is filled in a joint session and returned for written confirmation.
Numbering the rows before the first cut
Rows carry size codes rather than descriptive labels. W-1 to W-5, H-1 to H-5 and L-1 to L-5 are field identifiers tied to those codes. If a row is added or removed, the table gets a new version and the change note names the affected row.
This is also how a sample set is counted. Each row needs its own sample pieces, because a check on one size code does not stand for another. The sample request lists the rows explicitly so the review sheet can be prepared with the same structure.
Checking a sample against the grading table
At review, the observed values are written beside the declared ones for each row and each column. The record is a comparison, not a verdict. Where a difference is found, the entry states whether the table or the sample will be corrected, and the corrected version is filed.
We keep the comparison sheet with the physical sample set. A summary sent by email without the sheet tends to lose the row references, which makes a later order hard to reproduce. The sheet also carries the brief version, so two runs can be compared directly.
Recording a deviation in one dimension
A deviation is logged against its own column code. A difference in W-3 is not described as a general fit issue, because that wording would hide where the change actually sits. The log entry names the column, the row, the declared value and the observed value.
Classification follows the same rule as the rest of the brief: open field, transcription error or construction choice. Only the second is an error. The other two go back to the buyer as decisions, with the affected row identified so the rest of the table stays valid.
Using the published size guide as a reference
Our existing size guide page is a general reference for how size codes are described on this site. It is linked from this page as background reading. It is not a substitute for a buyer's declared table, and nothing from it is copied into a project brief.
Where a buyer's chart uses different code names, we keep the buyer's names and add a mapping column rather than renaming them. That avoids two teams using the same code for different ranges, which is a surprisingly common cause of a mismatched repeat order.
Where the grading table is used again
The agreed rows feed the artwork size grid, the sample request and the carton plan's size mix. Reusing one table keeps those three documents consistent. A change made only in artwork, without a new table version, is caught at print approval and sent back.
For a second range under another label, a new table is opened even if the values are identical. Each brief keeps its own version history. That separation lets one range change its size mix later without silently altering the other.
Version history of a grading table
A grading table is versioned as a whole, not row by row. When L-3 changes, the table becomes a new version with a note naming that field. The earlier version stays in the file with its own sample record sheet. This makes it possible to say which table a particular specimen was cut against, even when only one of fifteen values moved.
Artwork approval references the table version on its first page. A size grid in a pack file can be compared against that version field by field. Where the buyer's local chart uses different code names, the mapping column is part of the same check, so a translated code cannot drift away from the field it represents.
At goods inspection, the record sheet from the approved version is the reference again. A buyer who has since opened a second range with a different size set can still see which set the current order was built from. That is the practical reason for keeping version numbers on a table rather than on an email subject line.