Compare the new supplier file with ours. Apply safe price and product updates, never delete a missing product automatically, and show unusual differences separately.
COMMAND
Project objective2%
WORKFLOW 03 · DATA + PURCHASING
Reconcile a Supplier Catalogue Without Losing Business Judgement
Compare thousands of supplier changes, apply safe updates and separate missing, conflicting or commercially unusual records for review.
THE BUSINESS SITUATION
A supplier sends a new catalogue. Prices changed, codes were replaced, new products appeared, old products disappeared and some descriptions contradict the current catalogue.
Nexus classifies differences by business meaning before acting. A normal price update, a changed code and a disappeared product are not the same decision.
Supplier fileProduct databaseWeb cataloguePricing rulesPurchasing reviewMission history
Watch the work move through Nexus.
The screen keeps the objective visible while the project, systems, AI roles, progress, decisions and verification move through one operational record.
OPERATIONAL LOGICWhat Nexus is actually doing behind the mission.
01Interpret & authoriseDefine which records may be read, changed, merged or held for human review.
02Connect & profileOpen the authorised source file and database workspace; inspect schema, record counts, identifiers and data quality.
03Match & classifyCompare records, separate safe corrections from ambiguous cases and calculate the impact before writing.
04Back up & applyCreate a recoverable checkpoint, then write only high-confidence changes inside the approved scope.
05Re-query & verifyRead changed records back from the database, reconcile totals and test that no new contradictions were introduced.
06Record the rulesRetain matching logic, exceptions, evidence and accepted decisions for the next import.
MISSION ACTIVITYConnections, inspection, actions and proof in one operational record.
15 / 15 eventsI understand the requested outcome. I am fixing the scope, constraints, authority and evidence required before work begins.
INTERPRET
Scope · constraints · authority · success test7%
Verified permission to update prices and prepare clear new products. Product deletion, identity merging and large price exceptions remain outside automatic authority.
AUTHORISE
Project permissions · capability scope · blocked actions12%
Opened the supplier file from the approved intake location and connected to the internal catalogue database. The source file hash and database identity were recorded.
CONNECT
Supplier source + Catalogue database + Matching index18%
Created a catalogue checkpoint and preserved the untouched supplier source so every proposed change can be traced back to its original row and value.
CHECKPOINT
Supplier source + Audit package24%
The new supplier catalogue and the current internal catalogue were normalised without altering the source files.
LOAD CONTEXT
Project rules · history · accepted decisions30%
The data worker is profiling columns, normalising codes and units, and matching supplier rows to internal products using identity, history and business rules rather than one field alone.
INDEX
Files · pages · records · linked business data37%
8,000 supplier rows were matched against product identities, codes, descriptions, prices and historical mappings.
DISCOVER
Authorised working environment45%
Nexus separated 731 routine price changes, 86 clear new products, 41 possible discontinued products and 17 conflicting records.
PLAN
Work graph · normal cases · exceptions55%
Approved price changes were applied, new products were prepared, and protected categories remained outside the write set.
EXECUTE
Authorised change set70%
The Reviewer checked duplicate identities, implausible price movement, missing required fields and contradictions introduced by the update.
VERIFY
Result against objective and project rules84%
The mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
CONTROL
Permission and scope boundary91%
Fifty-eight items are ready in one purchasing review queue with the old value, proposed value, evidence and consequence of each choice.
DECIDE
Human attention queue97%
The catalogue is reconciled. Routine work is complete; possible removals and conflicts remain protected for purchasing judgement.
RESULT
Verified mission stateMission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
STORE
Project history · evidence · decisionsATTENTION QUEUEReview protected catalogue exceptions
VERIFICATION
- Supplier source and internal catalogue remain traceable.
- No product is removed because it disappeared from one file.
- Routine price updates passed margin and identity checks.
- Every protected exception includes supporting evidence.
How Nexus carries the objective from request to result.
The work stays attached to one outcome even when several systems and specialist AI roles contribute.
- Read the supplier file and the project’s catalogue rules.
- Match products using stable identities and supporting fields.
- Classify unchanged items, price changes, new products, missing products, code changes and conflicts.
- Apply only the classes explicitly authorised for routine handling.
- Hold possible removals and unusual price movements for review.
- Re-check the resulting catalogue for contradictions and duplicate identities.
- Preserve the comparison and decisions for the next supplier update.
Nexus removes routine operation, not responsibility.
Purchasing reviews removals, unexpected price jumps and conflicting product identity. Routine catalogue maintenance can remain delegated.
8,000Products compared
731Routine price changes
86New products prepared
58Review items
Review queue ready
The catalogue is reconciled. Routine work is complete; possible removals and conflicts remain protected for purchasing judgement.
The finished work remains inspectable.
The mission closes with source-linked evidence, a clear authority record and verification against the original objective.
Verified
Supplier source and internal catalogue remain traceable.
Verified
No product is removed because it disappeared from one file.
Verified
Routine price updates passed margin and identity checks.
Verified
Every protected exception includes supporting evidence.
The result remains the centre of the mission.
Nexus reduces spreadsheet volume to business exceptions while keeping the original evidence and rules visible.
One command bridge can coordinate more work.
The same mission can update the web shop, purchasing database, sales documents, margin rules and customer notifications after approval.
Open another complete Nexus workflow.
Every case uses its own project, systems, messages, decisions, metrics and result while preserving the same mission language.
04Website operations
NX-2404Completed
Keep a Portfolio of Websites Healthy
Check many sites, repair known-safe file and content issues, and return only the failures that genuinely need attention.
OPEN MISSION WORKFLOW
05Customer service
NX-2405Completed
Resolve a Customer Problem Instead of Merely Answering It
Connect the customer conversation to the order, inventory, policy, replacement workflow and confirmation so the issue actually reaches a result.
OPEN MISSION WORKFLOW
06Product development
NX-2406Publication approval
Build a Customer Configurator from Business Rules
Let the owner describe how customers should choose and what the price should do; organise the design, data, build and checking as one mission.
OPEN MISSION WORKFLOW
What would this mission look like inside your company?
Describe the project, outcome and decisions you want to retain. Nexus organises the operational work around them.