Menstrual Panties OEM: Quotation Fields Buyers Send
Menstrual panties OEM enquiries arrive with very different levels of detail. Some include a full specification sheet; others contain a single product name. This page lists the fields needed to quote a disposable nonwoven brief and marks which decisions can wait until sampling.
The distinction between required now and later is practical. A quotation can be prepared without an artwork file, but it cannot be prepared without a size set. Sorting the fields at the first exchange prevents a project from stalling on a document that was never actually needed.
| Field | Status | Supplied by | Used for |
|---|---|---|---|
| F-01 size set | Required now | Buyer merchandising | Quotation and sampling |
| F-02 tier code | Required now | Buyer technical contact | Quotation |
| F-05 pack count | Required now | Buyer merchandising | Quotation and pack plan |
| F-06 carton quantity | Can wait | Buyer logistics | Carton plan |
| G-03 artwork version | Can wait | Artwork owner | Print approval |
| Z-F / Z-R / Z-S | Conditional | Buyer technical contact | Overnight brief only |
Three fields a quotation cannot start without
F-01, F-02 and F-05 are required now. The size set determines how many builds are being quoted, the tier code identifies the range position, and the pack count determines how the order is expressed. Without those three, any total would rest on assumptions.
Buyers who have an existing sheet can attach it instead of filling our fields. We transcribe it into F codes and return the table for confirmation. The transcription is a separate record, so the buyer's original wording remains available if a question arises later.
Fields that can wait until sampling or artwork
F-06 and G-03 can wait. Carton quantity is a logistics decision and artwork version is a design decision; neither changes what product is being quoted. Both are closed later, at the carton plan and at print approval respectively.
Marking them as can wait is not the same as ignoring them. The status column of the table keeps them visible in the project file with a named owner, so they are requested at the right step rather than forgotten until goods are ready.
Enquiry handling sequence
Four steps run for each enquiry. Step 1 logs the enquiry wording and asks the product boundary question. Step 2 requests F-01, F-02 and F-05. Step 3 issues the quotation with the can-wait fields listed as open. Step 4 closes those fields at their own approval points.
Step 1 is where a washable garment enquiry is separated from a disposable brief. That question is asked once, recorded with a date, and not repeated in later exchanges. It is the single most useful line in the whole enquiry record.
- Log the enquiry wording and ask the disposable versus washable question.
- Request F-01, F-02 and F-05, or the buyer's equivalent sheet.
- Issue the quotation with the can-wait fields shown as open.
- Close F-06 and G-03 at the carton plan and print approval.
Steps are enquiry identifiers, not quantities or lead times.
Conditional fields for an overnight range
The Z rows are conditional. If the enquiry concerns an overnight layout, a zone brief is opened and Z-F, Z-R and Z-S become part of the specification. If it does not, those rows are left out of the quotation entirely rather than marked as open.
This is the one place where the field list changes shape between projects. The conditional marker in the table is deliberate: it tells a reader that the absence of a Z row is a decision, not an omission.
Rework caused by an incomplete first exchange
The common failure is a quotation prepared from a product name and a target pack count, with the size set assumed from a previous order. We do not inherit a size set from order history without written confirmation, for exactly this reason.
A second is a can-wait field treated as required, which delays a quotation while an artwork file is chased. The status column exists to prevent both errors: it says what is needed now and what has a later home.
Where the field list is reused
The same list appears on the quotation, the pack plan and the print approval record, with the status column updated at each step. Reusing one table keeps the three documents consistent without rewriting any of them.
For a repeat order the list is reopened and the previously confirmed values are shown for verification. A changed field gets a new value and a dated note. Nothing is silently carried forward, even when the buyer expects an identical build.
A buyer template that uses different field names
Procurement templates rarely use our F codes. That is not a problem. We attach a mapping sheet naming our fields beside the buyer's own columns and leave the template untouched. The attachment is versioned, so a revised template can be compared with the earlier one without guessing which column moved.
The status column is added to the attachment, not to the buyer's document. A field that the buyer marks optional may still be required now in our list, and the difference is stated on the mapping row. Where the two disagree, the buyer is asked to confirm which value governs the quotation.
This approach also makes a repeat enquiry faster. The mapping sheet already exists, so the second project begins with a verification of the confirmed values rather than a fresh transcription. Any changed column receives a new row with a dated note, and the earlier mapping stays available for comparison.