Bring the price list.
Keep the context.

1. Export your current catalogue

Use your existing spreadsheet or inventory system's supplier-product export. Keep the supplier SKU separate from your internal SKU. Include current purchase price, base units per purchase pack, base unit, currency and tax basis.

For example, a purchase price of 24 for a case of 12 bottles has 12 base units per purchase pack and a base unit of each. If your file has a price per each, its pack quantity is 1—only state that if you know it is true.

2. Add the incoming supplier CSV

Use a comma-separated UTF-8 CSV with one header row and one product/price basis per row. Up to 10,000 rows and 2 MB per file. PDF, XLSX and unstructured text extraction are not enabled in this build; export a CSV from your spreadsheet first.

Row count and file size are independent limits, not a guarantee that every maximum-size review fits. The full request is limited to 4.2 MB, including repeated original inputs when exporting a revision. Complete result evidence is limited to 64 MB decoded and 4 MB transferred, using standard browser gzip support when needed. Oversized records are rejected without dropping rows; split wider files or longer histories into smaller supplier reviews.

Prices must be plain decimal values, with no currency symbol or thousands separator. The supported base units are each, kg, L and m. Missing information becomes an exception rather than a guessed value.

3. Map the columns and confirm the basis

Recognised headers are suggested; review them. Both files must describe the same supplier and comparable product universe. Identifiers match exactly, preserving leading zeroes and punctuation. Duplicate rows and price tiers need clarification before they can be treated as a cost change.

4. Add optional commercial context

Selling price must be per base unit, excluding tax and in the same currency as the supplier cost. Margin is (selling price − unit cost) ÷ selling price. It is not markup, and supplier price alone is not landed cost.

Expected quantities create a projected purchase-cost change for your named period. They are not realised savings or an inventory valuation. Freight, duties, overhead, discounts, FX and changes in demand are not modelled. Non-comparable or missing-volume rows are excluded and counted.

5. Decide, then keep the review record

Stage comparable changes, keep current values or hold an item with a clarification note. Pack-size changes cannot be bulk-staged. An absent SKU is not automatically discontinued. Download the internal CSV for review or JSON for full source evidence and decision history.

No file is an ERP-ready import. No catalogue, purchase order or accounting record is changed. Your account stores identity and billing, not durable review history; download your record before starting another review or leaving the page.

6. Ask specific questions, then check the revision

Download a clarification draft with unresolved source evidence and your hold notes. It is an internal file, not an email or supplier submission; check its confidential contents and recipients before sharing.

Load one revised supplier CSV against the same locked catalogue and commercial scenario. StockBridge compares unique supplier identifiers across versions and separates resolved evidence, remaining issues, new exceptions and unverifiable continuity. A removed duplicate, absent or renamed SKU is not automatically counted as resolved. Revised inputs start with fresh decisions; the prior review and decision history remain available in a separate download and in the combined JSON.

The workspace supports one revision per working session. Download before reloading or clearing. The record is reviewer-supplied history validated against recomputed results, not a tamper-proof or signed supplier response.