Can we make the delivery address on a sales order copyable to the clipboard, so I can paste it elsewhere?
What happened: Added copy-to-clipboard on the address — then, on request, made the copied text link back to the sales order.
← All use cases
Changing an Odoo screen or business rule
Most Odoo frustration isn't dramatic. It's the field that should be mandatory and isn't. The warning that fires on the wrong condition. The button in a place that made sense to whoever configured it and to nobody since.
Each one is small enough that raising it feels disproportionate, so teams build a workaround and the workaround becomes the process. Then a new starter learns the workaround instead of the system.
These are the cheapest and fastest things CodeCobra does. Describe what you want the screen to do — not which model or view it lives in — and you get a plan back in business terms, then a pull request.
It's worth clearing a backlog of them in one sitting. Individually none is worth a project; together they are usually where the daily friction actually lives.
What people asked, and what came back
Real production requests, condensed and with anything identifying removed.
On the delivery checkout page, we need to let the customer enter a PO number and pick a ship date.
What happened: Built both fields into checkout, fixed the confirmation page, added a guard test, and pushed it all as a pull request.
Could I add a case weight, cube size and UPC to each item?
What happened: Added the fields — then built a paste-ready spec sheet with a copy-ready line for all 13 finished goods.
Can inventory show a pallet column too, so I don't have to convert cases to pallets by hand?
What happened: Added pallet quantity to the inventory view, computed from case quantities.
Can you make me a shared saved list of transfers that are ready to validate but missing landed costs?
What happened: Built the saved filter and shared it across the team rather than as a personal view.
Can the “New” tag filter default to open on the website?
What happened: Shipped it — plus alphabetical sorting on the category filter in the same pass.
More requests in this category
- Require a manager approval on credit notes over $500.
- Block new sales orders for customers more than 30 days past due, with a manager override.
- Add a QC checkbox on the work order that must be ticked before it can close.
- Let me set a seasonal reorder point per product without touching the regular one.
- Print the customer's PO number on every delivery slip and invoice.
- Warn the salesperson if they quote below the minimum margin on any line.
- Make the landed-cost field mandatory before a receipt can be validated.
- Sort the website category filter alphabetically and have it default open.
Is this different from Odoo Studio?
Studio covers a lot of this well, and if Studio can do what you need, use it. CodeCobra writes actual modules, so it also handles the cases Studio can't reach — conditional logic, rules that depend on data elsewhere, anything needing Python.
Will my change survive an Odoo upgrade?
Changes are written as proper Odoo modules in your own repository, which is what makes them portable across versions. Ask it to check a module against a newer version before you upgrade.
Can I batch several small changes together?
Yes, and it's usually the efficient way to do it. List them in one conversation; you get one plan covering all of them and one pull request to review.