PRODUCT · BUILT ON ODOO

ERP Enterprise Resource Planning

Sales, stock, purchasing, production and accounting in one database. A number that changes in one place changes everywhere.

The point of an ERP is to stop you entering the same information twice. An order deducts stock, a product hitting its reorder point raises a purchase request, and a goods receipt matches against the invoice. Odoo does this on a single database, so there are no separate programs to bridge.

What it solves

These three come up more than anything else in a first conversation.

“The screen says one thing, the warehouse another”

Every movement is tied to a document: receipt, delivery, transfer, count adjustment. When the number is off, you can see where the chain broke.

“Nobody knows what actually makes money”

Product cost includes the purchase price, freight and customs. Margin is reported per product and per customer.

“Departments wait on each other”

Sales sees stock and the delivery date while entering the order, so nobody has to phone the warehouse.

How data moves through the company

  1. 01

    Sales

    • Quotes and orders
    • Price lists
    • Customer ledger
  2. 02

    Inventory

    • Multiple warehouses
    • Lot and serial numbers
    • Reorder alerts
  3. 03

    Supply

    • Purchase requests
    • Vendor comparison
    • Goods receipt
  4. 04

    Accounting

    • Invoice matching
    • Bank reconciliation
    • Profit and loss

Odoo modules involved

These are Odoo’s own modules. We write whatever is missing, rather than building a program from scratch.

Inventory

Multiple warehouses, bin locations, barcode counts, lot and serial tracking.

Accounting

Ledgers, bank reconciliation, multi-currency, period reports.

Purchase

Vendor price lists, automatic reordering, receipt control.

Manufacturing

Bills of material, work orders, routings and work centres, production cost.

Project

Task lists, timesheets, income and cost tracked per project.

Quality

Incoming and in-process control points, measurement logs, non-conformity tracking.

Getting it running

01

We watch the process on site

We spend a day each in the warehouse, in sales and in accounting. The process people describe is rarely the process that runs.

02

We clean the master data

This is the longest part of the migration. Duplicate product cards, dead stock and unclosed accounts all get sorted out by hand.

03

We run in parallel

For a month the old system and Odoo run side by side. The old one is not switched off until the numbers agree.

04

We hand over without walking away

Someone inside the company is trained as system owner. Maintenance and version upgrades stay with us.

Connects to

  • Bank statement files
  • Barcode terminals
  • Online store
  • Shipping carriers
  • Supplier price lists
  • Excel import / export

Why Odoo

One database

The modules are different screens onto the same data. No bridges to build, no data to shuttle between them.

Grows a piece at a time

Start with one module and switch on another six months later. Nothing is rebuilt, the data stays where it is.

The data stays yours

Your own server or the cloud, it makes no difference: you can export the entire database whenever you want.

Frequently asked

Community or Enterprise?

We look at your business and tell you. Community costs no licence fee, but accounting automation, production scheduling and the mobile app stay on the Enterprise side. Manufacturers usually need Enterprise, while straightforward trading runs fine on Community.

Can data come from our current software?

Yes. We import from any system we can get an Excel or database dump out of: products, accounts, open balances and stock counts. Historical transactions usually stay in the old system as an archive.

What if the internet goes down?

If the server is in your office, work continues over the local network. On the cloud, access stops, so for manufacturers who cannot take that risk we put the server on site.

Can modules be added later?

That is precisely why we use Odoo. Start with inventory, switch on manufacturing six months later and maintenance after a year. The data stays where it is and nothing is rebuilt.

Half an hour is enough to know whether it fits.

How many of you there are, what you track today and how. We talk it through and give you a straight answer. If it does not fit, we say so.

Other products

Let the next project be yours.

Tell us what you have in mind; within two working days we come back with scope, timeline and a budget.

[email protected]

Start a project

Tell us briefly; within two working days we come back with scope, timeline and a budget.

Step 1 / 4

How should we proceed?

Both reach the same team; the detailed one lets us quote more accurately.

What do you want to build?

You can pick more than one.

Pick at least one.

Your budget range?

Not sure? That's fine, we work it out together.

Current state and deadline

Where do we start, and by when does it need to be ready?

What do you have right now?
Deadline

Tell us briefly

What do you want to build, and who for? Add any examples you like.

How should we get back to you?

We write within two working days.

Your request reached us

Our team is reviewing it; we reply by email within two working days.

Request no: