Six things across every Odoo engagement.
Most Odoo partners say they "implement Odoo." That's not a service — it's a job description. Here's the actual surface area of what we do, what's in scope for each, and the technical depth behind it.
Discovery & Design
Map the operation before touching the platform. Most Odoo failures start here — at the moment a partner skips this step.
Our angle
Most Odoo partners walk in with a demo and start configuring on day one. We walk in with questions and don't touch the platform for two to four weeks. Functional consultants document workflows, edge cases, and the terminology your team actually uses. Engineers join early — not at the build phase — to flag what's standard configuration vs. what needs custom work.
The output is a phased plan with honest scope, cost, and timeline. Not a sales proposal. A real plan that tells you what's likely to work, what's risky, and what would be cheaper to solve outside Odoo.
What's in scope
- Process mapping Current state of every workflow that touches the new system.
- Fit-gap analysis What standard Odoo handles vs. what needs custom development.
- Data model design How your entities map to Odoo's, including the gotchas.
- Solution architecture Module selection, integration points, deployment topology.
- Phased plan Phase 0/1/2 breakdown with scope, cost band, and timeline per phase.
- Risk register Honest assessment of what could go wrong and how to mitigate it.
If discovery feels expensive, the implementation will feel more expensive. Discovery is the cheapest place to find scope problems.
Configuration
The seventy percent of Odoo that ships out of the box, set up properly. The unsexy work that determines whether the system actually fits your business.
Our angle
Configuration is where most implementations quietly go wrong. Not because the work is hard — because it's done by people who know the platform but don't know your business. Wizards get clicked through. Default settings get accepted. Three months later your team is fighting the system because nobody asked them how they actually work.
We configure with operators in the room. Functional consultants who understand your industry sit alongside the people who'll live in the system every day. Decisions get made with context, not by guessing what's "best practice."
What's in scope
- Module selection & activation Sales, Inventory, Purchase, Accounting, HR/Payroll, Manufacturing, POS, Project, Website, Marketing — and the 30+ others.
- Master data setup Chart of accounts, customer/vendor structures, product hierarchies, warehouse zones, tax rules.
- User access & security Roles, record rules, multi-company access, approval matrices.
- Document templates Branded quotes, invoices, purchase orders, payslips. Localized for your countries.
- Localization & compliance Country-specific tax, fiscal calendars, regulatory reports.
- User training Role-based training for the people who'll actually use the system.
Phase 1 is always stock Odoo configured well. We don't touch custom development until configuration is live and proven in production.
Customization & module development
The custom code that makes Odoo fit your business. The work most Odoo partners can't deliver — and the reason most implementations stall at 70 percent of the way there.
Our angle
Most Odoo partners are configurators with a thin technical bench. When the standard module doesn't fit, they call it scope creep, recommend a workaround, or quietly disengage. The deal moves to a different partner who promises custom work, who's also a configurator, and the cycle repeats.
We've been a product engineering firm for 25 years. Custom Python, JavaScript, and database work isn't a stretch — it's our default capability. New modules, modified workflows, computed fields, business logic in code — these are well-trodden ground for our team, not a risky engagement we pad with disclaimers.
What's in scope
- New custom modules Built from scratch when the workflow doesn't exist anywhere in Odoo's catalog.
- Modified workflows Inheriting from standard modules, changing behavior, preserving upgradability.
- Custom fields & views Form, list, kanban, gantt, calendar — whatever the user actually needs to see.
- Computed fields & constraints Business logic where data is read or written, not in spreadsheets.
- Custom reports QWeb-based or PDF-rendered, branded, with real data not just summaries.
- API endpoints REST and JSON-RPC endpoints exposed where other systems need them.
- Frontend customization OWL components, custom widgets, embedded experiences.
- Performance optimization ORM tuning, query optimization, caching where it pays off.
Custom modules are written to survive Odoo version upgrades. We inherit, we don't fork. Your custom work doesn't lock you out of future Odoo releases.
Integrations
Real two-way connections to the tools your business runs on — ecommerce, marketplaces, payments, logistics, messaging. Not the brittle connectors that break in 90 days.
Our angle
Most Odoo "integrations" are off-the-shelf connectors that move orders between systems. They handle the happy path. They fail at edge cases — partial fulfillment, returns, multi-currency reconciliation, settlement matching, the actual cases that make integration valuable.
We build integrations that handle the unhappy paths. Real two-way sync, error handling, retry logic, observability. When something goes wrong (it will), the system tells you what failed and why. When it works, it works without anyone watching it.
What's in scope
- Ecommerce platforms Shopify, WooCommerce, Magento, BigCommerce — full bidirectional sync of products, inventory, orders, customers.
- Marketplaces Amazon (FBA + FBM), Walmart, eBay — including settlement reconciliation and channel-level P&L.
- Payment gateways Stripe, PayPal, Razorpay, Authorize.net, regional gateways.
- Logistics & 3PL Shiprocket, ShipStation, ShipBob, custom 3PL APIs, regional couriers.
- Messaging WhatsApp Business API, Twilio SMS, transactional email, conversation routing back into Odoo.
- Other ERPs NetSuite, Sage, QuickBooks — for migration, parallel run, or hybrid environments.
- Internal systems Custom REST/JSON-RPC endpoints, webhook handlers, message queues, data warehouses.
- Single sign-on SAML, OAuth, OpenID Connect — Okta, Azure AD, Google Workspace.
Every integration ships with logging, retry logic, and alerting. When something fails, your team knows immediately — not three days later when a customer complains.
Workflow automation & AI
The actions that should happen without anyone clicking — and the AI-connected delivery model that lets us ship customizations in a fraction of the usual time. Both, where the ROI is real.
Our angle
"AI for ERP" is everyone's pitch deck right now. Most of it is hand-waving — promises of intelligence wrapped around tools that mostly do scheduling. We're skeptical of AI features that don't have a measurable outcome. Skeptical, not opposed.
We build automation where it pays for itself. Document AI for invoice extraction. LLM-powered ticket triage. Forecasting where the data justifies it. Boring rule-based automation where AI is overkill. The question we ask first: does this remove enough manual work to justify the build cost? If not, we skip it.
But there's one place AI has changed how we work, not just what we build for you — and it's worth being specific about.
We connect Claude directly to your Odoo instance.
Using an MCP server, we link Claude to a connected Odoo instance — securely, with database credentials scoped to the engagement. This isn't a code assistant that writes snippets a developer copies over. Claude reads your live data model and builds the customization against it.
The clearest example: invoice and report customization. A customer hands us the PDF template they use today. We feed it to Claude, which generates a matching QWeb report and deploys it to a staging instance for review. Work that traditionally takes 8–15 hours lands in under an hour.
We've used the same approach for genuine engineering work, not just templates — the pharma field-force position management module was built this way. The benefit is straightforward: significant time savings, lower cost to you, and faster iteration when requirements change.
What's in scope
- Scheduled jobs Cron-based actions for the work that needs to happen at fixed intervals — month-end, daily syncs, batch processes.
- Event-driven actions Server actions and automated rules triggered by record state changes.
- Approval workflows Multi-stage approvals with routing logic, escalation, audit trails.
- Document generation Auto-generated quotes, contracts, statements, branded outputs at the right moment.
- Document AI Invoice and PO extraction, contract parsing, structured data from unstructured documents.
- LLM-powered routing Customer messages, support tickets, leads — classified and routed by intent.
- Forecasting Demand forecasting, cash flow projection, when the data supports it.
- RPA bridges When the legacy system has no API and screen-scraping is the only path.
AI-built or hand-built, nothing reaches your production instance without human review on staging first. Speed never comes at the cost of an unreviewed change to a live ERP. AI is a means, not a feature.
Migration & deployment
From legacy ERP to live Odoo without losing history, breaking month-end, or surprising your team. The unglamorous work that determines whether a migration succeeds.
Our angle
Most migration failures aren't technical. They're about timing and trust. The new system is technically working. Nobody trusts it. People keep using the old one in parallel. Six months later you're paying for both systems and using neither well.
We migrate with parallel run as the default, not the upgrade. Go-live happens when both systems agree, not when the calendar says it's time. Hypercare runs through at least one full month-end. The old system gets retired only after the new one has been load-tested by reality.
What's in scope
- Source system extraction Sage 100/50/Intacct, NetSuite, QuickBooks, Excel-and-email — pulling data from wherever it lives.
- Data cleaning & mapping Master data hygiene, deduplication, mapping legacy structures to Odoo's data model.
- Historical data load Open transactions, customer/vendor history, inventory positions, GL balances — at the depth your business needs.
- Cutover planning Cutover weekend playbook, rollback plan, comms plan for users.
- Parallel run Both systems live, with daily reconciliation, until trust is established.
- Hypercare Embedded support through first month-end close, real-time issue resolution.
- Deployment Odoo.sh, Docker on AWS/Azure/GCP, on-premise — with Git-based CI/CD.
- Disaster recovery Backup schedules, restore drills, failover procedures.
The new system goes live when both systems agree on the same numbers — not when the project plan says it's time.
Wondering which of these your project actually needs?
The assessment maps your situation to the right mix of services — and tells you honestly which ones don't apply.