A 50-person services firm in Bangalore runs ₹2 crore annual revenue across 12 clients. Their finance director calculates the Odoo base license at ₹12,000 per seat and signs a three-year deal. By month four of year two, after custom tax modules for GST reconciliation, payment gateway glue-code, and Shopify inventory sync, the actual bill sits at ₹35 lakh. The vendor lock-in has calcified: swapping invoicing modules out breaks GL reconciliation; extracting clean CRM data costs a retainer; exiting the contract triggers penalties on 'active customizations.' This pattern repeats across Odoo and Zoho One implementations. The trap is not the base price—it's the questions nobody asks before go-live. Customization costs hide in module dependencies. Exit friction multiplies when compliance rules (tax validation, e-signature audit trails, regional payment gateways) force proprietary integrations. Year two becomes financially inevitable; walking away becomes ruinously expensive. Before you sign a consolidation contract, run this 15-question scorecard. It will expose the actual cost and the real exit cost. Some decisions will still favor Odoo or Zoho One. But you will not be surprised in month five of year two. The Module Dependency Trap: Which pieces will you actually need? Bundled platforms sell on breadth. You get accounting, inventory, sales, HR, fulfillment, all in one place. What you do not get is clarity on which pieces are tightly coupled to which others. Ask these questions: If you use only invoicing and CRM, can you disable inventory, manufacturing, and warehouse modules without breaking GL reconciliation? Some platforms allow silent disabling; others charge for 'modules in license' even if unused. Odoo charges per module per user. Zoho One bundles all modules but customization to skip unused pieces often requires development work. Does your payment gateway integration (Razorpay, Stripe, HDFC Nodal) sit on a native connector or on Zapier-style middleware? Native connectors are included; middleware (even if free-tier) introduces a third-party dependency and debugging surface. The moment the middleware vendor changes their API (common), your invoicing flow breaks. You are responsible for the repair, not Odoo or Zoho. If you need India GST reconciliation with GSTR-2B automated matching, which platform owns that logic—Odoo core, a partner app, or a custom module the partner builds? Partner apps (Odoo Marketplace) and custom builds introduce perpetual support costs. GSTR-2B matching rules change quarterly. If Odoo core does not own the logic, you hire someone every quarter to patch it. Can you run invoicing without the full CRM? Some firms invoice passively (API-driven, event-based) and do not need a sales pipeline tool. If invoicing is hard-wired to CRM stages, you pay for and maintain CRM functionality you will never use. The actual implementation cost is not the base license. It is the sum of: base license + modules you cannot avoid + integrations you must custom-build + quarterly patch cycles to maintain compliance. Regional Tax and Compliance: Where proprietary costs compound Southeast Asia runs on hyperlocal tax rules: India has GSTR-2B/2A matching, Indonesia has e-Faktur with NPWP validation, Malaysia uses real-time SST declaration. If your platform does not natively support these, you will hire a consultant to build custom logic. That logic will break when the government changes the rule (common, quarterly updates). Then you hire them again. Ask: Does the platform have a native, government-approved real-time tax ID validator for India (GSTIN), Indonesia (NPWP), Malaysia (SST number)? 'Native' means built-in, updated by the vendor, no custom code. If the answer is 'via a partner app' or 'custom module,' budget ₹2–5 lakh for build and ₹30–50K quarterly for maintenance. If you invoice across India and Indonesia, can a single invoice line split GL entries for CGST, SGST, and e-Faktur PPN in one transaction? Most platforms can do one or the other. Multi-region split invoicing usually requires custom development. Does the platform offer audit-trail compliance for Malaysia's PDPA (personal data) and Singapore's tax-law e-signature requirements? Orin's e-signature module logs full audit trails; Odoo and Zoho require DocuSign or PandaDoc integration (additional cost, additional audit surface). Is real-time tax validation included, or does the platform batch-validate at submission time? Real-time catches fraud and invalid IDs before invoice save. Batch validation means you discover errors after the fact, during audit reconciliation. That costs weeks of cleanup. Payment Gateway and Reconciliation: The hidden integration cost Invoicing is only half the flow. The other half is payment capture, reconciliation, and GL posting. If the platform does not natively integrate your payment gateway, you will build it with Zapier, Make, or n8n. At 500+ invoices monthly, that integration becomes unreliable: payment notifications ar