Catalogue audit: compare approved changes with a staging export

A bulk import can finish without errors and still leave the wrong prices or stock counts behind. This original Sheetstead Studio demo shows how to check a staging export against the agreed catalogue changes before release.

What I built

A read-only Python check compares three CSV exports by SKU: the baseline, the approved changes and the updated staging export. It reports expected and observed values for missing or unexpected products, unapproved changes and mismatched approved prices or stock counts.

What I verified

On fictional data, two of four approved changes matched at first and five exceptions were flagged. One SKU should have had 15 units but still showed 12. After the corrections, four of four approved changes matched and the recheck found zero exceptions across eight expected products.

This is an AI-assisted studio demonstration. It uses fictional files and makes no changes to a live store. The results were checked against known fixture values.

[View the audit results and before-and-after comparison](https://www.twine.net/signin