Overnight Period Pants OEM: Planning a Channel SKU Mix
Overnight period pants OEM ranges differ between retail, e-commerce and institutional channels. This page is about the SKU mix each channel needs: pack format, size mix and carton planning. The product is a disposable nonwoven brief, and absorbency tier structure belongs to a separate page.
A single range can serve three channels, but not with one pack plan. Each channel has its own unit of sale and its own carton logic. Writing three plans against one underlying brief is what keeps the range consistent without forcing the packaging to match.
| Channel | Unit of sale | Size mix field | Carton plan field |
|---|---|---|---|
| Retail shelf | Retail pack | G-01 local grid | F-06 packs per carton |
| E-commerce | Shipping parcel | B-01 size mix | B-02 parcel quantity |
| Institutional | Bulk carton | B-03 size mix | B-04 carton quantity |
| Retail, second market | Retail pack | G-01 second grid | F-06 second value |
Retail shelf versus e-commerce
A retail pack is designed for a shelf facing and a local size grid. An e-commerce parcel is designed around a shipping unit and a size mix chosen for online orders. The brief underneath can be identical; the unit of sale is not.
B-01 and B-02 are therefore separate fields from G-01 and F-06. Reusing the retail grid for an online range tends to produce a parcel quantity that does not divide cleanly into the carton. The mismatch is arithmetic and entirely avoidable.
Institutional channel fields
An institutional order is usually planned as a bulk carton with a size mix agreed by the buyer's procurement team. B-03 and B-04 record that mix and the carton quantity. Artwork work is often minimal, but the marking sheet still needs its own version.
Documentation tends to be the longest part of this route. We supply the field list and the approval records as project documents, each tied to the brief version. No new figures are introduced for the channel; values come from the buyer's own schedule.
Channel planning sequence
Four steps apply to a multi-channel range. Step 1 confirms the shared brief version. Step 2 opens one plan per channel with its own unit of sale. Step 3 closes the size mix and carton fields on each plan. Step 4 issues a combined order schedule referencing all three plan versions.
Step 4 is where a mismatch becomes visible. If two channels share a size code but not a pack format, the schedule must show them as separate lines. A single combined line would hide the difference and make a later change impossible to trace.
- Confirm the shared brief version for the whole range.
- Open one plan per channel, each with its own unit of sale.
- Close the size mix and carton fields on each plan separately.
- Issue a combined order schedule referencing every plan version.
Steps are planning identifiers, not quantities or lead times.
Rework points in a channel mix
The first is an artwork version shared across retail and e-commerce packs. The second is a carton quantity copied from the retail plan into an institutional order. Both are caught at Step 3, where each plan's fields are closed against its own channel.
A third appears when a second market is added to an existing retail range. We open a new row with its own G-01 grid rather than editing the first. The two grids then sit side by side on the same schedule, each traceable to its market.
Where the absorbency tier structure sits
Tier codes, size multiplication and SKU codes are defined on the SKU tier page. This page does not restate them. It takes the tier set as given and asks only how each channel packs and ships the resulting rows.
The separation matters because a channel change should not rewrite a range decision. If a buyer adds an e-commerce line, the tier set stays fixed and one more plan is opened. No tier code needs to be re-approved.
Documents at order confirmation
Order confirmation lists the shared brief version and every channel plan version. The schedule is generated from those references. A plan that has no version is not included, which prevents an unapproved pack format slipping into a combined order.
For a repeat season, the plans are reopened and their versions confirmed. A channel that is no longer active is marked retired with a dated note rather than deleted, so the schedule history stays readable.
Adding a channel after a season has started
A new channel added mid-season does not change the shared brief. It creates one more plan with its own unit of sale, its own size mix fields and its own carton fields. The schedule is then regenerated to reference all active plan versions, including the new one.
The check at this point is whether any existing artwork or carton record was created for a different channel and is being reused. A retail pack file is not an e-commerce parcel plan, even when the same size codes appear on both. Step 2 of the planning sequence asks that question explicitly.
At the end of the season, each plan is marked active or retired with a dated note. The tier set stays fixed throughout. A buyer reviewing the season can therefore see which channels ran, which plan version each used, and whether a channel was added late enough to need a separate approval record.