My employees are struggling with filters. Can you write a detailed guide with examples of contains, is-in, equals, not-equals and child-of?
What happened: Wrote the filter training guide with worked examples drawn from their own database.
← All use cases
Documenting Odoo for your team
The gap between a configured Odoo and a team that uses it properly is documentation, and documentation is what gets cut when a go-live runs late.
So the knowledge stays with two or three people. New starters learn by asking them. Processes drift because nobody wrote down what the process was, and the workaround someone invented in month two becomes the official method by month six.
CodeCobra writes this material from your actual configuration rather than from generic Odoo documentation — so a guide describes your fields, your statuses, your approval steps, not the demo data. That's the difference between a document people use and one they skim once.
It also writes for the reader you name. "For warehouse staff who have never used an ERP" produces something meaningfully different from "for the finance team".
What people asked, and what came back
Real production requests, condensed and with anything identifying removed.
Make a guide with screenshots for building product sets, matching the style of our existing knowledge base.
What happened: Summarised the process for approval, wrote the guide in the house style, and published it to the staging and production knowledge bases.
Write non-technical user guides with screenshots for the picking and hold flows. Assume the reader is not technical at all.
What happened: Mirrored the client's installed apps onto its own instance so the screenshots match what staff actually see — then wrote the guides.
Draft the dispatcher scheduling SOP and responsibilities document.
What happened: Wrote the SOP covering the scheduling flow and who owns each step.
More requests in this category
- Write a one-page cheat sheet for drivers on validating deliveries in the app.
- Document our month-end close checklist as a knowledge-base article.
- Make a training guide for logging production and scrap on the shop floor.
- Write the returns-processing SOP with screenshots from our own database.
Does it describe our setup or generic Odoo?
Yours. It reads your configuration, so the guide names your actual fields and statuses. Generic Odoo documentation already exists and isn't what your team is stuck on.
What format do I get?
Word documents, PDFs or web pages, whichever suits. Word if it's going into your own template; a web page if it's going on an intranet.
Can it keep documentation current?
Ask it to update a document after you change the underlying process and it rewrites the affected sections. That's considerably cheaper than the annual rewrite that never quite happens.