Build a better catalog
Connect article numbers, materials and dimensions without losing the selected product variant.
All use casesIKEA
FURNITURE & HOME INTELLIGENCE
IKEA
product data.
Every article. In context.
Furniture specifications, prices and local availability. Structured around the markets and products that matter to you.
Track price changes
Compare published prices in the same market and currency, with a timestamp on every observation.
Understand availability
Keep online and store-level stock separate. A location is part of the record, not an afterthought.
FROM A PAGE TO A RECORD
Real furniture.
Useful data.
A dated snapshot of an IKEA Indonesia table lamp, extracted from its public HTML. Product identity, specifications and seven location quantities, without an AI call.
Research snapshot 09 Oct 2026
INDONESIA / IDRARTICLE / 303.213.73
ÅRSTID
Lampu meja, kuningan/putih
Rp 329.000Observed price, not a current quote- Article key
- 30321373
- Market / language
- Indonesia / Indonesian
- Currency
- IDR
- Source
- Product JSON-LD + page HTML
- AI processing
- None
Collected 09 Oct 2026 JSON-LD + HTML
Verified through 2Captcha Scraper API. Not a live feed or proof of all-market coverage.
THE DETAILS ARE THE DATA
Same product.
Different questions.
A catalog record is only useful when its meaning survives extraction. We keep the distinctions that matter to your analysis.
Product vs. package
A lamp can stand 55 cm tall and ship in a 23 cm-high box. Two fields, two units-aware contexts.
dimensions.height_cm / package.height_cmOnline vs. local stock
Store quantities describe a place and a moment. They do not guarantee delivery or reserve an item.
article_number + location_id + captured_atLocal price vs. global price
Rp329.000 is 329,000 Indonesian rupiah. Preserve currency and market before comparing products.
price.amount / price.currency / marketA LEANER COLLECTION PATH
One page can
answer a lot.
For the tested Indonesia page, identity and price were in Product JSON-LD; the same HTML contained specifications, stock and document links. No separate stock request was needed.
- 01 / COLLECT
Start with public HTML
Retrieve the selected product page. Check its identity and response before treating it as data.
- 02 / EXTRACT
Parse, then validate
Read structured data first, then enrich from tables and stock labels. Preserve missing values and source wording.
- 03 / DELIVER
Refresh what matters
Agree a cadence for prices and stock. Avoid repeatedly fetching static material descriptions and manuals.
What our access check established 09 Oct 2026
Two bounded 2Captcha Scraper API requests returned usable HTML and Markdown for the same Indonesia product page. The raw HTML supplied the product, price, specification tables, seven stock locations and five PDF links. The sample above was parsed from that HTML.
A direct public HTTP request also succeeded. No separate Browser API session, custom proxy or AI call was needed. Raw HTML is the preferred input here because it preserves JSON-LD and location IDs that a text representation can lose. The initial HTML task outlasted our first polling window, so this test does not establish a response-time guarantee.
This validates one product page, not a nationwide or global catalog. Wider coverage, sustained request rates and refresh cadence are checked against your project before commitment.
JSON / JSONL / CSV Scheduled snapshots
A maintained API or storage delivery can be scoped for your workflow.
TWO WAYS TO WORK WITH US
Page content, or
a maintained dataset?
Choose by responsibility and repeatability, not simply by the number of URLs.
Scraping API
Collect accessible public pages across many sites. Add AI when you need analysis, not just data.
- You handle extraction and scheduling.
- Useful for broad research and individual pages.
- No login or CAPTCHA bypass.
Managed IKEA data
A recurring product, price or stock feed shaped around your countries, locations and schema.
- Site-specific extraction and quality checks.
- Access requirements assessed per market.
- Source-change maintenance and agreed delivery.
Cost depends on usable records, locations, extra requests and refresh frequency. A custom workflow can reduce repeated work; it is not automatically cheaper in every case.
BEFORE YOU INTEGRATE
The questions
worth asking.
Market coverage, article identity and the meaning of a stock count.
Does the Indonesia sample prove coverage of every IKEA country?
No. This sample comes from ikea.co.id in Indonesian. IKEA markets can use different page structures, currencies, product ranges and availability systems. We validate each requested country and language before agreeing coverage.
Can I join products across countries using the article number?
An article number is a useful identifier, but a name alone is not a reliable join key. We preserve the original string, including leading zeros, and include market and selected variant. Cross-market matches are checked; a shared range name does not establish an identical product or price.
Is store stock the same as stock available for delivery?
No. A published store quantity, online stock and delivery to a postcode are different observations. The sample contains the locations published in that page response, not a delivery eligibility check or a reservation. We retain location IDs and timestamps, and assess postcode-specific requirements separately.
Will dimensions include packaging, assembly instructions and materials?
Where published, we separate assembled product dimensions from package dimensions and weights, with explicit units. Material descriptions retain their source wording. Document URLs, document type and language can be included; extracting the contents of each PDF is a separate step.
Do I need AI for the JSON output?
Not for fields already exposed as structured data or stable HTML. The observed sample was parsed deterministically from Product JSON-LD, specification tables and stock labels. AI can be added for translation, classification or comparison without silently rewriting the original observations.
What happens when a price or quantity is missing?
Unknown is not zero. We keep missing values null, distinguish unavailable data from a verified zero, and flag conflicting fields or unexpected pages. A successful HTTP response alone is not enough to treat a page as a valid product record.
Is this a ready-made IKEA endpoint in the Scraping API?
No. The self-service API collects accessible public page content; the IKEA-specific parsing shown here is a tested research extractor, not a deployed public catalog endpoint. For a maintained feed, we agree your schema, markets, volume and refresh schedule, then validate a representative sample before quoting.
YOUR CATALOG. YOUR REQUIREMENTS.
Start with a product.
Scope the whole picture.
Share a few IKEA URLs, the countries and stores you care about, and how often the data needs to change.
- Representative records before a rollout
- Coverage and gaps stated clearly
- A quote for the actual collection workflow
Projects are accepted individually, subject to feasibility and available capacity. An enquiry does not reserve a solution or confirm delivery. Pricing and terms are agreed directly with our team.
A real person reviews your requirements. This form does not start a paid collection.
ScrapingBuddy is independent and is not affiliated with or endorsed by IKEA. Collection feasibility and permitted use are reviewed per project. The interior photograph is illustrative; the data sample is a dated observation.