MENY Scraper โ€” Danish Grocery Prices by Store avatar

MENY Scraper โ€” Danish Grocery Prices by Store

Pricing

from $2.00 / 1,000 results

Go to Apify Store
MENY Scraper โ€” Danish Grocery Prices by Store

MENY Scraper โ€” Danish Grocery Prices by Store

Scrape Danish grocery prices by store from MENY. Each shop prices its own shelves, so you choose the store and get the price a shopper actually pays there. The everyday price and the offer price stay separate fields. Most rows also carry an EAN and a unit price.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 hours ago

Last modified

Share

What does MENY Scraper do?

MENY Scraper collects Danish grocery prices by store for MENY (meny.dk). Each MENY shop prices its own shelves and runs its own storefront, so the actor takes a shop address and returns that store's everyday shelf price with the offer price as a separate field, plus EAN, unit price, pack size, category, store id and a link to the product page in that shop. Ingredients, allergens and a full nutrition table are available as an opt-in per product.

New to Apify? Sign up free and use the included $5 monthly platform credit to test this actor.

Key features

  • ๐Ÿช Prices for the store you pick, not a national average: MENY prices PER STORE, and the difference is not small: across three stores on one day, 78% of the products they share carried different prices. Give the shop address (storeUrl, e.g. https://parkvej.meny.dk) and every row carries that store's own shelf price plus storeId, storeName and a portalUrl link straight to the product page in that shop, so a price you show a shopper is the price they will actually pay at MENY Parkvej rather than an average of somewhere else.
  • ๐Ÿ’ฐ Shelf price and offer price, never merged: every row carries the store's everyday shelf price in price and, when the product is on offer, offerPrice beside it - never folded together, because a comparison needs both. Multi-buy offers are handled properly: this platform prices "2 for 35" as offerPrice 35 with offerQuantity 2, so a 500 g line at 21.95 normal would read as DEARER than normal if you took the offer figure at face value. offerUnitPrice carries the per-pack price (17.50) and offerComparePrice the per-kg figure, both divided by the quantity. 37.4% of live offers measured on one store were multi-buy.
  • โš–๏ธ Per-unit comparison pricing: comparePrice + compareUnit (kr/kg, kr/ltr, kr/stk) on every product โ€” the same number consumer-law requires on the shelf label. Apples-to-apples comparisons across pack sizes without writing your own normalizer.
  • ๐Ÿ”ข EAN / UPC barcodes: barcodes[] on every product โ€” match REMA SKUs to your existing inventory, ERP, or competitive-pricing dataset without name-based fuzzy joins. Multiple codes per SKU when the supplier ships variants under different barcodes.
  • ๐Ÿท๏ธ Structured unit size + brand: unitSize, unitMeasure, and brand parsed from the shelf-label string โ€” so "1 LTR. / REMA 1000" becomes 1 + ltr + REMA 1000 as separate fields. No regex on the subtitle. 14 unit tokens recognized across the full catalog (gr / ml / stk / cl / ltr / kg / par / mtr / pk / sรฆt / bakke / bdt / pose / rl) at 100% parse rate.
  • ๐Ÿ›’ Department-scoped scraping: restrict a run to one or more departments (frugt & grรธnt, frost, mejeri, drikkevarer, slik โ€ฆ) via departmentIds. Every product carries departmentId + departmentName so dashboards filter cleanly without keyword guessing.
  • ๐Ÿฅ— Ingredients + structured nutrition: every product row carries the full ingredients text (allergens already stripped of inline HTML markup) plus a structured nutrition[] array โ€” name/value pairs for energy, fat, saturated fat, carbs, sugars, fibre, protein, salt โ€” pulled straight from the compliance-grade source the chain itself publishes. No regex over marketing prose.
  • ๐Ÿ” Keyword search: search the catalog with query ("mรฆlk", "รธkologisk", "pasta", brand names โ€ฆ) โ€” matches across product names, descriptions, and category terms. Pair with Incremental Mode to monitor every product that matches a query, even as new SKUs enter the catalog.
  • โ™ป๏ธ Incremental mode: daily runs emit only products whose price, campaign flag, or validity window changed since the prior run โ€” the rest stay UNCHANGED and are filtered out by default. Perfect for price-tracking apps and tilbud-alert pipelines. Saves 80โ€“95% on recurring monitoring.
  • ๐Ÿ“ฆ Compact mode: drop the heavy fields (ingredients text, full nutrition table, image variants, manufacturer block, label objects, price history) and keep shopping essentials: identity, current price, per-unit price, campaign flags + discount %, parsed unit size + brand, and basket line totals. Cuts each row by ~77% โ€” ideal for AI agents, MCP servers, and LLM context windows where allergen text is noise.
  • ๐Ÿ”Œ MCP connectors: export your results into Notion via Apify's MCP connectors โ€” a clean run-summary page, no glue code. Opt-in via the App connector field; deterministic field-mapping, no AI. Built on Apify's connector framework, so more destinations open up as their catalog grows.

What data can you extract from meny.dk?

Each result includes Core product fields (listingId, searchQuery, contentQuality, scrapedAt, changeType, productId, ean, and name, and more) and detail fields when enrichment is enabled (detailFetched). In standard mode, all fields are always present โ€” unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Enable detail enrichment in the input to fetch each record's detail page โ€” extra fields the search results omit.

Input

The main inputs are a search keyword and a result limit. Additional filters and options are available in the input schema.

Key parameters:

  • storeUrl โ€” Address of the shop you want prices from, e.g. https://arden.spar.dk or https://parkvej.meny.dk. Prices differ from store to store, so this decides which store's shelf prices you get. Leave the numeric store id empty when you use this.
  • merchantId โ€” Which MENY store to read. Prices are set per store โ€” the same product is priced differently from one store to the next โ€” so there is no national MENY price and no safe default. 1011 is MENY Parkvej. Optional when you supply a store address above โ€” it is resolved for you.
  • query โ€” Only return products whose name contains this text (case-insensitive). Leave empty to get the store's entire assortment. Paste a JSON array such as ["kaffe","mรฆlk"] to match any of several terms.
  • categoryId โ€” Optional. Restrict the scan to one category of the store's category tree. Leave empty to scan every category.
  • maxResults โ€” Maximum number of products to return (0 = the whole assortment). (default: 50)
  • compact โ€” Core fields only (for AI-agent/MCP workflows). (default: false)
  • excludeEmptyFields โ€” Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards. (default: false)
  • incrementalMode โ€” Compare against the previous run and report what changed โ€” this is how you track price movements over time. stateKey is optional; it defaults to a value derived from the store, category and filter so different scans never share state. (default: false)
  • stateKey โ€” Optional. Stable identifier for the tracked product universe. Leave empty to auto-generate from the store, category and filter.
  • emitUnchanged โ€” When incremental, also emit products whose price and details are identical to the previous run. (default: false)
  • emitExpired โ€” When incremental, also emit products that were on the shelf in the previous run and have since disappeared. Forces a full scan of the assortment. (default: false)
  • telegramToken โ€” Telegram bot token (from @BotFather). Required for Telegram notifications.
  • ...and 15 more parameters

Input examples

Basic search โ€” Keyword-driven search with a result cap.

โ†’ Full payload per result โ€” all standard fields populated where the source provides them.

{
"query": "kaffe",
"maxResults": 50
}

Incremental tracking โ€” Only emit products that changed since the previous run with this stateKey.

โ†’ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
"query": "kaffe",
"maxResults": 200,
"incrementalMode": true,
"stateKey": "kaffe-tracker"
}

