I'd like a dispatch board where we can drag loads into rounds, and that assigns the truck.
What happened: Built a drag-and-drop dispatch board as a real Odoo module — with browser tours running in CI so a regression can never silently ship.
← All use cases
Building a custom Odoo module
Sometimes there is no setting. The process your business runs on doesn't map to anything Odoo ships, and configuring around it produces something worse than the spreadsheet it replaced.
A custom module is the honest answer, and it's the thing people avoid because of what it traditionally costs: a scoping call, a quote, a wait, then a build against a specification written weeks earlier by someone who has since misremembered the detail.
CodeCobra collapses that. You describe the process; it writes a plan in business terms — what it will change, where you'll see it in Odoo, what happens to existing records — and you correct the plan until it's right. Approving the plan is the commitment, and it takes minutes rather than weeks.
What gets built is a proper Odoo module: models, views, access rules, tests, in your own repository. Not a configuration nobody can maintain.
What people asked, and what came back
Real production requests, condensed and with anything identifying removed.
Build an online credit application with a signing workflow.
What happened: Built the application form and the sign-off flow end to end.
If a customer hasn't ordered in X days, email them or create an activity. If they order double their usual average, flag a rep.
What happened: Built the rules engine — and explained up front which of the two rules Odoo's plain filters genuinely cannot express, and why.
We buy in EUR from some vendors. The PO needs to show EUR, the receipt must record cost correctly, and the bill gets exchanged at payment time.
What happened: Designed the multi-currency flow — then wrote out the fully manual native-Odoo version too, so the team had something to run the same day.
Rebuild our old webshop's search suggestions in the new theme, matching the original design.
What happened: Rebuilt it — along with the mini-cart, cart page and responsive shop grid. A whole storefront carried forward six versions.
More requests in this category
- Build a driver check-in screen for the loading dock with signature capture.
- Create a production schedule board we can drag orders around on.
- Build a portal page where customers can reorder from past orders in one click.
- Auto-create a quality alert when a lot fails inspection twice.
- Add a capacity check that stops overbooking a venue across overlapping orders.
How detailed does my description need to be?
Start with the outcome and the pain. "Our returns process has three approval steps and Odoo only models one" is a better opening than a field list. It asks about the gaps, and the plan is where the detail gets settled.
Who owns the module?
You do. It lands in your own GitHub repository and you can download it as a ZIP at any time. There's nothing to extract if you stop using CodeCobra.
Does it write tests?
Yes, and it runs them. A module arrives with tests and a passing CI run, which is what makes the next change to it safe.