The Iconic Scraper for Product, Price and Size Data

The Iconic Product Fields We Extract

Behind the rendered page each The Iconic product carries a structured record, and inside it a row for every purchasable size. That is what we extract, mapped to named columns rather than left in one description blob:

• Product id from the URL and the config SKU, such as AT049AA35MZ, as two columns
• Name, brand and brand id, gender, department and the full category path
• brand_type, the field that separates private label from branded, agency consignment and drop shipment ranges
• supplier, the company that actually holds and ships the item, plus the shipment type code
• Colour name with its hex value, and the count of other colourways of the style
• price, markdown_price, special_price and final_price, with the original and final display strings
• is_on_sale, final_sale, is_multipriced, and the minimum and maximum of the price range
• price_reason, which names price_matched or comp_price when a cut has a stated cause
• Marketing badges with their wording and colour, including sizes-on-sale counts
• One row per size with its own simple SKU, its own price, special price and GST percentage
• Size as printed, the bare size code, and the size system split into original and universal
• stock_status per size, reading in-stock, low-in-stock or one-left
• is_marketplace_stock, is_fbi_stock and is_sold_by_partner, set per size and not per product
• Dispatch time, instalment count and instalment price for each size
• composition_material, care_label, fabric_material and the measurements note
• Wishlist count from the listing tile, and the timestamp the product was activated
• Gallery, fullscreen and thumbnail image URLs, plus the SKUs styled into the same shot
• returnable, hazmat type and any country exclusions on the product

Prices come through as numbers with the currency in its own column, so an Australian row and a New Zealand row stay comparable rather than collapsing into formatted strings. The measurements note earns a field of its own: garment length quoted against a named Australian size, plus the model's height, bust, waist and hips. Size data can be nested one row per product or flattened to one row per size, the shape you want when the question is which sizes sold out first.

Two Storefronts, Four Brand Types, One Product Record

Two storefronts, one product record, and the difference lands where a naive parse misses it. The Australian page and the New Zealand page carry the same product id, the same config SKU and the same per-size SKUs, but the shelf figure differs: a Dr Denim hoodie listed at 130.00 in Australia rings up as A$135.91 across the Tasman. The product markup on the New Zealand page still reports the Australian figure and AUD as its currency, so anything reading only that markup will file New Zealand rows at Australian prices. Assortment differs too - the same dresses category currently shows about a thousand fewer items on the New Zealand shelf.

Who sets the price is itself a published field. The Iconic buys and prices wholesale ranges, runs private labels of its own such as AERE, Atmos&Here and Dazie, takes agency consignment stock, and hosts marketplace sellers on dropship or fulfilled-by-Iconic terms. A single product can mix them: a marketplace size row can be grafted onto a listing under a different config SKU and carry its own price. On own-label lines there is no competitor listing to compare against, which is exactly why assortment depth and markdown history are the only read available on them.

Some things are absent and should not be promised. There is no published product API. Reviews render through a third-party widget and carry shopper names, so we leave them out by default; no customer accounts, no order data, no personal data of any kind. The shelf figure is also not the figure paid - basket thresholds and a points programme sit on top of it - and we deliver the shelf price, labelled as such.