An importer can name the same disposable pull-on brief four ways in one paragraph: pants-type sanitary napkin, sanitary pad pants, menstrual sleeping pants and disposable period underwear. They usually describe one product. The risk is not the vocabulary. It is that a mixed-term enquiry gets transcribed into four different specification rows and quoted four times over.
We map incoming wording to a single enquiry record before any sample work is booked. The map records where each word came from: a category system, a use occasion, a retail shelf or the buyer's own range. Once that origin is written down, a buyer and a factory can discuss one specification without arguing about which name is correct.
| Enquiry wording | Where it came from | What it points to | Map code |
|---|---|---|---|
| pants-type sanitary napkin | importer category wording | pull-on brief construction | I-01 |
| sanitary pad pants | retail shelf wording | pull-on brief in a pad range | I-02 |
| menstrual sleeping pants | use-occasion wording | overnight coverage options | I-03 |
| disposable period underwear | US retail wording | single-use pull-on brief | I-04 |
| private label period pants | buyer range wording | the buyer's own SKU set | I-05 |
Four names for one pull-on brief
I-01 is the phrase most often used in an Asian or Middle Eastern importer's category list. It names a form: a pad-like absorbent product made as a pull-on brief. I-02 comes from a shelf where the same brief sits next to pads in one range. I-03 names an occasion rather than a form. I-04 is the US retail phrase. None of the four is a technical description, and none of them contradicts the others.
A buyer who has collected quotations in several markets often forwards the whole set of phrases in one email. Read literally, the email looks like four products. Read as a set of origins, it is one product described from four different positions in the supply chain. The transcription step exists to turn the second reading into a written record.
Where each term came from
Category wording is written by someone filling a catalogue or a customs-facing product list, so it favours a form description. Retail wording is written for a shopper and favours a short noun. Occasion wording is written by a merchandising team planning a night-time position in a range, so it names when the product is used rather than how it is made.
Once the origin is named, a disagreement becomes answerable. A category phrase and a retail phrase can both be kept, because they do different jobs. Two phrases with the same origin and different forms, on the other hand, are a real conflict and go back to the buyer as a question. We do not resolve that kind of conflict by choosing the phrase we prefer.
What stays constant in the specification
Whatever the incoming wording, the enquiry record holds one set of shared fields: the size set, the construction options selected from the published range, the pack format and the carton format. I-01 to I-05 all point at those same rows. A change to a name does not create a new row; it creates a note attached to the existing one.
This is the part buyers most often ask us to confirm in writing. Their concern is that a supplier will treat an occasion phrase as a new construction and quote a second tooling setup. Our record does the opposite: it states that the construction is unchanged and logs the occasion phrase as a coverage question, which is answered separately before sampling.
What changes when the buyer says sleeping
I-03 is the one phrase that changes a field rather than only a name. An occasion word for overnight wear points at how front, rear and side coverage are declared. We do not publish a value for that. We ask the buyer to confirm which coverage zones apply to the SKU, and we record the answer as a set of declared zones attached to the same enquiry record.
A buyer who does not want to fix the zones yet can leave them open. The sample team then records the construction it used, and the review compares that record with the buyer's later decision. Leaving a zone open is slower than assuming one, but it produces a decision that belongs to the brand rather than to a forwarded email.
Turning a mixed-term enquiry into one RFQ
Six steps turn a paragraph of mixed wording into one RFQ. Each step produces a written line, so a reviewer can see how the final specification was reached. The output is a single record with one set of shared fields plus a separate list of the incoming phrases and their map codes.
The steps are repeated when the buyer adds a market later. That produces a second dated version of the record, not an edited original, so the wording used for the first market stays available for comparison at print approval.
- Copy every product phrase from the enquiry into a list without changing it.
- Assign each phrase one of I-01 to I-05 and write down its origin.
- Mark the single shared construction that all phrases point to.
- Where I-03 appears, open a separate coverage-zone question for that SKU.
- Name the owner for each open field and return the record for confirmation.
- File the confirmed version as record M-01 and book sample work against it.
Step numbers and map codes are process identifiers. They are not quantities, prices or lead times.
Recording a term that does not map
Not every phrase fits the table. A word that describes a different garment, a fabric property or a channel is logged as M-R1 rather than forced into one of the five codes. The log records the phrase, why it was set aside, and the question sent back to the buyer. Nothing is deleted from the original enquiry text.
M-R1 is also where a phrase that looks like a product name but is really a buyer's internal project code ends up. Those codes are useful for the buyer's own filing and harmless in ours, as long as they are not transcribed into a specification row. Marking them once prevents the same code reappearing as a size or a pack format in a later email.
What we ask the buyer to confirm in writing
Three confirmations close the transcription. First, that the phrases in the list all describe one pull-on brief. Second, which of them is the shelf name for the market being quoted. Third, who owns the coverage-zone decision where an occasion phrase appears. A one-line reply to each is enough; a long technical document is not needed.
In our project files, the enquiries that close fastest are the ones where a buyer adds a single sentence naming the market for each phrase. Without it, a phrase from a category list and a phrase from a retail pack arrive with equal weight, and the first round of questions is spent working out which one belongs on the artwork.
A sample enquiry rewritten into one record
Consider an email that opens with a category phrase, mentions a night-time position in the range, closes with a retail phrase, and asks for a quotation on all of it. Read line by line it appears to request three items. Transcribed with the map, it produces one M-01 record: I-01 for the category phrase, I-03 for the occasion phrase, I-04 for the retail phrase, all pointing at the same shared construction row.
The transcription adds one separate line for I-03. Coverage zones for that SKU are recorded as open, with the buyer's merchandising contact named as owner. Nothing else in the record changes. The three incoming phrases are kept verbatim in a list attached to M-01, so a later reader can see exactly which words were in the original email and which code each was given.
The value of this exercise is not tidiness. A buyer who receives a quotation back with the original phrases listed against map codes can check in one read whether the supplier understood the enquiry. A quotation that silently chooses one phrase leaves that check to the sampling stage, where a misunderstanding is far more expensive to correct. We return the M-01 record with the quotation for that reason.
M-01 is a record identifier for the transcription, not a quotation number or an order reference.
