Every week someone sends me a link to a module on the Odoo Apps Store and asks whether it is safe to install. Increasingly the answer is no, and the reason is always the same.
An Odoo module used to take weeks. Now it takes an afternoon — describe the feature, accept the suggestions, wire up a manifest, and something installable exists by the evening. We use these tools every day and they are genuinely good. What is filling the store is what they produce when nobody owns the result.
They all read the same
This is the fastest tell, and checking it costs you nothing.
The assistants writing these listings draw on the same sources. Open five new modules from five unrelated vendors and you will find the same section headings, the same subtitle structure, the same confident cadence — seamlessly, fully configurable, out of the box. Different logos, one voice.
The code underneath tells the same story. A generated scaffold covers the happy path of a single model. It does not cover the workflow that model sits inside: the approvals, the accounting entries, the stock moves Odoo triggers three modules away. That part takes understanding the whole flow, and it is the part that is missing.
The failure is not a bug — it is your workflow
A badly built module rarely announces itself. It installs, it looks right, and then it quietly posts to the wrong journal, or skips a validation, or breaks a native flow you were relying on. By the time anyone notices, it is in your data.
The bill arrives on a schedule:
- The first version bump. Generated against 17.0, never re-tested, meets 18.0's ORM changes head-on.
- The first real dataset. Demo data hides everything. Ten thousand products and three companies do not.
- The first support ticket. Ask why something behaves the way it does and you get a new zip file instead of an answer. That is re-prompting, not support.
Nobody can tell you who is trustworthy
The Apps Store has no reviews. No rating, no deployment count, no way to separate a vendor running twenty live databases from a website built as a side project last month.
That gap is the business model. Publish twenty thin modules, price them like engineered ones, and let volume do the work.
Until the store closes that gap, the checking is on you. Before paying for any module — ours included — ask for four things:
- A live demo on your kind of data. Not screenshots. If they will not walk you through it running, treat the listing as fiction.
- Deployment evidence. How many live databases run this today, and who verifies it after each Odoo release?
- The upgrade story. Which versions are covered, what happened at the last major release, and what an upgrade costs you.
- Support terms in writing. Who answers, how fast, and what is included.
A vendor who understands their own module answers all four in one call. A vendor who does not will send you a feature list.
Where we stand
We are engineers first. AI sits inside our workflow as an accelerant, not as the engine — a person designs, reviews and owns every line that ships.
Every module we publish runs in live production databases across hospitals, IT services, real estate, food and beverage, and sales organisations. They are signed off by the directors and C-level managers who own those processes and know what a correct number looks like. Dashboards and reports are checked against real figures before release, licences include two free update requests, and you can ask for a live demo before paying anything.
The tools are not the problem. Shipping what you do not understand, and pricing it as though you do, is.