A B2B distributor on the Costa del Sol receiving catalogue orders, stock queries and email quotes does not need an AI agent that does everything: it needs to decide which tasks are worth automating and which must stay with a person. The prerequisite is an up-to-date catalogue with reliable references, prices and availability. Without that base, any agent answers quickly but badly. This article sets out a realistic order: prepare data, choose low-risk processes, define action limits and measure results, without promising miracles or replacing the commercial relationship that keeps recurring customers.
What an AI agent means in B2B distribution
In a distributorship, an AI agent is a layer that interprets incoming messages or documents (an email with an order, a reference query, a price request) and executes or prepares a specific action: extracting order lines, checking availability in the catalogue, drafting a reply or opening a task for the salesperson. It is not a generic chatbot or an ERP replacement.
The practical difference lies in scope. A conversational assistant answers questions; an agent connected to data can check stock and propose an action, but it should only execute it if the process is defined and supervised. In distribution, most gains come when the agent prepares the work and a person validates it, not when it acts without control.
Informational agent
Answers queries about references, lead times or conditions using the catalogue and customer records. It does not modify orders or prices.
Assisted operational agent
Extracts lines from an email, checks stock and generates a draft order or quote for someone to confirm before sending.
Bounded autonomous agent
Acts alone only in narrow cases (for example, confirming availability of active references) and escalates to a human when exceptions arise.
An up-to-date catalogue is the prerequisite, not a detail
If the catalogue has duplicate references, outdated prices or out-of-sync stock, the agent will repeat those errors faster. Before automating, clean references, unify sales units, flag discontinued products and decide which fields are mandatory for safe answers.
A perfect catalogue is not required to start, but a reliable one is needed in the fields the agent will use. A useful exercise is to pick the 200 most-queried references and verify that price, unit, lead time and availability match the ERP. If there are discrepancies, the first project is not AI: it is data quality.
- Define which catalogue fields the agent may quote and which it may not (for example, customer-specific prices).
- Flag discontinued references and substitutes to avoid answers with products you no longer supply.
- Set a synchronisation frequency with the ERP and a person responsible for reviewing incidents.
- Document sales units and minimums per reference: they are the usual cause of misread orders.
Comparison: what to automate and what not to in your operation
Not every process carries the same risk. Repetitive order entry and stock queries are usually good candidates because the data exists and validation is simple. Price negotiations, quality incidents or customers with special conditions require commercial judgement and should stay with a person.
The table below is guidance, not a recipe. Before deciding, review how often each task happens per month, how much time it consumes and what an error would cost. A frequent, low-impact process is usually a better first automation than a rare, delicate one.
| Process | Reasonable automation | Should stay with a person |
|---|---|---|
| Email order entry | Extract lines and references, generate a draft to validate | Confirm special prices and agreed conditions |
| Stock query | Answer availability of active references with ERP data | Commit lead times when there is a stockout or order in progress |
| Repetitive quotes | Prepare a draft with lines and standard conditions | Negotiate discounts and exceptions |
| Order tracking | Report standard status and flag expected delays | Handle complaints and incidents |
| New customers | Collect data and classify the query | Validate solvency and credit terms |
| Quality complaints | Log and classify the case | Investigate, decide and reply to the customer |
How to prepare the catalogue and data before activating the agent
The preparatory work can be set out in four steps. First, inventory sources: ERP, spreadsheets, PDF catalogue, customer-specific price lists. Second, choose a single source of truth for price and stock. Third, define what information is public and what is for internal use only. Fourth, establish who updates it and how often.
Many distributors run a commercial catalogue alongside operational ERP data. The agent must know which one rules in each case. If the salesperson keeps special prices in a separate sheet, that sheet must be integrated or explicitly excluded from scope. What is not decided beforehand shows up as an error in the first week.
Single source for price and stock
Choose the ERP as the reference and define a minimum daily sync. Special price lists are treated as a documented exception.
Response rules
Establish what the agent may say when it cannot find a reference: ask for clarification, offer an alternative or hand over to a person. It must never invent availability.
Order entry: the process with the most return and the most care
The order email is where the most time is lost: lines in different formats, abbreviated references, quantities in different units. An agent can read the message, propose lines with reference and quantity, and flag doubts. The person reviews, corrects and confirms. The saving lies in preparation, not automatic confirmation.
The limit must be clear: the agent does not confirm orders or commit lead times without validation. If it detects an ambiguous reference, an unusual quantity or a customer with special conditions, it must open a task. This design reduces errors and keeps the trust of recurring customers, who notice when their order is understood first time.
- Start with the ten customers who send the most email orders and study their formats.
- Set a quantity or value threshold above which a person always validates.
- Log the corrections the team makes to improve the agent's rules.
- Do not automate order confirmation until the correction rate is low and stable.
Stock queries and tracking: answering without overpromising
Answering availability is useful if the data is reliable and the agent distinguishes physical, committed and in-transit stock. An answer that mixes these states creates commitments the warehouse cannot meet. The agent must use ERP data and express uncertainty where it exists.
Order tracking follows the same logic. Reporting standard status is reasonable; handling a delay complaint is not. When the customer asks why their order has not arrived, the reply must include a person who can review the incident and offer a solution. Automation saves time; it does not replace responsibility.
| Situation | Agent response | Escalation |
|---|---|---|
| Active reference with stock | States availability and sales unit | Not needed |
| Reference out of stock | Informs and offers an alternative or alert | If the customer asks for a committed lead time |
| Order being prepared | Reports standard ERP status | If there is a delay against what was agreed |
| Delivery incident | Logs the case and alerts the owner | Always to a person |
| Customer with special price list | Does not quote price; hands over | Always to the salesperson |
Email quotes: where to set the human limit
Preparing a quote with lines, quantities and standard conditions is a repetitive task an agent can draft well if the catalogue is clean. The salesperson reviews, adjusts discounts and sends. The value is in reducing preparation time, not removing review.
The limits must be written down: which discounts the agent may apply (usually none), which conditions it may quote and when it must hand the case to a person. A quote sent with the wrong price costs more than the time saved. The practical rule is that the agent prepares and the person signs off.
Assisted draft
The agent proposes lines and standard conditions from the email and the catalogue. The salesperson validates before sending.
Flagged exceptions
Discounts, special lead times or new customers are automatically flagged for human review.
Common mistakes when deploying agents in distribution
The most common mistake is starting with the tool rather than the process. Another is automating before cleaning the catalogue, which amplifies existing errors. It is also common not to define who reviews responses or how they are corrected, so the agent learns from bad data.
A fourth mistake is measuring only time saved and not quality: poorly prepared orders, answers with invented lead times or customers who lose trust. Sensible deployment includes a trial phase with a few customers, clear metrics and an owner who adjusts rules. Without that discipline, the agent is seen as a problem, not a help.
- Do not activate the agent with an unreviewed catalogue: data first, automation second.
- Assign an internal owner to review responses and correct rules weekly.
- Test with a small group of customers and processes before extending it.
- Measure errors and corrections, not only time saved.
- Document what the agent does and does not do, so the team explains it consistently.
How the agent fits with your team and your customers
The agent does not replace the salesperson: it removes repetitive work so they can spend time negotiating, visiting and solving. It is worth explaining to the team what the agent does, what it decides and where the stop button is. Internal transparency prevents resistance and makes corrections easier.
With customers, the key is not to pretend. If a customer receives a reply prepared by an agent, they must be able to ask for a person without friction. In B2B distribution the relationship is built on reliability: answering fast is good; answering badly or with no human exit is not. The agent must always have a clear escalation path.
Visible escalation
Every agent response includes a simple way to request human attention. The customer should not feel they are talking to a wall.
Informed team
Staff know the scope, limitations and the procedure for correcting wrong responses.
Budget and scope: what to ask before hiring
Before hiring an AI agent, ask for a written description of scope: which processes it touches, which data it uses, what it decides alone and what it hands over. It is also worth agreeing how results are measured and who keeps the catalogue up to date. Without that clarity, the project is judged on impressions rather than performance.
Solaris handles these projects with a custom quote, because scope depends on the catalogue, the ERP and the chosen processes. An agent for stock queries does not cost the same as one preparing orders and quotes from several data sources. Ask for separate phases and a first phase that is narrow and verifiable.
| Element | What must be in writing | Why it matters |
|---|---|---|
| Agent scope | Processes and tasks included and excluded | Prevents unrealistic expectations |
| Data sources | ERP, catalogue and price lists consulted | Determines reliability |
| Autonomy level | What it decides alone and what it hands over | Defines operational risk |
| Maintenance | Who updates catalogue and rules | Without this the agent degrades |
| Measurement | Errors, corrections and preparation time | Lets you decide whether to continue |
At Solaris, AI agents are quoted case by case: there is no fixed rate until the process, the channels and the data are defined. Local SEO for the Google Maps listing, if you need it too, starts at €150 per month + VAT, or €250 per month + VAT with articles.