Self-initiated tool · Catalog change review
ChangeAtlas Commerce
See what a catalog import could change.
The problem
An omitted column, a cleared value, and a changed identifier can look similar in a spreadsheet but mean different things for a catalog. Reviewers need the source row, the intended import behavior, and any missing evidence before approving the file.
The solution
I built ChangeAtlas Commerce to compare a catalog export with a proposed file, then connect each difference to its source row, related records, and review findings. A spreadsheet shows a changed cell. The review needs to explain what that change could affect.
The analysis runs in the browser. It prepares a review package; it does not write changes to the store.
From a changed cell to a review decision
Source files
Baseline catalog + proposed changes
Review the difference
Changed values · cleared fields · missing evidence
Review package
Findings + related records + unresolved questions
The workflow
Read the source files. Choose the supported source profile and inspect the baseline and proposed catalog data.
Inspect the differences. Follow changed, cleared, omitted, and rekeyed values back to their sheet, row, and column.
Review the reach and coverage. Inspect related records, unresolved references, and checks that could not run.
Correct and verify. Re-run the corrected file and export the review package for the person who signs off.
A conversation is a good place to start.
Let’s talk about
the work.
Send the role, or your website and what needs to change.
Warren, Michigan