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

Wholesale & Distribution

Your margin moves in small steps across a large catalogue. Basalt matches supplier references to yours, turns a customer order sent as a PDF into clean lines, and flags a buy price that has drifted before anyone confirms it. Buyers spend the week acting on the data instead of repairing it.

Where your team’s time goes

01 / 04

The same steel bar is 4471-B at one supplier and BR-4471 at another, so every price update starts with a matching job.

Supplier language has to be reconciled with your catalogue before a buyer can even assess what changed.

Where your team’s time goes

02 / 04

A customer sends an order as a PDF and someone retypes it, from their names into yours.

Each line needs a product, unit and warehouse match, turning a routine order into careful manual entry.

Where your team’s time goes

03 / 04

A buy price goes up on a confirmation and nobody notices until the margin report.

A small increase can pass unnoticed across a large catalogue and erode margin before the monthly review exposes it.

Where your team’s time goes

04 / 04

Reorder levels set at go-live that nobody has looked at since.

Demand and supplier lead times move, while old settings keep generating decisions from a picture that is no longer current.

Workflows

Turn a customer PDF into a draft order

  • The agent reads the attachment, identifies the customer and matches each line to your catalogue using what that customer has ordered before, including their own codes and units.
  • Uncertain lines wait for a person.
  • Manual order entry can take a day and a half each week.

Catch a supplier price before you confirm it

  • The agent compares each line with the price you last paid and the twelve months behind it, and warns the buyer before confirmation.
  • Each month it groups the increases by supplier, with volumes, ready for the negotiation.

Bring old reorder settings back to reality

  • The agent compares each setting with what really moved, and each lead time on file with what the supplier actually did.
  • It prepares the exceptions worth a look, and leaves Odoo’s replenishment rules to do their job.

In your distribution operation

What if supplier part numbers are inconsistent?

The agent proposes the most likely matches and isolates uncertain lines. A buyer approves before any catalogue or price update.

Can it turn PDF or email orders into order lines?

It can prepare the likely products, units and depots. Exceptions remain visible and the order is reviewed before validation.

Does this work across several depots and pricelists?

Yes. The scope follows your actual rules by company, depot, customer and supplier instead of applying the same model everywhere.

Odoo already handles replenishment. What do you add?

Reordering rules and proposals remain native. Basalt can compare settings with real movements, expose stale parameters and prepare their review.

What volume makes the project worthwhile?

There is no universal threshold. Repetition and handling time matter more than the number of products. Map measures that against your week.

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