Why merch RFPs fail differently from other-category RFPs
The shape of a merchandise RFP is unusual among B2B procurements because the cost of the product is not the cost of the service. A software RFP compares licences, support and integration cost against a defined specification and the comparison is usually clean. A logistics RFP compares rates, transit times and service levels against a defined lane and the comparison is usually clean. A merch RFP compares the unit-cost line, the setup line, the decoration line, the freight line, the packaging line, the artwork line, the defect allowance, the payment terms, the lead time and the pilot result, and the comparison is rarely clean because no two vendors price the same spec against the same line structure unless the RFP forces them to.
The forcing function is the response format. A merch RFP that returns responses in the vendor preferred shape returns offers that are not comparable, and a buyer who scores them against a single scoring matrix is scoring comparability rather than merit. The fix is to publish the response template with the RFP, with each line pre-named, each line pre-labelled with the unit and currency the vendor must price against, and each line pre-padded with the buyer-side assumption. A vendor that refuses the template is a vendor whose offer cannot be compared, and a buyer who accepts the refusal is a buyer who has chosen to take the offer on trust.
The second unusual feature is the weight. A software RFP weights functionality, support and cost; a logistics RFP weights rate, transit and reliability; a merch RFP should weight execution, sample quality, brand governance, security and commercial terms — and the weights are programme specific in a way other-category weights are not. A conference programme with a brand-sensitive cohort needs higher weight on brand governance than a partner programme with a confidentiality-sensitive cohort needs higher weight on security. The right move is to set the weight in the RFP against the actual risk the programme carries, and to publish the weight so vendors can adapt their bids to the categories that will be scored highest.
- Forcing function
- Publish the response template with each line pre-named and pre-labelled
- Risk-adjusted weight
- Set the weight against the actual risk the programme carries — not against industry default
- Pilot round
- 3 SKUs, 2 decoration methods, 150–300 units, 2 delivery destinations, tight deadline, written acceptance checklist
- Round count
- Usually 2 rounds: written proposal + sample, then pilot or reference before award
- Reference format
- Two per vendor, with the contact named and permission to call in writing
- Response window
- 10–15 working days for the written round; 30–45 days for the pilot round
- Bid-comparability test
- All offers should arrive on the same template; offers off-template are scored zero on comparability
- Decision documentation
- Each score attached to a document clause or sample evidence