01
Start with the source.
Keep supplier columns and item references together so each update can be traced to its source.
Supplier price updates
Before the import,
see what changed.
A new supplier file. A new set of changes. We’re exploring a clearer way for distributors to review price changes before they reach the ERP.
Share your workflow
Written conversations.
No meeting required.
No meeting required.
What changed. What needs a look.CONCEPT
supplier_update_example.csv
Supplier file → price review
| Item | Current | Incoming | Review |
|---|---|---|---|
| DEMO-104 | $12.40 | $13.10 | Price changed |
| DEMO-208 | $8.50 | $8.50 | Unchanged |
| DEMO-312 | — | $22.00 | Match needed |
Human approval before export3 sample rows
Where we are
CatalogSpan is in early discovery. We’re exploring the workflow below with distributors; no product or ERP integration is available yet.
01 / The concept
Less uncertainty at every handoff.
The concept: keep the source, the changes, and the approval in one clear review.
02
Put exceptions in view.
Bring changed prices and uncertain item matches into the same review.
03
Keep approval deliberate.
Give the reviewer a clear point to approve a file before the existing import process.
Supplier file → review changes → human-approved export.