THE KEY POINT
If your team re-enters orders in several systems and corrects discrepancies by hand, the need may lie in integration, in the process rules or in how exceptions are handled. AI may help with part of it, but it is no substitute for understanding the full flow.
The order exists. The information arrives out of step.
A customer sends an order by email. The same order is entered again when it is forwarded to another team, with no common reference to detect the duplicate. Sales confirms one quantity, operations receives another version and administration prepares the invoice with the data it has. The ERP captures part of the flow, but a change still travels through messages and phone calls. When the discrepancy appears, the team has to reconstruct what happened.
The problem is not necessarily a missing tool. The tools may not share information, a change may not be recorded, or nobody may be clear about which version should be used. Automating that flow without clarifying it can simply reproduce the same bottleneck faster.
«The order is in the ERP, but the change in quantities stayed in an email. Operations has already prepared it and invoicing is asking us again which amount is correct.»
Before asking for a solution, follow one order from start to finish.
The starting point is a specific situation. It helps to understand the usual flow and also what happens when a piece of data is missing, a quantity changes or a delivery is cancelled.
- Where the order originates and who confirms its information.
- Which system holds the reference that the other teams use.
- At which steps data is re-entered, and why.
- How changes are communicated after the order is confirmed.
- Who spots an exception and who can resolve it.
- How large and how frequent the problem is, and what work it delays.
The expertise you need depends on the work to be done.
The same situation may call for several capabilities. That does not mean you need to hire several people: first you need to understand which work predominates and what collaboration it requires.
| What is happening | Capability worth exploring |
|---|---|
| The systems do not exchange data, or do so incompletely. | Systems integration: interfaces, common references and error handling. |
| A stable sequence of checks and notifications is repeated. | Process automation: rules, exceptions and follow-up. |
| Information arrives in documents or messages in different formats. | Applied AI, if it helps to extract or interpret information with checks in place. |
| Each team uses the flow in a different way. | Adoption and improvement: working agreements, explanation and support. |
| There are decisions spanning departments, suppliers and critical systems. | Technical leadership to coordinate priorities and responsibilities. |
A one-off intervention or capability within the team?
If the work consists of connecting a well-defined flow and maintaining it through periodic reviews, a specialist firm or an external collaboration may be a good fit. The size of the organisation alone does not determine whether a new hire is needed.
If there are continuous improvements across departments, day-to-day decisions and a sustained need for maintenance and adoption, it is worth exploring capability within the team. The time commitment depends on the work that will still exist after the first change.
What a candidate should demonstrate.
Naming an ERP or an automation tool does not explain how the person would approach this flow. What matters is what they would ask before changing it, what they would prioritise, how they would check that the data is correct and how they would explain the new way of working to the teams.
The BUSCOS Evidence service uses five scenarios tailored to the role and the company. Each one explores four skills: identifying problems, prioritising improvements, implementing and verifying, and explaining results. The answers and their audio explanation are brought together in a human-reviewed report before the interview.
Frequently asked questions
Does having an ERP prevent this problem?
An ERP can centralise information, but it is worth checking which flow it covers, how it connects with the other tools and how it receives changes and exceptions.
Do we need AI to solve it?
Not necessarily. Some needs are solved with integration, rules and working agreements. AI is explored when it adds something specific to the flow.
Does BUSCOS implement the solution?
No. BUSCOS helps you clarify the expertise and skills you need, and obtain evidence about candidates. If an external intervention is a better fit, it may suggest specialist firms.
Keep clarifying what you need. A specific situation is the starting point.
