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

Retail & E-commerce

Every channel describes the same business differently. Basalt breaks a marketplace payout back into orders, proposes the duplicate customers worth merging, and catches product information that has drifted between channels. Your team reviews exceptions instead of rebuilding the picture every week.

Where your team’s time goes

01 / 03

A marketplace pays you once for forty orders, minus commission, minus returns, minus fees, and someone has to work out which is which.

Finance cannot close the payout until every deduction is matched back to the orders and returns behind it.

Where your team’s time goes

02 / 03

The same customer in your system four times: she bought in store, on the site, and twice as a guest.

Small differences in names, emails and addresses split one relationship across records and weaken the customer view.

Where your team’s time goes

03 / 03

The same product described one way on the site, another in the shop, and priced differently on the marketplace.

Channel drift creates avoidable corrections for the team and an inconsistent promise for the customer.

Workflows

Break one marketplace payout back into its orders

  • The agent prepares the order-by-order breakdown across sales, returns, commission and fees, then isolates anything it cannot match confidently for finance to review.

See one customer instead of four records

  • Odoo merges contacts when the email or the name matches exactly.
  • Two addresses and one typo beat it.
  • The agent spots the same person and proposes the merge.
  • You still approve it.

Catch product drift before a customer does

  • The agent compares descriptions, prices and options across your approved channels and prepares the differences that need correcting.

Across your channels

Do we need to replace our marketplace connectors?

No. They continue to move orders and payments. Basalt works on exceptions, detailed reconciliation and cases that currently require manual work.

How do you reconcile one payout covering many orders?

The agent rebuilds the detail from the payout, orders, fees, returns and commissions available. Uncertain items are isolated for review.

Can an agent merge customers automatically?

It can identify and propose duplicates. A person approves the merge because a bad merge can cost more than a duplicate.

Does it work across several shops and warehouses?

Yes, when locations and channels are identifiable. Rules are defined by company, site and channel during Map.

How do you find price or product-detail differences?

We compare the useful fields across Odoo and connected channels, then present the gaps. The team chooses the correct value and triggers the correction.

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