Compact output for AI agents โ€” Return only core fields for AI-agent and MCP workflows.

โ†’ Small payload with the most important fields โ€” ideal for piping into LLMs without token overhead.

{
"query": "kaffe",
"maxResults": 50,
"compact": true
}

Output

Each run produces a dataset of structured product records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example product record

{
"listingId": "f8d18909faf9645759b521ce87ac154f1037bb42ba961ffbed0e0808369ad40f",
"contentQuality": "full",
"detailFetched": true,
"scrapedAt": "2026-09-08T21:44:03.772Z",
"source": "meny.dk",
"contentHash": "2c5b46d2bb9656ed68353ceb155ad0f2c661360b23df019c09fa22f3b9719696",
"productId": 474592381,
"ean": "3387390339499",
"name": "Morgen Mad",
"price": 39.97,
"currency": "DKK",
"isOnOffer": true,
"offerPrice": 30,
"offerQuantity": 1,
"offerUnitPrice": 30,
"packSize": "375 _",
"unitSize": 375,
"brand": "Nowaste Logistics Ab (Nestle)",
"categoryId": 2,
"categoryName": "Morgenmad",
"categoryPath": "Kolonial > Morgenmad",
"chain": "meny",
"storeId": 1011,
"storeName": "MENY Parkvej",
"portalUrl": "https://parkvej.meny.dk/produkter/morgen-mad-3387390339499",
"inStock": true,
"ageRestricted": false,
"imageUrl": "https://dagrofa-dam.s3.eu-central-1.amazonaws.com/PROD/600x600/3387390339499.600x600.jpg",
"ingredients": "Ingredienser: FullkornsVETE/-HVEDE/-HVETE (61,9 %), ris (34,9 %), socker/sukker, fruktooligosackarider/fructooligosaccharider,\ninvertsockersirap/invertsukkersirup, maltextrakt (KORN/BYG/BYGG), solroso...",
"allergens": [
"Mรฆlk",
"Glutenholdigt korn",
"Nรธdder",
"Hvede (glutenholdigt korn)",
"Byg (glutenholdigt korn)"
],
"nutrition": [
{
"name": "Energi",
"quantity": "371 Kilokalorier"
},
{
"name": "Fedt",
"quantity": "2.1 Gram"
},
{
"name": "Heraf mรฆttede fedtsyrer",
"quantity": "0.6 Gram"
},
{
"name": "Kulhydrater",
"quantity": "73 Gram"
},
{
"name": "Heraf sukkerarter",
"quantity": "8.9 Gram"
},
"... 3 more items"
],
"producer": "Nowaste Logistics Ab (Nestle)",
"countryOfOrigin": "Frankrig",
"storageInstructions": "Opbevares tรธrt og kรธligt."
}

