What the parser collects and where it goes
The parser puts what it finds on the website into the source price list: page fields, photos, files and specifications. Here you will learn what exactly it takes, what happens to the price list on a repeat run or a break-off, and how collected specifications end up in your attribute directory.
- What exactly the parser takes from a product page
What data the parser collects from a product page: 64 rule rows, 33 product page fields, photos, videos, files, and specifications. How to set up each field and what the app does with the value it finds.
- How the parser updates a price list: new products, reruns and interrupted runs
How the parser tells a new product from one it already collected, what happens to prices on a rerun, what stays in the price list after an interrupted run, and when to click “Continue”.
- How specifications from a website become attributes in your catalog
How specifications collected by the parser land in your attribute directory: the mapping dictionary, AI matching, an attribute into a card field, and how to remove extra attributes without bloating the directory.
