Customer story · Retail
A retail customer
AI-assisted stock correction for a retail customer
The system does the comparison and math. The category manager decides what changes.
Executive summary
The situation
Physical and presentation stock must be compared with system records. A discrepancy alone does not say which adjustment deserves attention; product importance and a manager’s judgement still matter.
What was built
Nexus compares inputs, classifies discrepancies by risk and priority, and generates recommendations weighted by ABC classification. A custom dashboard lets category managers review, edit and approve them.
Why it matters
Designed to reduce the comparison and calculation burden while preserving the commercial decision. No adjustment is exported toward ERP until a person approves it.
- Primary users
- Category managers
- Core systems/data
- Physical, presentation and system stock
- Human control point
- Manager approval before ERP export
- Nexus role
- Comparison, prioritisation and recommendations
The challenge
Stock that does not match the system.
Physical, presentation and system stock do not always tell the same story. Comparing them identifies a difference, but deciding what to do about it requires another layer of judgement. Product importance and the priority of a discrepancy matter.
The calculation work had to lead into a category manager’s decision, not bypass it. A recommendation needed to be understandable and adjustable before it could become an ERP-bound change. Automation could prepare that work without owning the commercial call.
What we built
Recommendations a category manager approves.
Nexus brings stock inputs together, calculates discrepancies and classifies them by risk and priority. Recommendations are weighted by product importance using ABC classification. This produces a reviewable proposal rather than treating every difference as an instruction to change stock.
The category manager reviews those proposals in a custom dashboard and adjusts them where their judgement calls for another answer. Approval is separate and required. Nothing is exported toward ERP before it, and the values that leave are the values the manager accepted. The system does the comparison and math. The category manager decides what changes.
How the workflow runs
Step by step.
01
Collect stock inputs
Physical, presentation and system stock data are brought together. Discrepancies are calculated per product.
02
Classify
Each discrepancy is ranked by risk and priority. Order adjustments are proposed, weighted by ABC classification.
03
Review and approve
The category manager adjusts and approves in the dashboard. Only approved adjustments are exported toward ERP.
What the business team sees
A review dashboard for category managers.
The dashboard gives the manager a prioritised starting point, with the recommended adjustment and its reasoning. A proposal can be changed before approval. This is a decision workspace, not an unattended correction engine: calculated recommendations on one side, the manager’s judgement on the other.
- Discrepancies by risk and priority
- ABC classification per product
- Recommended order adjustment
- Edit before approval
- Approved export queue
How Nexus works underneath
The approval gate is part of the process.
Discrepancy calculation and ABC weighting run as deterministic logic. AI-assisted classification organises the review work, while Nexus keeps ERP export downstream of human approval. The dashboard is where the manager decides; the orchestration underneath ensures a proposed adjustment and an approved adjustment are not treated as the same thing.
Architecture
How the layers fit together.
Business team
Category manager dashboard
Ranked discrepancies · recommendations · adjust · approve
Nexus orchestration
- 01Stock comparison
- 02Risk classification
- 03ABC weighting
- 04Recommendation
- 05Approval gate
- 06ERP export
Connected systems and data
- Physical / presentation stock
- System stock
- ERP
Human control and audit
Nothing changes without the manager.
Recommendations are proposals. The export step is gated on approval, and the approved values, including any manager adjustments, are what leave the system.
What this changes
A prioritised starting point. Gives managers a ranked list rather than treating all differences alike.
Calculation before judgement. Defined comparison and weighting prepare recommendations that managers can inspect.
Approval before export. Only manager-approved values leave toward ERP; a recommendation cannot trigger that change by itself.
Your process
Discuss a similar workflow
Tell us about the documents, systems and decisions involved. We will discuss where Nexus orchestration fits and where your team stays in control.