Man measuring a wooden plank

Our approach to Odoo Standard

The comprehension of internal processes is the crucial factor in any implementation. This comprehension is based on three main motivations:

  • Stability

    To determine the right set-up to ensure stability as well as efficiency during productive operation.

  • Training

    The key to this is, of course, to take the system to the user, which can only be achieved through training. To be able to do this, however, one has to become acquainted with the customer’s internal application scenarios and their procedures.

  • Research

    To minimize risk, it is far better to do your research beforehand rather than start discussing things afterward.

To learn what questions to ask and discuss and to understand and classify the answers, it does not only take a corresponding investment in time and effort on the part of the customer. The implementers also need to have the appropriate expertise in each of the relevant areas, but a single person cannot provide this.

Quite often, and motivated by Point 3 above, the next threshold is the construction of a prototype to ensure that both sides share the same understanding of the request. Still, this also takes time and is not even done by a programmer (see also our Blog on Odoo Studio).

However, this only concerns the initial analysis, but I am sure that you can well imagine that this consultation is a standard feature throughout the entire project.

The list of items and reasons to justify this step is seemingly endless. But does a project have to run like this? Is it not possible to merely use Odoo in standard mode?

The answers are short and simple – „you don’t have to“ and „it is.”

However, what are the prerequisites, what are the requirements and what are the risks?