What you need to know about the Import / Export features in Odoo

I have to admit that I needed time to get used to working with these features, but it did not take as long as I expected. With a little knowledge of Excel and the Import/Export function, you can do pretty much anything. If you are still on the look-out for mass-update modules, you have obviously never worked with these features either, because, in combination with Excel, you have a real winning team!

Odoo is able to save a vast amount of data. Consequently, the field lists are incredibly long. Since none of the data are saved redundantly but are interlinked, a lot of information is distributed to sub-records. But there is almost unlimited access to both import and export – which does not shorten the field lists though.

But with a few little tips on handling (which we want to share in the course of this blog), the underbrush will clear up rapidly.

How could this happen? – A note on Accounting in Odoo 13

With Odoo 13, a lot has changed in the Invoicing and Finance modules. The most significant change probably is that Invoicing no longer exists as a single object. Until last October, with the release of version 13, the analog world acted as a template for the technical invoicing process. You generated an invoice, used „the next number“ on the list, put it on the document, sent it off, and forwarded it to the accounting department. The latter put a date of receipt stamp on it, allocated it to an account, added it to a batch, and finally posted it.

A short How-to regarding the change of value-added tax rates in Odoo

The VAT rate decrease has been announced. Currently, are probably a lot of newsletters and other information on how to implement this change in Odoo. First of all, however, we would like to point out that it is difficult, if not impossible, to find a “one size fits all” solution. After all, the type of adaption very much depends on the individual set up. Connections and links have to be considered, price calculation, and, of course, the effect on online shops or POS systems.

We are currently reviewing all our set-ups to discuss the ideal implementation and the necessary steps within the relevant parameters. This clearly shows that there is no such thing as THE standard solution or THE best way for this task. Nevertheless, we can distinguish two basic approaches to tackling this requirement that are feasible almost independently of the individual Odoo versions.

Odoo Installation / Re-installation – Part 2

Let’s move on to the next milestone during installation – the re-configuration of existing modules.

We will review the most important and most popular configuration options for each main module. This does not mean, however, that all other options are unimportant. But the number of configurations, meanings, and possible combinations is too comprehensive to discuss all of them without exceeding the scope of this blog.

Odoo Installation / Re-installation – Part 1

After quite a few theoretical articles, let’s talk about something more practical for a change. It is not that common that I am involved in a new installation myself unless it is a demo set-up. Usually, we take over an existing project, or one of our consultants or project managers will take responsibility for an installation, with me acting like some sort of “know-it-all” in the background.

Be that as it may, at the beginning of the year, it was time for me to get involved again. Here are my experiences and the key steps I can recommend.

Selecting your Software – What you should pay attention to

When you are faced with a choice of software solutions, you should know what precisely you are deciding on. In this blog, we would like to draw your attention to a few parameters that we think are important for such a decision.

In the following, we present comparisons mostly between SAP, Navision, and Odoo. Not just because customers usually include Odoo in their shortlists together with these respective vendors, but also because we are in a position to assess these products based on past migration assignments from these solutions to Odoo. And because they all have a very similar, i.e., integrated, international, and generalized approach. None of these systems focusses on a specific industry sector, area, country, or company size.

Odoo Migration

In this article, we will take a closer look at some of the questions from the previous blog. What exactly does migration entail, how often do you need to migrate, and what costs are involved in such a migration?

Our approach to Odoo Standard

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?

People first, machines second

It is hard to tell whether it is the fault of Odoo or the policy of the respective partner. Perhaps it is just one’s personal view on one’s own development or a reflection of what all the projects have in common when you take them over. Maybe it has to do with the fact that, when you receive them, some of the requests or specifications already contain precise functional descriptions. Or maybe it is only a question of a partner’s maturity once he gets involved.

We are quite familiar with this kind of approach from past experience. Quite often, decision-making bodies are present during the workshops, either discussing supposedly missing functions or planning processes and their optimization at the very beginning of an implementation. One of the reasons for these discussions is that the clients are familiar with the processes of the previous system that they regard as the “standard” and are now looking for a new and better “previous system” that covers the standard in the well-known way.[1] Consequently, they now face a situation where implementations, if successful, are more than a little bumpy, consume a lot of support for „remedies“ and, in retrospect, are very difficult to scale.

[1] In a previous blog, we have already discussed our views regarding the definition of the term „standard“, what it is and what it is not.

What makes IT tick – or an answer to the question of why less is more

The comparison may be valid or not, but it is a sad fact that people seem to compare Odoo and Microsoft Navision all the time. There is always at least one Navision partner in each bidding round of a tender.

In conversations, someone is bound to point out that „the other systems appear much more sophisticated when you look them in detail.” Much the same happens when we are processing or answering questionnaires or tenders that only inquire after a software’s features. Naturally, it is possible to replicate many of these functions, but they are simply not part of the Odoo Standard. The answer to the question of whether they are available, therefore, is a definite “no.”

Our recurring argument is that, in the long run, the software will be more cost-efficient and will offer more security since the Standard is the responsibility of the manufacturer. Thus, all risks of the implementation are already included in the license fee.