Hi, I'm
Subash Magar
Senior Odoo Consultant & Developer
Odoo consulting and development with SNM Digitech and Consulting. I shape Odoo around the way a business already works, build the modules and integrations the standard apps leave out, and hand over a system the team can run without me.
into systems that run
I build systems businesses actually run on.
I'm Subash Magar, a senior Odoo consultant and developer with SNM Digitech and Consulting. Most of my work sits close to day-to-day operations: sales, inventory, purchasing, accounting and the reporting people actually make decisions from.
Recent work has been in solar and energy-equipment distribution — inventory and pallet tracking, sales and CRM, US payroll, sales-tax reporting, and federal tax-credit compliance (FEOC and domestic content) built directly into Odoo 19 — alongside a stand-alone compliance platform that turns versioned, cited rule tables into deterministic determinations.
The standard I hold the work to is simple: a year from now, can your team change it without calling me?
What I build, and what changes.
A deliberately short list — the work I do often enough to do well, for businesses whose operations have outgrown the standard configuration.
Core expertise
What I deliver most oftenOdoo ERP implementation
Odoo configured against your real process, not a demo database. Sales, purchasing, inventory and accounting working off one set of records — with a written plan for moving the data you already have.
Custom module development
For the gaps standard Odoo leaves: new models, workflows, reports, portal pages. Written the way Odoo expects them, so the next version upgrade is an afternoon rather than a rewrite.
Integrations & automation
Banking, telephony, shipping and whatever else the business already pays for, wired into Odoo so nobody types the same record twice — plus the automations that remove the copy-paste in between.
Specialized services
Extended capabilities for specific needsCompliance & reporting
US tax-credit compliance (FEOC, domestic content), sales-tax reporting and payroll withholding, built into the workflow that creates the data — carrying the evidence trail a reviewer will ask for.
Web platforms alongside Odoo
Some workflows deserve their own product rather than a bent ERP. When that's the honest answer I build it beside Odoo — API-first, multi-tenant, with a mobile client — and keep the two in step.
Applied AI inside Odoo
AI only where it changes an outcome: an assistant grounded in your own records, document classification, first drafts. Where a feature can't beat the person already doing the job, I'll say so.
Ready to plan your next system?
Tell me what isn't working. I read every message myself, and usually reply within a day.
Compliance that shows its work.
A stand-alone platform built alongside Odoo for US solar projects: FEOC, domestic-content and tariff determinations computed from versioned, cited rule tables.
Deterministic determinations, with the evidence attached
Every threshold, rate and percentage is a cited rule-table row with an effective date; every determination is immutable, hashed and reproducible; every "not PFE" traces back to a screening or a certification on file.
Full-stack development
Both ends of the same platform
Odoo, rebuilt around the people using it.
The everyday screens reworked: a home that opens on what is late and what is pending, a menu each user shapes for themselves, and industry builds on top of the same core.
What I build with.
Chosen around the system being built and the people who will maintain it — not to fill a list.
Curated for stability and zero tech bloatERP & business systems
Daily, in productionApplication engineering
Web, API and mobileData & infrastructure
Where the data livesIntegration & AI
Getting it live, safelySystems built for real operations.
Odoo and platform work where the software had to solve an actual operational problem. Described by scope; client names on request.
Federal tax-credit compliance in Odoo
FEOC and domestic-content compliance module: vendor status, safe-harbor rate tables, project lines, thresholds and the reports a reviewer asks for — inside the ERP the purchasing team already uses.
Client: US solar equipment distributorSolar compliance platform
Multi-tenant platform for FEOC, domestic-content and tariff determinations — immutable records, evidence packs, a grounded AI assistant and a shared equipment library.
Own product · web + mobileInventory & logistics extensions
Pallet tracking, bulk stock updates, average stock-age reporting and a parcel-carrier integration, so the warehouse and sales see the same picture.
Client: US solar equipment distributorFinance, tax & payroll in Odoo
US federal income-tax withholding for payroll, a sales-tax report, partner tax exemptions and bank-feed synchronisation through Plaid.
Client: US solar equipment distributorSales, CRM & customer engagement
Sales-order customisations, SLA contracts, CRM usage analytics, engagement reporting, a geolocated contacts map, appointment booking and Twilio calling from the CRM.
Client: US solar equipment distributor · SNMAI assistants grounded in real data
An in-Odoo assistant over company records and a public site assistant with a project-brief mode — both answer from configured knowledge, never from guesswork.
SNM Digitech and ConsultingThree problems, and what changed.
Described by scope, client names withheld. The outcomes are stated plainly — no invented percentages.
Tax-credit compliance in the ERP
- Challenge
- Qualifying equipment for federal tax credits meant spreadsheets, vendor emails and rule tables nobody trusted to be current.
- Solution
- A module holding vendor FEOC status, safe-harbor rates, thresholds and project lines, with reviewer-ready reports — inside the purchasing workflow.
- Outcome
- One place to answer "does this project qualify?", with the evidence trail auditors ask for.
A compliance engine that shows its work
- Challenge
- Compliance answers that change when a rule changes, with no record of what was relied on at the time.
- Solution
- Versioned, cited rule tables; immutable, hashed determinations; a change feed that re-evaluates every project when a rule row is added.
- Outcome
- Same inputs always give the same answer — and last year's answer still points at exactly the text it relied on.
Warehouse, sales and finance on one Odoo
- Challenge
- Pallet-level stock, carrier shipping, US payroll and sales-tax reporting all lived in different tools and hands.
- Solution
- Targeted Odoo 19 extensions — pallet tracking, stock updates, carrier integration, payroll withholding, tax reports, CRM telephony — each written to survive upgrades.
- Outcome
- Warehouse, sales and finance read the same records; manual re-keying between tools is gone.
Clear scope. Visible progress. Fewer surprises.
Scope first, then milestones. Changes get written down before they hit the timeline.
Sprint by sprint, no black boxesUnderstand the problem
We start with the workflow, the constraints and what "done" looks like — before any talk of modules.
Design the approach
A written plan: what stays standard, what gets built, how data migrates, and the milestones. You approve it first.
Build in visible increments
Small, testable releases on a staging database with regular demos — progress every week, not a big reveal at the end.
Launch and hand over
Go-live, documentation and training, plus a support window so launch week stays calm and the team owns the system.
Trusted by teams that run on their systems.
Verbatim from Upwork, where every one of these is attached to a contract the client paid for. Client names stay private; the project and the rating are as Upwork shows them.
"10/10!"
"Working with Subash is great, will always recommend!"
"very good knowledge with quick turnaround. Will definitely recommend him"
"Excellent job!"
"Communicates well. Reverts back quickly. Flexible to accommodate changes to sow."
Open to selected Odoo projects and the right long-term role.
Odoo implementation, custom development and integration work where practical technical ownership matters — as a consultant, or in a senior role with a strong team. Remote-first; references on request.
Before we start.
Straight answers to the questions people usually ask first — or ask the assistant.
What kind of Odoo work do you take on?
Implementations, custom modules, integrations, data migration, reporting and workflows that need more than standard configuration. Most of my current work is on Odoo 19, Community and Enterprise.
Can you work with an existing Odoo setup?
Yes — a lot of work starts with a database and custom modules that already exist. I review what's there first and recommend the smallest sensible path forward rather than a rewrite.
Do you work outside Odoo?
When a workflow needs its own product, yes: API-first web platforms (FastAPI, Next.js) and mobile clients (Expo), usually alongside an Odoo system rather than instead of one.
How do projects usually start?
Send the problem, the outcome you want and anything you already have — process notes, a spreadsheet, an existing database. The AI brief on this page is a quick way to structure that; I still read every message myself.
How do you price work?
Hourly or by milestone, depending on how well-defined the scope is. Fixed scope gets a fixed quote; exploratory work is hourly with a written estimate up front.
Community or Enterprise?
Both. The choice depends on which apps you need and how you want to host; I'll say plainly which one fits before anything is bought.
Have a system to build or improve?
Tell me what you're working on, what's in the way, and what a good outcome looks like. Every brief reaches me directly, not a form queue.
Direct response, no middlemenTell me about the project
Fill this in and it opens as an email to me — or let the assistant draft a structured brief from a few sentences first.