Skip to Content
Q&A

The customisation register: per customer, which custom work is running and which tickets it belongs to

How we keep track of what was built for each customer, without relying on anyone's memory

Back to all Q&A
November 4, 2026 by
The customisation register: per customer, which custom work is running and which tickets it belongs to

In short: What was built for a customer should not live only in a code repository and in someone's head. We built a register that shows per customer which custom work is running, what it does, which fields it adds, where the code is and which tickets it belongs to. The register fills itself by reading the customer's environments. This article describes how we work and is not a product offer.

An employee with a tablet stands at a large cabinet of drawers, with lines connecting the drawers to small buildings and tickets

Anyone who works on Odoo for several customers knows the question. A ticket comes in and you want to know straight away what is different at this customer. Which modules are installed that do not come from Odoo itself? Does this one run on production, or only on staging? And did we discuss it in an earlier ticket? We wanted that answer in one place, so we built it as a module in our own Odoo.

What the register records per customer

Every installed module that does not come from Odoo itself gets its own entry for that customer:

  • What is running: name, author, version and the description from the module. The origin is DAADit, Connecta or a third party.
  • Where: on which of the customer's environments it is installed, such as production, staging or development.
  • What it adds: the fields the module creates or changes, per model, with label and type.
  • Where the code is: the repository, the branch and a direct link to the folder.
  • Which tickets and tasks: tickets and tasks of the customer in which the module was mentioned. You can add to these by hand.
  • What it does: a functional description in plain language.

A register that fills itself

A register you have to keep up by hand tends to go out of date. That is why ours reads the customer's environments itself, every night and also when someone presses the button on the customer.

This has clear limits. It only reads, and only metadata: modules and fields. It uses the same boundaries as any other agent call. A separate check on GitHub determines in which repository the module is located.

The register also keeps track of when a module was first and last seen. A module that can no longer be found is not simply deleted from the list, but gets the status that it was no longer found.

A functional description from the code

A technical module name says little to someone answering a ticket. The functional description therefore explains what the custom work does for the customer: which process, which screen and which settings.

To write it, the system reads the module's code on GitHub: the manifest, the readme, the models, the screens, the wizards and the data. When the code changes, the description is updated.

People stay in charge of the text. If someone adjusts a description, that text stays, and the register shows whether a description came from the code or from a person. It also records when the description was last updated and the last error when reading failed.

How the helpdesk uses it

The register is visible in the helpdesk, and our helpdesk agent uses it as well. With a ticket, the agent immediately sees which custom work is running at that customer, with the functional description and the fields, without having to look it up. How that agent works is described in our article on helpdesk with AI.

One link is not there yet. Connecting custom work to the customer's process steps, so that research can start from the process, is not part of this version.

What this means for you

Do you have custom work in your Odoo? Then you can start on a small scale, also without a module like this:

  1. List every installed module that does not come from Odoo itself, per environment.
  2. Record for each one who made it, which version it is and where the code is.
  3. Describe in plain language what it does and who uses it. If nobody can explain that, that is worth knowing too.
  4. Note which fields it adds, so that you can recognise them in screens and reports.
  5. Link tickets to the module whenever it comes up, so that the history stays findable.

Two pitfalls are worth avoiding. A list that depends on someone remembering to update it will fall behind, so make updating it part of a fixed routine. And a description written only for developers does not help the person who answers the customer.

An overview like this also helps when you plan an upgrade, because you can see what has to be checked. Our upgrade checklist covers the rest of that preparation.

This article says nothing about price, delivery time or availability. Whether something like this suits your situation is something we discuss in a conversation.

Frequently asked questions

How does a customisation register stay up to date?

Our register reads the customer's environments every night, and this can also be done with a button on the customer. It only reads, and only metadata: modules and fields.

Who writes the functional description?

The system reads the module's code and writes the description in plain language. When the code changes, the description is updated. If a person adjusts the text, that text stays.

How does the register know which tickets custom work belongs to?

It links tickets and tasks of the customer in which the module was mentioned. You can add to that link by hand.

Finally

Custom work is only manageable if you can see what is running, where it is running and why it was built. That is what this register is for. Want to discuss how to get a grip on the custom work in your Odoo? Contact us for a conversation. Prefer to look at your own processes first? Take the free Business Scan.

in Odoo

Question not answered?

Our Odoo consultants are happy to think along with you. Book a no-obligation intro call.

Book an appointment
Why Odoo emails do not arrive: SPF, DKIM, DMARC and where to look
A step-by-step way to find out whether the problem lies in Odoo, in your domain settings or at your mail provider