The six fields that make a request quotable
A request becomes quotable at the moment it stops being a description and becomes a set of numbers. Six fields do most of that work, and all six can be filled in before anybody speaks to anybody. The first is the item, named specifically enough that two suppliers would recognise the same product — not “merch” and not “gifts”, but “cotton crew-neck t-shirt” or “A5 notebook with a PU cover”, ideally with a reference to a product that already exists. The second is the quantity, and the third is the split underneath it: the size breakdown for apparel, the recipient list for gifting, the variant mix for a multi-item kit. A quantity without a split is the single most common reason a quotation has to be reissued.
The fourth field is the decoration, stated as method and colour count rather than as an intention. “Branded” is not a decoration. One-colour screen print on the left chest is a decoration, and it is the difference between an answer and a conversation. The fifth is the delivery point: a named address, or at minimum a named city and the term required. The sixth is the date the merchandise has to be in use, which is not the same as the date of the event and is usually the more useful number, because it is the date from which the schedule is built backwards.
Everything beyond those six is negotiable in the answer rather than required in the request. Packaging, sample requirements, individual personalisation, kit assembly, storage, split deliveries — all of these change the figure, and all of them can be discussed once an answer exists. The mistake is to leave them out of the request and be surprised that they were not included in the price, which is the same mistake as leaving the delivery point out and being surprised that freight appears later as a variation.
- Field one — the item
- Named specifically enough that two suppliers would recognise the same product, ideally with a reference
- Field two — the quantity
- The total unit count, stated as a number rather than a band, a range or an intention to grow
- Field three — the split
- Sizes, variants, recipients or packs — the breakdown that determines which quantities are actually being bought
- Field four — the decoration
- Method and colour count and location, written as a description of the result rather than as a brand instruction
- Field five — the delivery point
- A named address and city, plus the term required where that is not the obvious default
- Field six — the in-use date
- The date the goods must be in the hands of the person using them, not the date the event opens
- Optional but useful
- Budget range, packaging expectation, whether a sample is wanted, and who approves
- Best attached to the request
- Any existing artwork in a production format, with a note on what it is and what is still to change
Two of the six fields cause more friction than the other four, and it is worth knowing why. The split is the harder of the two because it lives in the buyer’s organisation rather than in the request: someone has to decide size distribution, and nobody wants to be the person who chose it. The right way to handle that is to state the split you can commit to and flag it as provisional, rather than to omit it and let a supplier assume an even distribution. An even distribution across a garment run is a real production choice with real consequences at inspection, and assuming it is worse than saying “provisional, to be confirmed by the end of this week”.
The date field is the other one, and the friction there is usually about honesty rather than effort. Buyers frequently put in a date they have not been given, because the event date is the only date anyone can name with confidence. That is fine as long as it is labelled. A request that says “needed for an event on this date” is understood; a request that says “delivery required on this date” is a commitment, and the difference between the two is the difference between a question and an obligation.