Meijer Product Price Scraper

Track Meijer prices, availability, and product data at scale

Need reliable Meijer grocery and retail price data without manually checking hundreds of products? This actor turns Meijer search terms and product URLs into clean, structured product rows with prices, stock status, UPC/SKU identifiers, product URLs, and images.

Use it to monitor competitors, build grocery price datasets, enrich product catalogs, compare market baskets by location, or power retail intelligence workflows.

Why use this actor?

Meijer product pages and search results can be difficult to scrape with a normal browser crawler. Automated sessions may hit edge protection or return Access Denied instead of product data.

This actor is built around that reality. For search terms, it uses Meijer's public product-search data path first, which is faster and more reliable than waiting for rendered search pages. Browser extraction remains available as a fallback for direct product and category URLs.

That means you get practical output instead of a scraper that looks good in theory and dies on the first real run.

What you can do with it

• Monitor Meijer prices for grocery, household, baby, pet, health, and personal-care products
• Compare product prices across a market basket
• Resolve ZIP codes/cities to nearby Meijer stores and attach store context
• Generate price, brand, availability, query, category, and location intelligence
• Track availability changes over time
• Build UPC/SKU-matched retail datasets
• Enrich internal catalogs with Meijer names, images, URLs, and pricing
• Research category assortment and brand coverage
• Feed dashboards, spreadsheets, BI tools, or pricing intelligence systems

What data do you get?

Each result is a normalized product row:

{
  "productName": "Meijer Whole Milk, Gallon",
  "price": 3.1,
  "salePrice": null,
  "regularPrice": null,
  "currency": "USD",
  "availability": "In stock",
  "brand": "Meijer",
  "size": "Gallon",
  "sku": "4125010200",
  "upc": "4125010200",
  "imageUrl": "https://www.meijer.com/content/dam/meijer/product/...jpg",
  "url": "https://www.meijer.com/shopping/product/meijer-whole-milk-gallon/4125010200.html",
  "sourceType": "listing",
  "storeContext": "49525",
  "extractionConfidence": "constructor-api",
  "searchQuery": "milk",
  "resolvedSearchQuery": "milk",
  "scrapedAt": "2026-05-13T16:00:00.000Z"
}

Key benefits

Built for price monitoring

Submit product keywords like milk, eggs, toothpaste, dog food, or paper towels and receive structured rows ready for tracking, comparison, and analysis.

Better reliability for search inputs

Keyword searches use Meijer's public search data path instead of relying only on browser-rendered pages, reducing failures from blocked search pages.

Location-aware outputs

Pass ZIP codes or city/state searches and the actor resolves nearby Meijer stores, then attaches store ID, store name, address, city, state, ZIP, distance, and market key to product rows.

Built-in analytics intelligence

Every run can generate a SUMMARY record with totals, cheapest and most expensive products, average prices, query-level stats, location-level stats, availability counts, brand counts, and category signals.

Clean product identifiers

The actor captures UPC/SKU-style identifiers when available, making it much easier to join Meijer products against your own catalog or external datasets.

Ready for business workflows

Output includes product name, price, availability, brand, size, image, URL, source query, and scrape timestamp. No messy DOM cleanup required.

Handles overlapping inputs

If multiple search terms return the same product, the actor deduplicates rows so your dataset stays cleaner.

Browser fallback included

For direct product URLs and some category/listing pages, the actor can still use Playwright browser extraction when useful.

Input examples

Search by keywords

Best for broad price monitoring and category research.

{
  "queries": ["milk", "eggs", "bread", "toothpaste", "paper towels"],
  "locations": ["49525", "Detroit, MI"],
  "maxStoresPerLocation": 1,
  "maxItems": 100,
  "includeAnalytics": true,
  "includeProductDetails": false
}

Scrape Meijer URLs

Use this when you already have product or search URLs.

{
  "startUrls": [
    { "url": "https://www.meijer.com/shopping/search.html?text=coffee" },
    { "url": "https://www.meijer.com/shopping/product/meijer-whole-milk-gallon/4125010200.html" }
  ],
  "maxItems": 50,
  "includeProductDetails": true
}

Larger market-basket run

{
  "queries": [
    "milk", "eggs", "bread", "butter", "cheese",
    "chicken", "ground beef", "bananas", "paper towels", "toothpaste"
  ],
  "maxItems": 250,
  "maxPages": 50,
  "includeProductDetails": false,
  "proxyConfiguration": { "useApifyProxy": true }
}

Input fields