Incremental fields

When incremental mode is on, each record also carries:

  • changeType โ€” one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true or emitExpired: true to opt into the others.

How to scrape meny.dk

  1. Go to MENY Scraper in Apify Console.
  2. Enter a search keyword.
  3. Set maxResults to control how many results you need.
  4. Enable includeDetails if you need the extra detail-page fields.
  5. Click Start and wait for the run to finish.
  6. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Extract product data from meny.dk for market research and competitive analysis.
  • Track pricing trends across regions and categories over time.
  • Monitor new and changed products on scheduled runs without processing the full dataset every time.
  • Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
  • Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape meny.dk?

MENY Scraper uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.01 per run
  • Per result: $0.002 per product record

Example costs:

  • 10 results: $0.03
  • 25 results: $0.06
  • 100 results: $0.21
  • 200 results: $0.41
  • 500 results: $1.01

Platform usage is billed on top of these prices. The figures above are Apify event fees only. Compute units and proxy traffic are billed separately by Apify at your actual consumption, and for proxy- or browser-heavy workloads they can exceed the event fees. What you actually pay depends on your own input โ€” how many results you request, whether detail enrichment is on, the run memory you choose, and your proxy settings โ€” so it cannot be stated as a fixed figure here. Every run reports its exact platform usage on the run detail page.

The Actor Start event is charged once per GB of run memory (minimum one), so a run configured with 2 GB is charged two start events rather than one.

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of products that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency โ€” the scenarios below are examples, not predictions.

Example setup: 200 products per run, daily polling (30 runs/month). Costs scale linearly with the number of products.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% โ€” stable niche query$0.41$0.03$0.38 (93%)$0.90
15% โ€” moderate broad query$0.41$0.07$0.34 (83%)$2.10
30% โ€” high-volume aggregator$0.41$0.13$0.28 (68%)$3.90

Full re-scrape monthly cost at the same cadence: $12.30. First month with incremental costs $1.28 / $2.44 / $4.18 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage (see the note above) also applies to these figures. Incremental runs consume less of it on result processing, though the fixed per-run overhead stays the same.

FAQ

How many results can I get from meny.dk?

The number of results depends on the search query and available products on meny.dk. Use the maxResults parameter to control how many results are returned per run.

Does MENY Scraper support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed products on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate MENY Scraper with other apps?

Yes. MENY Scraper works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use MENY Scraper with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use MENY Scraper through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode, a single descriptionFormat, and excludeEmptyFields to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from meny.dk. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

Getting started with Apify

New to Apify? Create a free account with $5 credit โ€” no credit card required.

  1. Sign up โ€” $5 platform credit included
  2. Open this actor and configure your input
  3. Click Start โ€” export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Disclaimer

This actor accesses only publicly available data on meny.dk. You are responsible for how you use the extracted data โ€” in particular any personal information such as names, phone numbers, or email addresses โ€” and for complying with MENY's terms of use, applicable data-protection law (including the GDPR where it applies), and the anti-spam rules of your jurisdiction.

This actor is not affiliated with, endorsed by, or connected to MENY.

Search keywords

meny scraper, meny api, apify meny, meny data extraction, meny.dk scraper, meny.dk data, meny.dk api.