Skip to content
ChangeAtlasCommerce
Intake

Upload

Drop the proposal you are about to import and, ideally, an export of the catalog as it stands. Both files are read in this browser — digested, bounded, and matched to a pinned profile. Nothing is uploaded anywhere.

Required
Proposal

The file you are about to import.

Drop a .xlsx or .csv here, or press Enter to choose one

Optional · recommended
Baseline

An export of the catalog as it stands. Recommended: without it, changes cannot be classified.

Drop a .xlsx or .csv here, or press Enter to choose one

Add the proposal to start.

Sample analyses

Autumn catalog updateBLOCK
proposal.xlsx vs baseline.xlsx · ~1,000 rows

The walkthrough sample: three blockers, a dozen warnings, two checks that could not run.

Autumn catalog update (corrected)READY
proposal-fixed.xlsx vs baseline.xlsx · ~1,000 rows

What READY looks like: the corrected file with only advisory warnings left.

Price list refreshREVIEW
products-proposal.csv vs products-baseline.csv · ~300 rows

A REVIEW verdict with a declared execution intent, so the Intent screen shows conditional expected effects.

Full catalog re-exportUNKNOWN
full-catalog.xlsx vs full-catalog-baseline.xlsx · ~10,000 rows

An UNKNOWN verdict: a required sheet is missing, so two checks cannot run until coverage is declared.

Parser budget (what bounds every upload)
parser-budget@1.0.0

Bounds

Bytes per source
25 MiB
Data rows
10,000
Columns
256
ZIP entries (xlsx)
256
Decompressed total / per entry
100 MiB / 50 MiB
Compression ratio
100:1
Sheets
16
Worker time per source
8 s
Decoded allocation
128 MiB
Parser workers
1, cancellable