Globus Scraper — German Grocery Hypermarket Products & Prices avatar

Globus Scraper — German Grocery Hypermarket Products & Prices

Pricing

from $1.20 / 1,000 result scrapeds

Go to Apify Store
Globus Scraper — German Grocery Hypermarket Products & Prices

Globus Scraper — German Grocery Hypermarket Products & Prices

Scrape products, prices, and stock status from globus.de -- Germany's Globus grocery hypermarket chain. Supports keyword search and category browsing.

Pricing

from $1.20 / 1,000 result scrapeds

Rating

0.0

(0)

Developer

Studio Amba

Studio Amba

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Globus Scraper

Scrape product data, prices, and stock status from globus.de -- Germany's Globus grocery hypermarket chain.

What is Globus Scraper?

Globus runs large-format grocery hypermarkets across Germany, known for a wide fresh-food range and weekly offer cycles. Their online catalog at produkte.globus.de exposes structured product data (JSON-LD) on every product page, which this scraper reads directly rather than scraping rendered text.

Here is how teams typically use this scraper:

  • Grocery price monitoring -- track price changes and weekly offers on specific products or full categories over time
  • Cross-chain price comparison -- benchmark Globus against other German grocery chains (Edeka, Kaufland, Rewe, Penny) or European grocers, product by product
  • Assortment tracking -- see which brands and products Globus carries in a given category, useful for manufacturers checking retail distribution
  • Stock and availability checks -- pull the current in-stock signal for products you care about
  • Weekly offer capture -- the default run (no input) pulls the current weekly-offers page, which changes every week

How to scrape Globus data

Search by keyword

{
"searchQuery": "kaffee",
"maxResults": 50
}

Keyword search uses the storefront's autocomplete endpoint, which returns up to about 10 matches per keyword. It's fast and precise for a specific product, but for larger volumes use categoryUrl instead. Popular German search terms: "milch" (milk), "kaffee" (coffee), "brot" (bread), "kaese" (cheese), "wein" (wine), "schokolade" (chocolate).

Scrape a category page

{
"categoryUrl": "https://produkte.globus.de/obst-gemuese/",
"maxResults": 500
}

Category pages paginate via ?p=N and the scraper follows pagination automatically until it has enough products or the category runs out. This is the higher-volume path -- use it for anything beyond a quick keyword check.

No input

Calling the actor with {} scrapes the current weekly-offers page (/angebote-der-woche/), so you always get a populated result without having to look up a category URL first.

Input reference

FieldTypeDescription
searchQueryStringGerman keyword to search for (default: "milch")
categoryUrlStringA produkte.globus.de category page URL to scrape
maxResultsIntegerMaximum number of products to return (default: 100, max: 50,000)
proxyConfigurationObjectProxy settings -- datacenter/automatic proxy works fine, no anti-bot on this storefront

If both searchQuery and categoryUrl are set, categoryUrl takes priority.

What data does Globus Scraper extract?

Each product result includes these fields when available on the page:

  • name -- product name/title
  • brand -- manufacturer or brand name
  • price -- current selling price
  • currency -- always EUR
  • pricePerUnit -- pack size and unit price, e.g. "9,29 € / 1 kg"
  • sku / ean -- GTIN/EAN barcode (this storefront uses the GTIN as its internal article code, so both fields carry the same value)
  • productId -- Shopware's internal product UUID
  • inStock -- true, false, or null when the page doesn't state availability (never guessed)
  • category / categories -- breadcrumb path, as a joined string and as an array
  • imageUrl -- primary product image
  • description -- product description text
  • language -- always "de"
  • url -- full product page URL
  • scrapedAt -- ISO 8601 timestamp of when the item was collected

Example output

