Most manufacturing and trading businesses in Gujarat start the same way — a few Excel sheets for stock, a Tally file for accounts, and a WhatsApp group where someone shouts "bhai, stock check karo" before every big order. It works fine until the company crosses a certain size. Then purchase orders go missing between departments, two people quote different prices to the same customer, and the owner finds out about a stockout only after a client calls to complain. That gap — between what spreadsheets can hold and what a growing business actually needs to run smoothly — is exactly where Odoo ERP implementation and customization earns its keep, and it's the reason we're opening this position in Vadodara.
Why Vadodara, and why now
Vadodara has a dense cluster of mid-sized manufacturing units, chemical traders, engineering workshops, and packaging companies, many of them in and around the GIDC belts and the Alkapuri-Fatehgunj commercial corridor. A good number of these businesses have outgrown basic accounting software and are now asking for proper inventory management, multi-location stock tracking, automated invoicing, and reports their finance team doesn't have to rebuild by hand every month. Devmixa is a small web design and digital marketing team based in Bhopal, and over the last year we've picked up several Odoo projects from clients in this part of Gujarat — a plastics trading firm, a textile accessories manufacturer, and a logistics coordination office among them. Rather than handle all of it remotely, we're setting up a small on-ground presence in Alkapuri, Vadodara, and this hire is the first developer on that team.
If you search for an Odoo ERP Developer job in Alkapuri Vadodara, you'll notice there aren't that many agencies hiring locally for this specific stack — most of the demand is either freelance or tied to large Odoo partner firms. We're a smaller setup, which means you'll get hands-on exposure across the full implementation cycle instead of being boxed into one narrow task.
What the work actually looks like
This isn't a role where you sit and write generic code all day. A typical week might involve configuring a new inventory module for a client who just added a second warehouse, writing a QWeb report template because their old invoice format doesn't match what their accountant wants, or fixing a workflow where sales orders aren't triggering delivery notes correctly. Some days you'll be deep in Python backend logic; other days you'll be adjusting XML views so a form looks the way the client described over a phone call that didn't quite match what they meant.
- Setting up and configuring Odoo modules — Sales, Inventory, Accounting, Purchase — based on what each client's existing process actually needs, not a generic template
- Writing custom Python code to extend standard Odoo models when the out-of-the-box behaviour doesn't fit a client's workflow
- Building and modifying QWeb report templates — invoices, delivery challans, purchase orders — to match the formats clients are used to
- Working with PostgreSQL to troubleshoot data issues, write queries for reports, and occasionally clean up messy historical data during migrations
- Editing XML views and form layouts so screens match how the client's team actually works day to day
- Coordinating directly with client teams in Vadodara during go-live weeks, sometimes on-site, to handle user training and bug fixes as they come up
- Supporting business automation requests — automated email alerts, approval chains, recurring tasks — once the core modules are stable
Who we're looking for
We're hiring across two experience bands for this opening, and honestly the fresher band matters just as much to us as the experienced one. If you've just finished a degree and picked up Python and some Odoo exposure through a course or a college project, you are exactly who this listing is written for — we expect to train you properly in your first few months rather than throw you at a live client on day one. For someone with 2-4 years already doing module customization or working as a functional consultant on Odoo projects, you'll be handed more complex client work faster and will likely end up mentoring the newer hires within a few months.
Skills we actually care about, roughly in order:
- Working knowledge of Python, enough to read and extend existing code without breaking unrelated features
- Familiarity with Odoo's module structure — models, views, controllers — even if it's only from self-study or a short course
- Basic SQL and comfort with PostgreSQL, since a lot of debugging in this role comes down to looking directly at the database
- Some exposure to XML, since views and reports in Odoo are built on it
- Willingness to sit with a client, understand what they're actually trying to achieve, and translate that into a working configuration — this matters more than people expect
- Basic understanding of how a trading or manufacturing business runs — purchase, stock, sales, accounts — because the software is only useful if it maps to a real process
You don't need a polished portfolio of enterprise implementation projects. A few personal projects, a course certificate, or even a confident walkthrough of how Odoo's module system works during the interview is enough to get you considered.
Pay, growth, and what the first year looks like
Starting salary for freshers on this role is ₹18,000 to ₹25,000 per month, depending on how much you already know versus how much training you'll need. That's deliberately set as a real, livable number for Vadodara rather than a token stipend — we've seen enough "fresher" postings elsewhere that pay next to nothing and don't want to be one of them. Once you've built two or three implementations end to end and can handle a client conversation without a senior hovering nearby, the role moves into the ₹35,000 to ₹58,000 per month band (roughly ₹3.5 to 7 LPA), which is where our 2-4 year hires currently sit. Growth here is tied to what you can independently deliver, not just time served, so a sharp fresher can move through that range faster than the "2-4 years" label suggests.
Beyond the number on the offer letter, you get something that's harder to put a price on in this specific field: breadth. Working across Sales, Inventory, Accounting and reporting modules for different client industries in your first year teaches you more about how ERP software actually gets used than staying inside one large company's single Odoo instance for the same stretch of time.
Where this sits, and how we work
The role is based out of our Alkapuri office in Vadodara, Gujarat — 390007 — and is on-site, full-time. We're not set up for remote hiring on this particular position yet, partly because client visits and in-person training sessions are a real part of the job in the early months. The team is small enough that you'll know everyone by name within your first week, and decisions about how a client's module gets configured usually happen in a five-minute conversation rather than a formal review cycle. If you've worked at a bigger IT company before and found the process overhead frustrating, you'll probably find this a welcome change — though it also means more is expected of you in terms of taking ownership.
We interview on a rolling basis rather than batching candidates, so if your profile fits, you can expect to hear back within a few working days rather than waiting weeks. Shortlisted candidates are usually called in for a short walk-in round at the Alkapuri office followed by a practical discussion — nothing elaborate, just enough to understand how you think through a configuration problem and how you'd explain a technical fix to someone non-technical.
A quick note on where this role can take you
Odoo as a platform keeps adding modules and keeps getting adopted by more small and mid-sized businesses across India, which is a decent long-term signal if you're weighing this against, say, a generic full-stack developer path. The ceiling here isn't just "senior developer" — plenty of people who start in module customization move into functional consulting, project implementation leadership, or even freelance consulting for multiple clients once they've built up enough real-world project experience. None of that happens overnight, but the first step is the same for almost everyone: get properly good at one ERP system by actually implementing it for real businesses, under people who'll correct your mistakes early rather than let them become the client's problem.
If that sounds like the kind of work you want your next year to look like, we'd like to hear from you.