Postpartum briefs and disposable period briefs are often quoted on the same line. Buyers ask whether one production run and one specification sheet can cover both. This page does not restate the construction detail already published on our existing postpartum pages. It is a map: which page answers which question, and which fields have to be answered separately for each brief.
Two distinctions run through the whole index. The first is the product brief, recorded as declared construction options in a project file. The second is the wording a finished pack carries. Those are owned by different people. Keeping the two apart is what lets a buyer extend a range without reopening an earlier specification.
| Question a buyer asks | Page that answers it | What that page covers | Index code |
|---|---|---|---|
| How a postpartum brief is described in a range | /comfort-pants/postpartum-disposable-period-underwear.html | The postpartum brief and its published range wording | N-01 |
| How a maternity supply enquiry is framed | /comfort-pants/maternity-sanitary-pants-bulk-supply.html | Supply-side questions for that range | N-02 |
| How a side-open construction is discussed | /guides/postpartum-disposable-menstrual-pants-side-open-guide.html | One construction option and where it is explained | N-03 |
| Where the two brief families are separated | /blog/period-pants-vs-incontinence-underwear-specs.html | The category boundary and the filing rule | N-04 |
| Where pack and shelf wording is recorded | /blog/us-uk-wording-for-disposable-period-pants.html | Wording columns, not construction | N-05 |
Two briefs that buyers often quote together
A buyer building a range around a disposable pull-on brief will often add a postpartum line in the same enquiry. On paper the two look like neighbours: both are single-use, both are described with a size set and a pack count, and both can appear in one carton plan. It is reasonable to ask whether they can be treated as one item.
The answer in our project file is a split rather than a merge. Two briefs get two records, N-01 and N-02 in the index above, even when the order sheet carries a single header. The shared fields are copied between them; the fields that describe the intended use are not. That is a filing convention, and it is the reason the index exists at all.
Coverage and waistband: where the briefs diverge
The questions a buyer asks about each brief are different. For an overnight period brief the question is where front, rear and side coverage are declared. For a postpartum brief the question is which construction option from the published range is being selected. Those are not two versions of one question, and they are not answered by one value in a table.
This page will not give the coverage detail. N-03 points at the guide that discusses one construction option, and N-01 points at the postpartum brief page. A buyer who needs the detail should open those pages; a buyer who only needs to know where to find it can stop at the index. Repeating the detail here would duplicate pages that are already published.
Pack count and channel differences
Pack count is a merchandising decision, and it frequently differs between the two ranges even when the briefs are ordered together. A care-range pack and a menstrual-range pack can be planned for different shelves and different replenishment cycles. We record the count for each record separately and do not average them into one figure for the order.
The carton plan is the one place where the two records deliberately meet. A buyer shipping both ranges to one warehouse may want one carton format, and that is recorded once and referenced by both files. If a later order separates the ranges, each file still has its own pack count and can be quoted on its own.
Claims belong to the brand, not the factory
What wording a finished pack carries is set by the brand for its own market. Our project file records declared construction options and the fields that describe them; it does not set pack wording for the buyer. Where a buyer asks us to review artwork, we check that the written values trace back to a record, not that the wording is one we would have chosen.
This division is worth stating plainly because a two-brief enquiry is where it most often blurs. One range may carry wording that the other range cannot use, even though the two briefs share a carton. Keeping that wording attached to its own record, N-01 or N-02, prevents a phrase approved for one pack from being copied onto the other at print approval.
Existing pages that cover each brief
The five rows in the index are not a reading list in order. N-01 and N-02 answer range and supply questions. N-03 answers a construction question. N-04 answers where the category boundary sits. N-05 answers where wording is recorded. A new buyer can use the index as a routing table and open only the two rows that match the question in front of them.
We have not created a new specification page here, because the site already carries a set of pages for these ranges. A further page repeating the same construction detail would add a sixth answer to a question that is already answered, and would make it harder for a reviewer to tell which version is current. The index is the smaller and more useful addition.
How we open two project files from one enquiry
Four steps run when a combined enquiry arrives. Step 1 lists the briefs named in the email. Step 2 opens one record per brief and copies the shared fields. Step 3 attaches the relevant index code to each record. Step 4 returns the two records for written confirmation before any sample work is booked.
A buyer can short-circuit the whole exchange by writing one line at the top of the enquiry: two briefs, two records. That single line has become the clearest signal we receive, and it costs nothing to add.
- List the briefs named in the enquiry without merging them.
- Open one record per brief and copy only the shared fields.
- Attach the matching N-01 to N-05 index code to each record.
- Return both records for confirmation before booking sample work.
Step numbers and index codes are process identifiers. They are not quantities or durations.
A short navigation checklist for a new buyer
Before an enquiry is sent, three checks are enough. Name each brief in its own line. State which market each pack is for. Say whether the two records may be quoted in one document. Those three lines let us attach the right index codes on the first pass instead of after a round of clarification.
If the range grows later, the index does not have to be rewritten. A new brief opens a new record and a new row; the existing rows keep their codes. That is the practical reason to keep a navigation page short: it can be extended without being revised.
How the index is extended when a new page is published
An index only stays useful if adding to it does not require rewriting it. When a new page is published for one of these ranges, it receives the next available N-code and one new row. Existing rows keep their codes and their wording. No row is reclassified to make room, and no earlier page is edited to point at the new one. The index grows at the end rather than being reorganised in the middle.
That rule has a consequence buyers sometimes notice: an older page may not link forward to a newer one. This is deliberate. A navigation index can point outward from a single new file, while changing every earlier page each time a row is added would turn a small update into a site-wide edit. The cost is that the index has to be found first, through a sitemap entry or a direct link.
The owner of each row is the person who wrote the page it points at, not the person maintaining the index. When a row becomes inaccurate, it is marked as superseded and a new row is added; the old row is kept so that a reader following an older link can still see what it referred to. In our files that small amount of history has settled more than one dispute about which page was current at the time an enquiry was answered.
N-codes are index identifiers. They are not page versions and are not reused after a row is superseded.
