This is the cleanest result in our supplier catalogue. One product URL came back with fifteen of seventeen columns populated - name, brand, price, currency, stock, both identifiers, a full description and images - and we checked every one of those values against the live page.
/products/ page or a /collections/ page. Other shapes are rejected, and the status column says so in as many words.Our successful run returned a full retail title, the manufacturer in its own brand column, a price as a computable number, a currency, a stock status, both identifier columns, a paragraph of product copy and an image URL. Only rating and reviews came back empty. Among the supplier catalogues on this schema, that is the fullest row we hold.
Fetching the same product URL returns about 620 KB of HTML carrying three structured-data blocks, one of them a full product record whose offer node states the same currency, the same price and the same stock status our export holds. The item number appears two dozen times in the markup and the manufacturer over a hundred. Nothing in the row is inferred - it is all on the page.
Our two other runs submitted a placeholder address and did not come back with a bare error. They came back with unsupported URL (use a /collections/ or /products/ URL) - the service naming the two shapes it takes. That is unusually helpful, it matches the vendor's own recorded example inputs, and it means a mistyped list tells you what is wrong instead of returning nothing.
Worth knowing if you are writing one importer for several of our supplier services. Here price and parsed_price held the same value with no currency symbol - unlike our Uline pages, where price carries a dollar sign and parsed_price does not. Read currency for the denomination rather than parsing it out of the string.
The names did not change, but their order did: our July run lists the columns starting name, brand, price, while the later runs start with the identifier and the product URL. Seventeen names either way. If your loader reads by position rather than by header, it will silently mis-map a Gemplers file - so read by name.
sku and sku_code held the same value on our row, the way they do on our Uline page and unlike our reseller catalogues, where one is the seller's number and the other the manufacturer's. The brand column carries the maker separately, so you still get both facts - just not two numbers.
Read from a real export, in sheet order. The notes come from our single successful run and from a direct fetch of the same listing, so where this says a column carried a value it is describing a row we actually hold.
sku on our row. The same number appears two dozen times in the live page's markup, so a row can be checked against the listing it came from.query and url on our row, because we submitted a product page rather than a collection.description is worth importing.price.currency rather than inferring the denomination from the string.USD on our row and confirmed by the offer record on the live page.rating. Plan around a supplier listing that carries specifications rather than consumer review furniture.sku_code on our row. Use either; keep both if you are writing one importer across several of our catalogue services, where they sometimes differ.product_url on our row.images on our row.ok on the real product URL, and unsupported URL (use a /collections/ or /products/ URL) on the two placeholder submissions. Read it first - it is the column that tells you your input was the wrong shape.Seventeen columns per row · CSV, JSON or Excel
Two practical notes and one piece of good news. The good news first: this is the fullest row we hold from any supplier catalogue on this schema. Fifteen of seventeen columns carried values, and a direct fetch of the same listing confirms every one of them - the page ships three structured-data blocks, one of which is a complete product record whose offer node states the same price, currency and stock status our export holds. Now the caveats. First, price arrives as a bare number here rather than a formatted string, so an importer that strips a currency symbol will strip nothing, and one that expects a symbol will not find it; read currency instead. Second, and easier to miss, the column order is not stable between exports. Our July run and our later runs list the same seventeen names in different sequences. Read by header name, never by position, or a Gemplers file will load cleanly into the wrong fields.
parsed_price is a bare number and currency tells you what it is denominated in, so a scheduled run over the items you buy produces a price series with no parsing step at all. Keep sku and the date beside it and a change announces itself.
The stock column arrived populated, which is not true of every supplier catalogue we cover. Pair it with a weekly schedule and you have a restock alert for the handful of parts whose absence actually stops work.
Name, brand, description and an image URL all came back on one row. That is enough to populate an internal catalogue entry without opening the page - and the description is real product copy rather than a duplicate of the title.
brand is its own column here rather than something to parse out of the title. Submit a collection page and you can see which makers a category is built from, and at what prices, without normalising a single string.
One time, on signup. No card, and nothing to cancel afterwards.
Billed on rows actually returned. A collection page can produce many rows where a product page produces one, so start with a few URLs and see what the shape of your list costs.
Credits do not expire on a monthly cycle. Check your supply prices at quarter end and nothing in between if that is the shape of the work.
LIVESCRAPER10 at checkout.One category URL returned 99 priced rows there. Worth reading beside this one: same schema, but the price carries a symbol and the brand column is empty.
Industrial supply on the identical columns - the obvious second source when you are checking a supply price against an alternative.
Another store built on the same commerce platform, where a collection URL fanned out into a row per size and colour.
A dated image of the listing beside the row, for when a price needs to be evidence rather than a number in a file.
List prices and item numbers on a public catalogue page are ordinary commercial facts. This is one of the calmer pages in our catalogue, and the caveats are correspondingly small.
A price, a product name and a catalogue number are facts about goods offered for sale. Reading them from a page served to any visitor is the same activity a buyer performs by hand, at a useful speed. Nothing in the seventeen columns describes a person: no name, no email address, no phone number, no account - so the data-protection questions that shape our people-facing services do not arise here. Prices are published openly on the listing rather than behind an account, which is why the money columns in this export arrive full.
Access was straightforward. The site's robots.txt answered a plain request with HTTP 200 on 12 August 2026, and read with a proper group matcher its general group carries 40 rules, no blanket exclusion, and both of the path shapes this service accepts - product pages and collection pages - are allowed. Nothing we ran was blocked, and the only non-successful rows in our export are the service politely rejecting a placeholder address that is neither shape. The one caution is ordinary rate: a collection page does more work per request than a product page, so schedule with that in mind rather than treating it as a free multiplier.
Our own terms are the same as on every other service here. Publicly available pages only, nothing behind a login, no third-party trackers on the data layer, and exports auto-delete after 30 days. Your first 500 rows are free and need no credit card.
unsupported URL (use a /collections/ or /products/ URL), and the vendor's own recorded example input for this service is two URLs, one of each shape.rating and reviews were empty. That is the fullest row we hold from any supplier catalogue on this schema.price and parsed_price held the same bare number on our row. That differs from some of our other supplier services, where price is the formatted string. Read currency for the denomination rather than parsing the price text.brand, so you still have both facts.Name, brand, price, currency, stock, description and images from one product URL - with every value confirmed against the live listing. Your first 500 rows are free, then $0.002 each.
Gemplers supplies agricultural, grounds and workwear equipment, and of all the supplier catalogues we cover on this seventeen-column schema it is the one that returned the most complete row. Our successful run submitted a single product URL and came back with fifteen of the seventeen columns populated: a full retail title, the manufacturer in its own brand column, the price both as a computable number and as the displayed value, a currency, a stock status, both identifier columns, a paragraph of genuine product copy, and an image address on the store's own host. Only rating and reviews were empty - which is what a supplier listing built around specifications rather than consumer reviews looks like.
We did not take that on trust. Fetching the same listing on 12 August 2026 returns roughly six hundred and twenty kilobytes of HTML carrying three structured-data blocks, one of which is a complete product record. Its offer node states the same currency, the same price and the same in-stock status that our export holds; the item number appears two dozen times in the markup and the manufacturer's name over a hundred. That makes this the best-corroborated row in the whole family of catalogue pages on this site - every value in it is visible on the page it came from, rather than inferred, rendered client-side or reconstructed from a neighbouring source.
Two things about the file are worth knowing before you write an importer. The price arrives as a bare number: both the price column and the parsed price column held the same value with no currency symbol, which is not the case on every service that shares this schema, so read the currency column for the denomination rather than stripping characters out of a string. And the column order is not stable between exports. Our July run lists the seventeen names in one sequence and our later runs list them in another - the names are identical, the positions are not. A loader that reads by position rather than by header will map a Gemplers file cleanly into the wrong fields, which is the kind of bug that produces plausible nonsense rather than an error.
The rest is unusually calm, and we would rather say so than manufacture drama. Nothing of ours was blocked. The site's robots.txt answered a plain request, carries no blanket exclusion for general crawlers, and permits both of the path shapes this service accepts. Those shapes are worth stating because the service itself states them: our two other runs submitted a placeholder address and came back not with a bare error but with a status reading that the URL was unsupported and that a collection or product URL should be used - the same two shapes the vendor's own recorded example input uses. Three runs is far too small a sample to quote a success rate from, and we quote none. Publicly available pages only, no third-party trackers on the data layer, exports auto-delete after 30 days, and your first 500 rows are free with no credit card.