Custom scraper

Ocado price data

We do not have a dedicated Ocado data API. What we do have is an AI scraper that reads an ocado.com page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.

  • ocado.com
Three stages of an Ocado run: paste an ocado.com URL billed from the render price of EUR 0.75 per 1,000 pages; declare columns such as product_title and brand; and the 11 columns it returns.

How to scrape Ocado

Ocado publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. Ocado carries more branded lines than any other UK grocer, which makes it the best single source for UK branded grocery pricing. The way to get the data is to read the page the way a customer sees it. Grocery is the category where the shelf price tells you least: the comparable number is the price per unit, and it is frequently printed in smaller type next to a pack size that changes.

Branded lines match on a barcode and settle the argument; own-label lines have to fall back to names and pictures. That split is what sets the ceiling on bebo.ee, our grocery comparison for Estonia: over 130,000 products tracked, 36,300 comparable across the 12 chains it follows.

How ocado.com is laid out

What a run needs to know about Ocado before you pick the URLs.

  • Product ID at the end of the URL

    Product pages follow /products/{name}-{id}, for example /products/ocado-british-tenderstem-broccoli-63028011. The trailing number is the key.

  • Unit price next to every price

    Every tile shows the unit price per kilo, litre or item, and an Ordinarily figure for the usual unit price. Capture both; they make pack-size changes visible.

  • Offers have an order-by date

    Offer lines read like Now £2 when you order by 08/09/2026, with a Previous price and a limit of 18 promotional items per customer. Store the end date with the price.

  • Ocado Price Promise

    Many lines carry an Ocado Price Promise badge. Record it as a flag; it tells you which items Ocado is pricing against other supermarkets.

  • Product life guarantee

    Fresh and some chilled items show a guaranteed minimum life, such as Life 2m+. It matters when comparing fresh prices across grocers.

What the AI scraper does with an ocado.com link

The same three steps as any other page you point it at. Nothing about Ocado is pre-built, which is exactly why it works on pages nobody wrote a connector for.

  1. Paste the link

    Give it an ocado.com product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.

  2. Declare the columns

    Name each field, give it a type and write a line telling the AI what to look for. “product_title” and “brand” are the two most people start with. The schema is yours and you can change it between runs.

  3. Schedule it and collect

    Run it daily, weekly or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.

Set it up once. The data keeps coming.

Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.

  1. Set it up once

    Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.

  2. Runs on your schedule

    Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.

  3. Saved in your database

    Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.

  4. Use it your way

    Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.

Ask your AI assistant about your own data

Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.

  • Which of my ASINs lost the Buy Box this week?
  • Which competitor cut prices the most since Monday?
  • Show the keywords where I dropped out of the top 10.

What you send and what you get

You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.

You give
  • Link to an Ocado pagerequired

    Open the product or category page in your browser and copy the address. Any Ocado country domain works the same way.

    https://www.ocado.com/
  • Your column listrequired
    product_title, brand, pack_size, price
  • How often it runsoptional
    Daily at 06:00 UTC
You get

One row per product on the page, 11 columns each

  • product_title
  • brand
  • pack_size
  • price
  • unit_price
  • unit
  • promo_price
  • currency
  • availability
  • product_url
  • checked_at

REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.

The columns an Ocado run comes back with

We are not going to print a table of invented grocery prices and call it real output. Ocado did not return a readable product page to an ordinary request, so we have no run of our own to quote from. So what is published here is the column list you declare before the run, which is the same list every run comes back with.

product_titleProduct title as the retailer writes it
brandBrand as the retailer labels it
pack_sizePack size as printed, which is what unit price is derived from
priceShelf price today
unit_pricePrice per litre, kilo or unit, where the page prints it
unitWhich unit that per-unit price is quoted in
promo_pricePromotional or multibuy price, where the page shows one
currencyCurrency the page quoted
availabilityWhether the line is in stock for the selected store
product_urlLink back to the page the row came from
checked_atWhen this run collected the page (UTC)

Every column here is one you name yourself in the schema. If a field is not on the page on the day of the run, it comes back empty rather than guessed.

