See it on a file
Three files, three different outcomes
No account, nothing to upload. Pick a file and see what the mechanism produced for each one, including what it refused to do.
- file lines
- 218
- rows read
- 214
- matched
- 96%
- reading
- 2 minutes
Sample rows
- Bath towel 70x140AL-221012,90
- Ceramic mug 350 mlKR-1188,40
- LED desk lampNV-0345,60
- Travel caseTX-905Cost dropped 72% since last time. Needs your eyes.0,45
- PAGE TOTALA total row, not a product. Never became a price list row.no price
Five of the file's rows. Flagged ones always come first on the review screen.
No file-level observations. Match rate and median price are where you would expect them.
Review zones
- Needs attention3
- Ready198
- New products9
- Not in price list4
- Skipped0
The above are stored results from three real files, not a run happening now. Nothing is sent and nothing is stored. With your own files and your own catalogue the numbers will differ, and the match rate in particular depends on how closely your codes agree with your supplier's.
What a sample cannot show
The three above show reading and matching. The part that touches your store starts after that.
01
Your selection
Pick row by row or in bulk, change any price, leave out whatever does not convince you. The button always states how many changes will be sent.
02
The push
Before writing, the system re-reads your store and excludes anything that is not as you saw it. After writing, it reads back to confirm.
03
Undo
Previous prices are stored before every write. Undo writes them back, recalculating nothing.
The next step is a file of your own
Fourteen days, no card. You do not need to connect a store to upload a price list and watch it being read.
Want to see what setup takes first? The twenty minute guide