How to Write an EC RFP | Template Items, Recipient Selection, and Pitfalls
"We've been tasked with creating an RFP (Request for Proposal) for building an e-commerce site, but we don't have any past samples in-house, so we're unsure which items to include and at what level of detail." "Even after sending out the RFP, we receive irrelevant proposals from vendors that aren't useful for selection." "There's no clear distinction between an RFP and a requirements specification document within the company."
Introduction
This is a common concern heard from business managers, e-commerce managers, and IT system administrators considering the creation or replacement of an e-commerce site, right at the beginning of the RFP (Request for Proposal) process.
1. What is an EC RFP? | Differences from Requirements Definition Documents and Specifications
An EC RFP (Request For Proposal) is a document used when building or replacing an e-commerce site to present potential vendors with "our requirements," "the content of the proposal you would like to receive," and "the evaluation criteria."
1-1. Differences between RFP, Requirements Definition Document, and Specification Document
The practical workflow progresses in stages, from RFP (request for proposals and initial requirements) → requirements definition document (agreement on requirements) → specifications document (implementation design), with the level of detail increasing progressively.
1-2. Granularity of requirements to include in the RFP
If you try to include detailed functional requirements at the RFP stage, similar to those in a requirements definition document, it will take several months just to create it, delaying vendor selection.