What an Ocado page costs

Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count. The price shown is the starting price: €0.75 per 1,000 pages with a browser render. If a run also needs a residential proxy it costs €3.75 per 1,000 pages.

€0.75per 1,000 pagespay-as-you-go, no plan

Measured on 3 October 2026, not assumed. A plain request for an ocado.com page comes back HTTP 202 rather than a page, so the run goes through a browser.

Worked example

500 Ocado pages checked once a day for a month is 15,000 pages.

about EUR 11.25 for the month at the render price, about EUR 56.25 if the pages also need a residential proxy

You are charged for what a run actually used, not what it was expected to need, and your balance never expires.

See the full price list →

Typical fields the AI scraper extracts from an Ocado page

Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.

Unit price, not shelf price

The only grocery number that compares across brands. A 750 ml bottle at 4.50 and a 1 litre bottle at 5.40 is not a comparison until you divide.

  • Shelf price
  • Pack size exactly as printed
  • Price per litre, kilo or unit where the page prints it
  • Which unit the per-unit price is quoted in
  • Multibuy, loyalty or promotional price where shown

Promotion mechanics

Grocery promotions are rarely a simple percentage, and the mechanic is what moves volume.

  • Promotional price and the wording that explains it
  • Multibuy conditions, where the page states them
  • Loyalty-card price where the page shows one for members
  • Promotion end date, where printed
  • Any was-price

Product identity

Own-label lines have no manufacturer identifier at all, which is why the retailer's own code matters here.

  • Retailer's own product code
  • EAN or GTIN, where published
  • Brand, or own-label name
  • Category breadcrumb
  • Product image URLs

The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →

What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when Ocado publishes them.

What people use Ocado data for

01

Unit-price comparison across retailers

The only honest grocery price comparison. One schema with pack size and per-unit price across several retailers turns shelf prices into a table that actually compares.

02

Promotion calendar reconstruction

When a competitor starts a promotion on a line, how deep it goes and how long it runs. That calendar is public but only visible if you collect it daily.

03

Own-label versus brand price gap

The gap between a retailer's own label and the branded equivalent is a core grocery pricing input, and it moves. This is how you measure it rather than estimate it.

04

Availability and range checks

Whether your line is actually listed, in stock and findable at a given retailer. Suppliers usually discover delisting late; a daily check tells you in a day.

05

Price-index reporting

A fixed basket of lines, read daily, is a price index you own, rather than one you buy from a panel provider with a six-week lag.

What makes Ocado harder than an ordinary storefront

Here is what the scraper is actually up against on ocado.com, measured rather than assumed.

Access

  • Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
  • No named protection vendor on the response, which is why this one lands on a cheaper tier than most of the cohort
  • No usable sitemap directive in robots.txt, so the URL list comes from your own category pages

Pack size is the whole problem

  • Shelf price is not comparable across brands until it is divided by a pack size the page prints in small type
  • Pack sizes change without the product changing, which silently breaks a per-unit comparison built on a fixed assumption
  • Promotions are multibuys and loyalty prices rather than simple percentages, so the mechanic has to be captured as text
  • Grocery catalogues run to tens of thousands of lines, so scope the page count before switching a run on

What the page publishes

  • No product-level structured data is published, so every field is read off the rendered page
  • Unit price is published alongside the pack price, which is unusually helpful and worth capturing rather than deriving.
  • Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number

What to watch on ocado.com

The one thing specific to this site. The general limits — public pages only, no field the page does not show, your URLs rather than a full crawl — are in the custom scrapers FAQ.

  • Ocado has one specific trap

    Unit price is published alongside the pack price, which is unusually helpful and worth capturing rather than deriving.

FAQ

Ocado scraping — questions

What people ask before pointing the scraper at ocado.com.

Ocado publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.

Questions that apply to every site — scheduling, exports, what it will not do — are answered in the custom scrapers FAQ.

Ready to pull Ocado data into your stack?

Start free — or talk to our team about your exact fields, refresh cadence and volume.