Field	Type	Best for
queries	array of strings	Fast, reliable product search by keyword. Recommended for most runs.
startUrls	array	Meijer search, category, or product URLs.
locations	array of strings	Optional ZIP codes or city/state queries. Resolves nearby Meijer stores and adds store context.
locationRadiusMiles	integer	Store search radius. Default: 50.
maxStoresPerLocation	integer	Nearby stores to include per location query. Default: 1.
includeAnalytics	boolean	Adds per-row price intelligence and writes a run-level SUMMARY. Default: true.
maxItems	integer	Total product rows to save. Default: 100. Max: 5000.
maxPages	integer	Browser fallback safety limit. Default: 50.
zipCode	string	Optional store-area label saved as storeContext.
includeProductDetails	boolean	Open product detail pages for richer extraction when using URL crawling.
proxyConfiguration	object	Optional Apify proxy settings for browser fallback pages.

Output fields

Field	Meaning
productName	Product title from Meijer.
price	Current detected product price.
salePrice	Sale price when separately available.
regularPrice	Regular/list price when separately available.
currency	Usually USD.
availability	Normalized stock status, e.g. In stock or Out of stock.
brand	Product brand when available.
size	Parsed size or pack description when available.
sku	Meijer product identifier when available.
upc	UPC/EAN-style identifier when available.
imageUrl	Product image URL.
url	Product page URL.
sourceType	listing or product.
storeContext	ZIP/store label from input, if provided.
locationQuery	Original location query, such as a ZIP code or city/state.
storeId	Resolved Meijer store ID when available.
storeName	Resolved store display name.
storeAddress, storeCity, storeState, storeZip	Resolved store address fields.
storeDistanceMiles	Distance from the location query when available.
marketKey	Store/location grouping key used for analytics.
priceRankForQueryLocation	Rank within the same query + location group.
priceDeltaFromQueryLocationAvg	Difference from the average price for the same query + location group.
isLowestPriceForQueryLocation	Whether this is the cheapest row in its query + location group.
isHighestPriceForQueryLocation	Whether this is the most expensive row in its query + location group.
priceBucket	Price band such as under_2, 2_to_5, 5_to_10, 10_to_25, or 25_plus.
extractionConfidence	Extraction source, such as constructor-api or json-ld.
searchQuery	Original keyword that produced the product.
resolvedSearchQuery	Actual fallback query used, if different.
scrapedAt	Timestamp for the extracted row.

Reliability proof

This actor was tested against a 50-input Meijer search set across grocery, household, pet, baby, health, and personal-care categories.

Validation result:

• 50 / 50 search inputs succeeded
• 250 product rows extracted
• 250 / 250 rows had price, product name, URL, and availability

Tested terms included milk, eggs, bread, coffee, chicken, ground beef, bananas, paper towels, toothpaste, diapers, vitamins, tylenol, and trash bags.

Recommended settings

For most use cases:

{
  "queries": ["milk", "eggs", "bread"],
  "maxItems": 100,
  "includeProductDetails": false
}

Use includeProductDetails: true when you specifically need richer metadata from product pages and are comfortable with slower browser-based crawling.

Analytics summary

When includeAnalytics is enabled, the actor writes a SUMMARY record to the default key-value store. It includes:

• run totals and coverage
• products with price and availability
• unique UPC and brand counts
• cheapest and most expensive products
• query-level price intelligence
• location/store-level price intelligence
• brand frequency
• availability counts
• category signals
• warnings from partial failures

Important notes

• Meijer prices and availability can vary by store, fulfillment method, account state, and time.
• zipCode is recorded as context, but exact store-specific pricing should be verified for high-stakes decisions.
• Direct browser extraction can still be blocked by Meijer's edge protection if proxies are not suitable.
• The actor does not log in, add products to cart, or access account-specific offers.

FAQ

Does this actor require a Meijer account?

No. It extracts publicly available product data.

Is this better for search terms or product URLs?

Search terms are the strongest path. They are faster and more reliable because they use Meijer's public product-search data path. Product URLs are supported through browser/page extraction.

Can I run many keywords at once?

Yes. The actor was validated against 50 search inputs in one run.

What happens if a query returns duplicate products?

Duplicates are removed using product URL, SKU/UPC, name, and price signals.

What if one query returns fewer results than expected?

The actor performs a deeper fill pass to use remaining maxItems capacity where possible.

Local development

npm install
npm test
npm start

For local runs, put your input in storage/key_value_stores/default/INPUT.json or run through Apify tooling.