Product cards, grid or list
Product links come from the category's cards, whether the shopper has the grid or the list layout switched on, so a page is listed before any product is opened.
BigCommerce stores built on Stencil themes (Cornerstone and the many themes derived from it) keep every product detail in the same places: the SKU in a data attribute, the RRP in the price box, the full gallery behind the main photo. Web Product Scraper has a reader for exactly that layout. Point it at a category, brand or search page and you get one row per product and every gallery photo, with the theme's small copies swapped for the original upload.
Add to Chrome, it's free No account · private by default
If it is your own store, use the control panel: Products, then Export. If it is a supplier's or another public store, open one of its category pages in Chrome, click the Web Product Scraper icon and press the Scrape button. Each product becomes a row with its name, price and link; choose Full: open each product page and the SKU, brand, RRP, category, description and gallery are added before you download Excel, CSV, JSON or a photo ZIP.
Stencil themes share their markup, so each value has a known place.
Product links come from the category's cards, whether the shopper has the grid or the list layout switched on, so a page is listed before any product is opened.
The SKU from the element the theme marks data-product-sku.
Stores that display prices both ways show two figures; the one without tax goes in the price column. A retail price (RRP) is kept only when it is above the selling price, and lands in the MRP column; a sale's Was price is not taken.
The brand link in the product view, the last breadcrumb before the product as its category, and the text of the product's description area.
Every gallery photo, from the main-image address each gallery link carries, not the small thumbnail.
Category results are numbered ?page=2, ?page=3 with a Next arrow at the bottom. A run follows that arrow up to the last page you set.
BigCommerce serves product photos from its image CDN in size folders: one picture exists as /images/stencil/500x659/, /images/stencil/1280x1280/ and more, and the theme picks a size for each spot on the page. When a photo comes from a small size folder (under 1000 px, such as /500x659/), Web Product Scraper asks for the /images/stencil/original/ file instead; a copy already 1000 px or wider, such as 1280x1280, is kept.
Because a store links the same picture in several sizes, those copies are recognised as one image: each product folder in the ZIP holds every photo exactly once.
Merchants already have an export. In the control panel go to Products, choose Export, pick a template such as Bulk Edit, and download a CSV in the format BigCommerce imports again.
Without a login to someone else's control panel, the public catalogue is what you have. The extension reads the pages you open, so nothing is installed on that store and no API key is needed.
The control-panel CSV holds image addresses in columns. Here each photo is downloaded into a folder named after its product, beside the spreadsheet.
This spreadsheet has one plain row per product, not BigCommerce's Item Type rows for products and their variants, so map the columns when you import it into a store.
Real exports the extension made from its own sample shop: 12 made-up products, two pages, read in Full. They show what the files hold; they were not made from a BigCommerce store.
The main use: a category and its numbered pages, from the first to the last you choose.
Stencil gives every brand its own page of product cards, which reads like a category.
The store's search.php results list cards the same way, so a search inside the store can be exported too.
On a product page, that product alone is taken with its gallery; the related and recently viewed products below it are left out.
Options such as size or colour change the price and SKU with a script after the shopper picks them. The table keeps what the page shows when it loads, one row per product, so prices per option are not listed.
Headless storefronts, such as those built on BigCommerce's Catalyst, do not use Stencil markup. There the general reader takes over with the structured product data most storefronts publish, and "Teach this site" lets you click the right value once when a field comes out wrong.
There is no separate column for the price with tax. On a store that shows only the price with tax, that figure is the price.
A sale's Was price is not read: only an RRP goes in the MRP column.
A SKU set only on a product's options is likely to stay empty.
Photos: a copy already 1000 px or wider is kept as it is, Quick keeps the photos of the product cards without swapping them, and each product keeps up to 20 photos.
By default a run reads the current page only (choose All pages for the rest) and stops after 100 products.
Often: a small copy is swapped for the uploaded original; a copy of 1000 px or more is kept.
Stencil themes, Cornerstone and the many built from it, go through the BigCommerce reader. Other layouts fall back to the general reader and, where needed, to a rule you teach it with one click.
Only when the store's structured data lists the options (a schema.org ProductGroup): then tick Variants. Otherwise each product is one row, with the SKU and price its page shows before an option is chosen.
No. It reads public pages in your own browser. Whether you may reuse what you collect depends on the store's terms, so check them, and keep the default pause between pages.