{
"name": "Kaffee kräftig gemahlen",
"brand": "Globus",
"price": 4.99,
"currency": "EUR",
"pricePerUnit": "9,98 € / 1 kg",
"sku": "4306188414773",
"ean": "4306188414773",
"productId": "0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d",
"inStock": true,
"category": "Brot, Backwaren & Frühstück > Kaffee > Bohnenkaffee, gemahlen",
"categories": ["Brot, Backwaren & Frühstück", "Kaffee", "Bohnenkaffee, gemahlen"],
"imageUrl": "https://produkte.globus.de/media/...",
"description": "Kräftig geröstete Kaffeemischung, 500g",
"language": "de",
"url": "https://produkte.globus.de/brot-backwaren-fruehstueck/kaffee/bohnenkaffee-gemahlen/4306188414773/kaffee-kraeftig-gemahlen",
"scrapedAt": "2026-09-16T14:22:10.000Z"
}

Export to JSON, CSV, Excel, XML, or RSS directly from the Apify dataset.

How much does it cost?

The scraper uses plain HTTP requests (CheerioCrawler, no browser) against server-rendered pages, so per-result cost is low -- expect roughly $0.002-0.005 per result on top of your Apify platform usage.

ScenarioProductsEstimated cost
Quick keyword search20~$0.02
Single category200~$0.15
Multi-category export1,000~$0.70
Large catalog crawl5,000~$3.50

A run's usage cost only settles once it reports SUCCEEDED -- checking the cost while a run is still in progress will show a partial number, not the final one.

Can I integrate?

Connect Globus product data to your existing stack:

  • Webhooks -- trigger downstream processes when a run completes
  • Google Sheets -- auto-populate spreadsheets with product data
  • Slack / Microsoft Teams -- alert on price drops or stock changes
  • Zapier / Make (Integromat) -- route data to other apps without code
  • Amazon S3 / Google Cloud Storage -- dump results to cloud buckets
  • SQL databases -- push directly to PostgreSQL, MySQL, or BigQuery
  • REST API -- full programmatic access (see below)

Can I use it as an API?

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("studio-amba/globus-scraper").call(run_input={
"searchQuery": "kaffee",
"maxResults": 50,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(f"{item['name']} - EUR {item['price']}")

JavaScript

import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: "YOUR_API_TOKEN" });
const run = await client.actor("studio-amba/globus-scraper").call({
searchQuery: "kaffee",
maxResults: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach(item => console.log(`${item.name} - EUR ${item.price}`));

FAQ

Why Globus and not another German grocery chain? Globus is a regional hypermarket chain with a different product mix and pricing than national discounters. If you're already tracking Edeka, Kaufland, or Rewe, adding Globus fills in a gap those don't cover.

Does the search field find everything in a category? No. searchQuery uses the storefront's autocomplete, which returns roughly 10 matches per keyword -- good for checking a specific product exists and what it costs, not for a full category sweep. Use categoryUrl for volume.

What if I don't know a category URL? Browse produkte.globus.de, apply any filters you want, and copy the resulting URL into categoryUrl. The scraper follows the pagination on that URL as-is.

Is stock status reliable? inStock reflects what the page states (JSON-LD availability or a delivery status indicator). When the page doesn't say either way, the field is null rather than guessed as false.

Is the data in German? Yes -- product names, descriptions, and category breadcrumbs are exactly as published on globus.de, in German.

Limitations

  • Data is exclusively in German from produkte.globus.de
  • Full-text search on the storefront itself is not available upstream, so searchQuery is limited to the ~10 autocomplete matches per keyword
  • Store-specific pricing or local availability across individual Globus locations is not captured -- only the online catalog
  • Large category crawls (thousands of products) take proportionally longer since each product is visited on its own detail page

Other German grocery scrapers

Compare prices across the German grocery market with our scraper collection:

Maintained by Studio Amba

We run 700+ scrapers for European websites, and the priority is keeping every one of them working. Automated runs test this actor against the live site and verify the output is complete. When the website changes, the scraper usually gets repaired the same day, without you having to report anything. Questions and issues go straight to the people who built it, and most get an answer the same day.

Need this data on a schedule, or a custom version?

We run this scraper as a managed service for businesses: scheduled runs, deduplication, delta detection, and delivery to your inbox, Google Sheets, or API, maintenance included. We can also build a custom version with your exact fields and filters, or combine multiple sources into one feed.

See studioamba.dev/services or email hello@studioamba.dev for a free data sample.