Review for Map Rubber Co., Ltd
A read of the Odoo quote from Spellbound Soft Solutions, and a cheaper way to find out what this project really costs.
The USD 8,000 is not what this will cost. The vendor says so themselves, inside the document she is being asked to sign.
Twelve problems are listed below, worst first. Three of them are enough to stop a signature on their own. The fix is to pay a small fee for a proper requirements study, so she knows the real price before she commits to anything.
"This Quotation creation is done with approx time line with the customization. The final one we may share after doing the requirement gathering. But considering the price of the quote will go higher than this quotation."Spellbound Soft Solutions · Key Notes, page 7
That line is in their own proposal. It says the 8,000 is a guess, the real requirements have not been collected yet, and the final price will be higher.
So she signs, pays 40 percent, or 3,200, and only then finds out the new price. There is no maximum price in the contract. There is no clause that lets her stop and get her money back.
Page 3 says the system will cover Manufacturing (BOM Part). The price table on page 4 does not include it. The detail pages cover only four modules: Sale, Purchase, Accounting, Inventory.
Manufacturing is the main reason a rubber factory buys an ERP. Recipes, bills of material, scrap, batch tracking, curing. None of it is in the price. All of it becomes "customization" later.
That means they control the account her business runs on. If the relationship goes bad, she has a real problem.
She should buy the Odoo licence herself. Her company, her email, her card. Then add them as a partner with access.
The same clause also lets them pause or cancel if she has not bought the licence within 15 days. By then she has already paid 3,200, and there is no refund clause anywhere in the document.
Page 7, bullet 2: the quote was made "with the customization." Page 7, bullet 5: "This contract does not include any customization."
Both cannot be true. When a contract is unclear, the vendor decides what it meant. Anything she asks for after signing becomes customization at 2,000 a month.
No list of what gets built. No deadline. No end date. It just runs every month until she stops it.
Customization should be quoted item by item at a fixed price, against a written list. A monthly fee pays them to take longer.
Six modules, data migration, testing and training for five people in 24 days. That is four days per module. Real Odoo manufacturing projects take 60 to 120 days.
Put their own two prices next to each other:
The project costs about 3.7 times what their own developer costs. Either the 8,000 has a lot of margin in it, or the 24 days is not real. Ask them which, and ask if customization can be billed at 91 a day instead.
The schedule is 40 percent on signing, 30 percent after 15 days, 30 percent before go live. The middle payment is 2,400 for fifteen days going by on a calendar. They do not have to deliver anything for it.
Seventy percent is paid before go live. There is no test she signs off on. There is no definition of finished. Nothing is held back for after go live, which is exactly when problems show up.
An Indian company, a Thai client, and payment to a bank in Ahmedabad. The document does not say which country's law applies, or where a dispute would be settled.
There is no way to cancel. There is no refund. If the work stops after she has paid 70 percent, her only option is to sue in India.
The website clause shows Map Rubber already runs Odoo 16. Moving a live system with real orders, stock and accounts is much harder than starting fresh.
"Data Migration" is listed under every module. It is never explained, never counted in records, and never priced. Nobody has said who cleans the data, or what happens to history that does not transfer.
"2 Months Support is free" does not say what support means. Bugs only, or changes too? Which hours? How fast do they reply?
Maintenance is "2500USD in one time payment." For how long? Covering what? Odoo version upgrades are the expensive part and they are not mentioned at all.
It stops her sharing their proposal. Nothing stops them sharing her customer list, her prices, or her rubber formulas. That is exactly what an ERP company gets access to.
There is no data protection clause either. Thailand has a data law, the PDPA, and it applies when personal data goes overseas.
No date. No quote number. No company registration number. No tax number for either side.
It says the price is valid for 15 days from the date of issue, but no date is printed on it.
It says she owns the custom code, but nothing says when they hand it over, or where it gets stored.
The numbers marked as theirs come straight from the proposal. The customization and website ranges are our estimate, built from their own 2,000 a month rate applied to work the proposal openly excludes. They are a guide, not a competing quote. The point is the gap between the headline price and the real price.
Do not sign the 8,000. Pay for a short requirements study instead. Every serious Odoo firm offers this, and Spellbound already said in writing that requirement gathering is needed. So they cannot object to being paid for it.
The fee comes off the project price if she goes ahead with them. She owns the document, and that is written down before she pays.
What the study must give her:
Why it works: she owns the document, so she can send it to two other Odoo firms and get fixed quotes on the same scope. Tell Spellbound that up front. It makes the study more honest.
The fee is small enough that walking away costs almost nothing. That is the whole point. Right now walking away costs her 8,000 and a deposit she cannot get back.
Two messages. Send the short one first. If they reply, send the long one. Replace the name at the bottom before sending.
Hi Sujeet, Thank you for the proposal. Before we go further I have two questions. 1. Your Key Notes say the price will go higher than this quotation. Can you confirm what the final price range is? 2. Your Executive Summary includes Manufacturing (BOM Part), but the price table and the module details do not. Is Manufacturing included in the USD 8,000, yes or no? I would rather pay you to do a proper requirements study first, so we both work from a final number. Can we discuss that?
Dear Sujeet, Thank you for the proposal for Odoo 19 Enterprise. We are serious about doing this, but I cannot sign the document as it stands. Please help me with the following. 1. PRICE Your Key Notes say: "considering the price of the quote will go higher than this quotation." So the USD 8,000 is not final. I cannot sign a contract and pay 40 percent against a price that you have already said will change. 2. MANUFACTURING Your Executive Summary includes Manufacturing (BOM Part). The price table and the module details do not. Manufacturing is the main reason we need this system. Please confirm in writing whether it is inside the USD 8,000 or not. 3. CUSTOMIZATION One bullet says the quote was prepared "with the customization." Another bullet says "This contract does not include any customization." Please confirm which is correct. 4. WHAT I WOULD LIKE TO DO INSTEAD Before we commit to the full project, I want to pay you for a requirements study. Fixed fee, 5 to 10 working days. I am willing to pay USD 1,000 to 1,500, credited in full against the project if we proceed with you. The study should give us: - A map of how we work today - A list of everything standard Odoo cannot do for us, each item with a fixed price - A data migration plan from our current Odoo 16, with record counts and who cleans the data - A scope that states clearly whether Manufacturing, CRM and Reporting are in or out - A final fixed price and a realistic timeline - The Odoo licence and hosting cost per year, listed separately We will own this document. 5. ODOO LICENCE We will buy the Odoo Enterprise licence in our own company name and add you as a partner with access. We cannot have the subscription held under your account. 6. CONTRACT TERMS If we proceed, we will need these in the agreement: - Fixed price on a fixed scope, with customization quoted per item, not per month - Payment 20 / 30 / 30 / 20, with the last 20 percent paid 30 days after go live against an acceptance test we sign - Milestones tied to delivered work, not to days passing - Governing law and dispute resolution in Thailand or Singapore - A mutual confidentiality agreement covering our data as well as your proposal - The right to cancel, with a refund of fees not yet earned - Source code placed in a repository we control Once I have the requirements study I can approve the full project quickly. I would rather pay you properly for good scoping than argue about change requests later. Best regards, [Your name] Map Rubber Co., Ltd
| Clause | Change needed |
|---|---|
| Price | Fixed price on a fixed scope. Customization quoted per item. Remove the open-ended $2,000/mo. |
| Payment | 20 / 30 / 30 / 20. Last 20 percent paid 30 days after go live, against a test she signs. |
| Milestones | Tied to work delivered, not days passed. Remove "30% after 15 days". |
| Licence | Map Rubber owns the Odoo account. Vendor gets partner access only. |
| Code | Pushed to a repository she controls from day one, not handed over at the end. |
| Support | Maintenance defined: yearly fee, reply times, what is covered, what is not, upgrade policy. |
| Law | Thailand or Singapore. Not India. |
| Data | Mutual confidentiality plus a data clause covering PDPA. |
| Exit | Right to cancel, refund of unearned fees, and a data export on the way out. |
| Delays | A small credit for late delivery. It changes how they behave. |
| Team | Named people, with the developer's level written into the contract. |
Check that Spellbound is a listed Odoo partner at odoo.com/partners, and see what level they are.
A company that wants to hold her Odoo subscription while not being an official partner is a much bigger risk than the contract wording alone suggests.