REAV

Foundation

Odoo as a foundation,
not as the answer.

The REAV ERP is built on Odoo open-source code. That is a deliberate choice about robustness and scalability, and it is worth being precise about what the foundation gives you and what refurbishment still requires on top of it.

Book a demo See the full ERP

What the foundation gives you

A serious business layer, already solved.

Odoo is an open-source suite of business applications, with a Community edition published under LGPLv3. Building on it means a whole category of work is already done.

The standard modules stay within reach

Purchasing, HR, e-commerce, website and accounting are there, and they are the same modules the rest of the market uses.

Open-source code, not a black box

The foundation can be read, extended and hosted on your terms rather than only consumed as a service.

A known ecosystem

Hosting, integrators and documentation exist independently of REAV, which matters for anything you intend to run for a decade.

Where standard modules stop

Refurbishment runs the flow backwards.

A factory consumes known parts to produce known products. A repair operation receives unknown items, discovers what they are, and produces a mix of resold devices, harvested parts and waste streams. Four consequences follow, and they are why a business layer had to be built.

  1. 01

    Stock is serialised and unique, not fungible

    Standard inventory is comfortable with forty identical units. Refurbishment needs one record per device, because each one has a different history and a different grade.

  2. 02

    Incoming condition is unknown at intake

    Purchasing assumes you know what you ordered. A pallet of returns has to be received first and characterised afterwards, which inverts the usual sequence.

  3. 03

    Dismantling produces stock that was never purchased

    A harvested part enters inventory with no purchase price and a provenance worth keeping. A forward-only bill of materials has no natural place for it.

  4. 04

    Erasure, grading and certificates are not standard objects

    A device record has to carry an erasure certificate, a grade and a repair history, and none of those exist in a generic business suite.

What this is not

The boundaries, stated plainly.

  • The product is the REAV ERP. Odoo is the code base it is built on, not what is being sold to you.
  • This page does not claim standard Odoo cannot run a refurbishment operation. It sets out what a business layer has to add before it can, and REAV built that layer rather than finding it.
  • REAV does not publish Odoo and does not speak for it. Licence terms and editions are Odoo’s.

FAQ

Common questions.

It is built on Odoo open-source code, with a business layer built for refurbishment on top: intake by lot, erasure and audit, repair, dismantling, sales, logistics and after-sales.
Yes. Purchasing, HR, e-commerce and website stay within reach alongside the refurbishment layer.
No. REAV deploys, connects and trains. Whether you later want your own team on the foundation is your decision, and the open-source base is what keeps it open.
Because an operation needs both halves. The refurbishment layer is what no generic suite provides; purchasing, accounting and e-commerce are what no niche tool wants to rebuild.

Related terms

← Back to the REAV ERP

See the business layer, not the foundation.

The interesting part is what sits on top. Tell us about your volumes and device mix, and we will walk one device through the full lifecycle on the REAV ERP.

Book a demo Contact us