New: Your Basalt workspace for Odoo. MCP, proactive agents, visualisation. Learn more

Basalt
Menu

Language

MapLet’s understand your processDeployLet’s improve your processMeasureLet’s ensure team adoptionExpandLet’s save you more timeShow me the money.A clear price and scopeManufacturing & ProductionProduction, BOM, and Work Center TrackingWholesale & DistributionMulti-Warehouse Logistics, Supply Chain, and ShippingFood & BeverageBatch Lots, Traceability, and Expiration DatesRetail & E-commerceOmnichannel Sales, POS, and Storefront InventoryProfessional ServicesMilestone Projects, Timesheets, and Helpdesk TicketingConstruction & Field ServiceSubcontracting, On-Site Jobs, and Resource SchedulingPartnersOdoo integratorsLog in to your Basalt workspaceOpen your workspaceAboutWho builds BasaltCareersWhat we look forContactWrite or callCase studiesWork and resultsBlogNotes and guides

Industries

Manufacturing & Production

Half your enquiries look like something you have already built. Basalt finds the closest past job, prepares the parts list and the routing, and shows what the work really consumed once the order closes. Your engineers keep their time for the jobs that need them.

Where your team’s time goes

01 / 04

An engineer pricing a job that looks almost exactly like one you priced last year.

The comparable job exists, but finding its parts, routing and final outcome still pulls an experienced person away from new engineering work.

Where your team’s time goes

02 / 04

Working out what a job cost after it shipped, with the material, the scrap and the hours in three different places.

The margin becomes clear only after someone reconstructs the full production record, often too late to correct the next similar quote.

Where your team’s time goes

03 / 04

A component short on Monday, and no single list of the work orders competing for it.

Planners need the affected orders, promised dates and available alternatives together before they can make a useful trade-off.

Where your team’s time goes

04 / 04

Answering “can we take this on for March” by opening three screens and adding it up yourself.

Capacity decisions slow down when demand, material availability and work-centre load cannot be read in one prepared view.

Workflows

Quote from the closest job you have already built

  • The agent reads the enquiry, finds the jobs closest to it and prepares the parts list and the steps.
  • An engineer reviews the differences instead of rebuilding familiar work.
  • One manufacturer we spoke to takes 4,000 enquiries a year, about half of them straightforward, across 12 salespeople and 24 engineers.

See which jobs kept their margin

  • Odoo costs one work order at a time, on a page someone has to open.
  • The agent does it for every order that closed this month and puts the material, the scrap and the hours next to the quote.
  • You see the jobs that drifted, not only the few someone had time to check.

Prepare the trade-off when a component is short

  • The agent lists the work orders competing for the same component, with the customer order and the promised date behind each one, and proposes what to launch and what to move.
  • The shop floor decides, and the agent updates the dates.

On your shop floor

Do our bills of materials need to be perfectly clean?

No. We first measure the gaps affecting the selected workflow. Corrections are proposed with the manufacturing orders that support them, then approved by your team.

Does this work when every job is different?

Yes, when your history contains comparable work. The agent finds the closest cases and prepares a starting point. The engineer keeps decisions requiring technical judgement.

Can an agent promise a delivery date?

No. It assembles capacity, components, current work and existing commitments to prepare an answer. A person decides and confirms the date.

Odoo already calculates the real cost of an order. What is different?

That native calculation remains the source. Basalt can compare several orders, expose repeated gaps and prepare a revision decision rather than replacing the Odoo calculation.

Should we start in sales, inventory or production?

We start where time and uncertainty accumulate in your company. Map uses your volumes, data and baseline to make that choice.

Deployment and results

Does the whole process need to be in Odoo already?

No. Map also looks at spreadsheets, shared inboxes and tools around Odoo. The first workflow still needs a reliable source and a clear boundary.

How do you work with our integrator?

They remain responsible for the ERP. We document access, objects read or written and dependencies so everyone knows what belongs to Odoo and what belongs to Basalt.

How long does the first deployment take?

The scope aims for a first real use in the first month. Your team mainly explains the task, reviews exceptions and approves production.

Who keeps the final decision?

Your team does. Agents prepare, reconcile, flag and document. A person approves sensitive decisions and sends external communications.

How do you prove the workflow is useful?

We compare time, volume, exceptions and usage with the baseline written during Map. If the result is unclear, the workflow is not presented as a success.

Bring us one workflow that takes too much time.

In 30 minutes, we will see whether it is worth mapping.

Book 30 minutes
  • Start with a real task
  • Look at the modules involved
  • Identify the control points
  • Choose a clear next step