Odoo ERP · Buying
What to Put in an Odoo RFP So Proposals Are Comparable
· Updated · 2 min read
An RFP that says “implement Odoo” receives five proposals for five different products. Name the documents that must exist on go-live day, and the ones that must not.
Write processes, not a module shopping list
Describe how a sale becomes a delivery and an invoice today, including the exceptions that happen every week. Ask the partner which of those are standard and which are custom. A list of app names invites a list of app names back.
Give volumes: orders a day, warehouses, companies, users who will actually log in. A quote without volumes is a guess, which is why timelines slip.
Say what is out
State the integrations, the portals, and the reports that are not in this phase. Partners will still mention them. They should appear as options, not inside the mandatory total.
Ask for the same lines you would demand in a quote: data ownership, environments, hypercare, and whether licences are extra.
Score the first release, then the price
Compare the sentence each partner uses for go-live. The prices are comparable only after that. India implementation typically costs ₹2–15 lakhs before licences, hosting, and training.
If writing the RFP is the blocker, a free audit produces the first-release sentence you can send to more than one partner.
Frequently Asked Questions
How long should an RFP be?+
Long enough to describe the weekly documents and the volumes. A 60-page feature matrix produces 60-page proposals that still disagree.
Should we name Odoo.sh or self-hosting?+
Ask the partner to recommend one and to say who restores a backup. You can state a preference if you already have one.
Do we have to take the lowest price?+
No. Take the proposal whose first release matches the documents you cannot run without.