The problem: A client needed extra questions only when the order was delayed
Imagine you manage quality at your company's shipments. You use Odoo and have a defined process with quality worksheets that trigger when an order is delivered. Everything works well, until a client tells you: "I need that, if the order arrives late, the quality form includes additional questions to document the reason." You don't want to complicate things with external development or hire programmers. You want an agile solution, native to Odoo, and ideally supported by artificial intelligence to speed up the work. That is exactly what we are going to solve here.
The solution: Quality worksheets as a data model
Quality worksheets are special because, unlike other types of control (such as "pass/fail" or "spreadsheet"), they create a new model in Odoo. That is, a table in the database with all the fields you define. This lets you access analysis, pivot tables, and even use them as a source for Business Intelligence. The downside? They are not as visually flexible as a spreadsheet. But for cases where you need relationships and automatic calculations, they are ideal.
Real story: At Ganemo, a client in the logistics sector asked us for exactly this. They had a standard quality checkpoint when delivering goods. But if the order arrived after the scheduled date, they needed to capture the reason for the delay. Using quality worksheets, we defined a new model. Then, with artificial intelligence (specifically Claude Opus), we generated the Python code for a computed field that automatically detected whether the shipping date was later than the planned one. The functional consultant, without being a developer, was able to do it by following a clear process supported by AI. And if you have questions, at Ganemo we guide your team step by step.
Step 1: Identify the relationships between models
Before touching any code, you must understand how the data is related in Odoo. In our case, the quality worksheet is linked to a "quality check", and this check has a field that points to the "picking" (the inventory transfer). That is the path: worksheet > quality check > picking. Without this clarity, not even AI will save you from making mistakes.
Real story: In the client's project, the functional consultant (let's call him Carlos) spent 30 minutes reviewing the models from developer mode. He identified that the "quality.worksheet" model had no direct field to "stock.picking", but it did have one to "quality.check", and that one had the "picking_id" field. That information was key to asking the AI for the correct code. "Without that understanding, AI may suggest relationships that don't exist," comments Carlos. "At Ganemo, from day one we teach you to read the data model, because it is fundamental."
Step 2: Clearly define what you want to automate
Once you understand the relationships, you must specify the business rule. In our example: we want a boolean field called "X_retraso" to be automatically checked if the shipping date (field "X_date") is later than the scheduled date of the picking (field "scheduled_date" of the picking). And then, when "X_retraso" is true, we want a selection field "motivo_retraso" to appear so the cause can be chosen.
Real story: The client had doubts about which field to use to determine the delay. It could be the picking's validation date, or a manual date on the form. They decided to use the manual date "X_date" because it represents the actual moment of the check. "This decision was made by the functional consultant based on his knowledge of the process, not by the AI," Carlos clarifies. "At Ganemo, we encourage you to make those decisions with judgment; AI only speeds up the implementation."
Step 3: Use artificial intelligence to generate the code
With the relationships clear and the rule defined, you can ask the AI to generate the Python code for the computed field. In the video, the presenter used Claude Opus and passed it screenshots of the model and fields, along with a textual description. The AI returned the code and the dependencies. Then he himself validated that the code was logical, asked about possible errors (such as different date types), and adjusted the dependencies to only "X_date" to avoid unwanted recalculations.
Real story: The code the AI generated included type conversion: "scheduled_date" was datetime and "X_date" was date, so it used .date() to compare them. The consultant, without being a programmer, asked: "What happens if any field is blank?" The AI replied that the code handled that case with conditions. "That interaction is key," says Carlos. "It's not blindly copying and pasting; it's understanding the basics so you can trust the result." He then pasted the code into Odoo Studio, in the field's "compute" tab, and added the dependencies. In total, it took him 4 hours the first time; an expert at Ganemo does it in 5 minutes.
Step 4: Implement the conditional visibility of the extra field
Once the boolean field is calculated automatically, the "motivo_retraso" field must be visible only when it is true. In Odoo Studio, this is achieved with an invisibility condition: invisible if the "X_retraso" field is not checked. Simple and powerful.
Real story: The client tested the form in a test environment. First, without a delay: the reason field did not appear. Then, when entering a date later than the scheduled one, the boolean field was checked automatically and the dropdown appeared with options such as "Lack of stock" or "Pending confirmation". The end user was satisfied. "And all without touching any code beyond the pasting," celebrates Carlos. "Ganemo delivers the documentation of every customization so your internal team can maintain it."
Step 5: Leverage the data with analytics and BI
The best part of using worksheets: you now have a table with historical quality data. You can create pivot tables grouping by delay reason and count frequencies. You can even connect Power BI or Tableau directly to PostgreSQL for advanced reports. This turns a simple form into a business intelligence source.
Real story: After implementing this, the client started generating weekly reports of delay reasons. They detected that 70% were due to lack of stock, which led them to adjust their inventory policy. "We wouldn't have obtained that value with a static spreadsheet," states Carlos. "With Ganemo, we implement solutions that generate actionable data."
Conclusion: AI is a tool, not a replacement
This case shows how artificial intelligence can speed up customizations in Odoo when you have the fundamentals clear: model relationships, business logic, and functional judgment. You don't need to be a developer to achieve it, but you do need to understand what to ask and how to validate. At Ganemo, we train functional consultants with that capability, even if they start from scratch. If your company is looking to implement Odoo with efficient, documented customizations, we are the right partner.
Ready to optimize your quality processes with Odoo, hassle-free? Contact us and find out how we can help you.