We do not implement everything. We implement the apps that manufacturers and wholesalers depend on, and we know where each one bends and where it breaks.
Quotes, pipeline and pricing in one place.
Quotations that take their prices from one price list instead of from the last version of a spreadsheet, and a pipeline that a sales manager can read on a Monday morning without asking anybody.
For a manufacturer the useful part is the quotation itself: optional lines, margin visible while you type, and a confirmed quote that becomes a works order without being typed again.
Stock you can trust, reorders that run themselves.
One stock figure per article per location, counted in cycles rather than once a year in a panic, and replenishment rules that raise the purchase orders instead of a planner remembering to.
Most of the work in this app is in the first three weeks: article numbers, units of measure, lead times and minimum quantities. Get those right and the rest of the implementation runs on rails.
BoMs, routings and planning on the shop floor.
Bills of material and routings that match how the hall actually works, work orders on a tablet at the work centre, and a quality check that is part of the operation rather than a form somebody fills in afterwards.
This is the app where a bad implementation is most visible, because the floor stops using it within a fortnight. We spend the blueprint phase standing next to the machines.
Invoicing, bank sync and VAT for the Netherlands and Belgium.
The Dutch and Belgian charts of accounts, bank statements read automatically, and a VAT return that comes out of the system rather than out of a workbook on somebody's desktop.
We implement with your accountant in the room, because the one thing that cannot be fixed after go-live is an opening balance that nobody agreed.
A B2B portal and webshop on the same stock.
A customer portal where trade customers see their own prices, their own order history and the stock that is really there, and a public webshop on the same catalogue when that is wanted.
The point of putting it in Odoo is that it is not a second system: an order from the portal is the same sales order as one typed at the desk.
Tickets and service visits tied to the customer record.
A ticket that knows which machine it is about and which order it came from, and a planned visit with the parts, the hours and the travel on it when the engineer closes the job.
For a manufacturer with an installed base this is usually the second phase, once the order to cash chain is steady.
Each one is quoted as part of a phase, not as a project of its own.
Orders and despatch advices in the formats the large retailers send.
Labels at the pack bench and a tracking link on the customer's order.
Statement import, payment files and matching that does not need a human.
Articles, customers, open orders and balances, migrated with a dry run first.
That is what the quick scan answers, in writing, in a week.
Brightmoor is a fictional company created for demonstration purposes. The implementation figures, delivery times and service claims on this website are illustrative.