Pingo Doce Portugal Prices Scraper

Extract current product prices from Pingo Doce's Portuguese online catalog. Search by keyword, filter by a free-text brand, or leave both filters empty to collect the complete public catalog.

It reads actual prices displayed in Pingo Doce's public online catalog rather than promotional leaflets. Results include product identity, brand, package size, regular and promotional prices, unit price, currency, image, and product URL.

Why use this Pingo Doce price scraper?

This Actor converts Pingo Doce's public product cards and promotion labels into a consistent dataset that can feed:

• price comparison apps and consumer tools;
• retail and competitor price monitoring;
• brand distribution and assortment research;
• promotion analysis;
• procurement and category-management workflows;
• recurring price-history datasets;
• data pipelines, dashboards, and spreadsheets.

Use the combined Portugal Supermarket Prices Actor when one run must cover several retailers.

How does the Pingo Doce price scraper work?

1. Optionally enter a product keyword, a brand, or both.
2. Run the Actor.
3. Download the dataset as JSON, CSV, Excel, XML, or another Apify-supported format.

flowchart LR
    A[Filters] --> B[Pingo Doce catalog] --> C[Price dataset]

When Keyword and Brand are both empty, the Actor follows Pingo Doce's public catalog pagination until the available online catalog is exhausted.

The Actor reads public online catalog pages without requiring a customer login, delivery address, or postal-code input.

What input does the Actor accept?

Field	Type	Description
keyword	string	Optional product search such as leite, café, arroz, cerveja, or detergente.
brand	string	Optional free-text brand filter such as Mimosa, Delta, Compal, or Fairy.
proxyConfiguration	object	Optional Apify Proxy configuration for access problems.
datasetId	string	Optional existing Apify dataset that receives a second copy of every result.
runId	string	Optional workflow or external job identifier copied to every result.

Brand is deliberately free text rather than a dropdown. Retailer brand lists change frequently and are too large to keep as a trustworthy static input.

Filtered search

{
  "keyword": "leite",
  "brand": "Mimosa",
  "runId": "weekly-milk-prices"
}

Complete catalog

{}

What Pingo Doce price data does the Actor return?

Each dataset row represents one supermarket product and its currently displayed price.

{
  "supermarket": "Pingo Doce",
  "productId": "48150",
  "productName": "Leite UHT Meio Gordo",
  "brand": "Pingo Doce",
  "category": "Leite e Bebidas Vegetais / Leite Meio Gordo e Gordo",
  "packageSize": "1 L",
  "price": 0.86,
  "discountPrice": 0.83,
  "unitPrice": "0,83 €/L",
  "currency": "EUR",
  "url": "https://www.pingodoce.pt/...",
  "imageUrl": "https://www.pingodoce.pt/...",
  "runId": "weekly-milk-prices"
}

Output fields

Field	Meaning
supermarket	Retailer whose online catalog displayed the product.
productId	Stable retailer identifier for matching the same item across repeated exports.
productName	Displayed product name.
brand	Displayed brand when available.
category	Displayed catalog category when available.
packageSize	Displayed package quantity, weight, or volume.
price	Regular displayed price. When there is no promotion, this is the current price.
discountPrice	Lower current promotional price, included only when the retailer explicitly displays a promotion.
unitPrice	Displayed comparison price per liter, kilogram, or unit.
currency	EUR.
url	Direct public product page URL.
imageUrl	Displayed product image URL when available.
runId	Optional identifier copied from the input.

The absence of discountPrice means that the Actor did not find a genuine lower promotional price on that product card. It does not mean the product has never been promoted.

How are regular and promotional prices represented?

Price interpretation follows the retailer's public product card:

• A product without an explicit promotion has one price in the price field.
• A promoted product keeps the crossed-out or stated reference price in price and places the lower current amount in discountPrice.
• Unit price remains the retailer's displayed text because units and locale formatting vary.
• The Actor does not calculate historical changes.
• The Actor does not label ordinary prices as discounts.
• Shipping, basket discounts, loyalty-only benefits, coupons, and checkout-specific adjustments are not included unless they are already displayed on the public product card.

How does brand filtering work?

The Actor sends the keyword and brand to the retailer search where possible and then validates the displayed brand in the parsed results. Brand matching is case-insensitive and accent-insensitive.

A retailer can omit a structured brand or use a different spelling. For maximum recall, search by Keyword without Brand and filter the larger dataset downstream.

How do I run the Actor through the Apify API?

Run the Actor through the Apify API:

curl -X POST \
  "https://api.apify.com/v2/acts/trovevault~pingo-doce-portugal-prices/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "café",
    "brand": "Delta"
  }'

After the run finishes, read its default dataset through the Apify API or export it in the Console. Keep API tokens in server-side secret storage, not browser code or public repositories.

How can I integrate Pingo Doce prices into a pipeline?

Use datasetId to append results to a longer-lived Apify dataset while still receiving the normal dataset for each run. Use runId to associate rows with a workflow, snapshot, client, or scheduled job.

For recurring price history, schedule the Actor and retain each run or append to a dedicated dataset. Product ID is the practical matching key for repeated Pingo Doce exports.

How reliable is the Pingo Doce price scraper?

Request failures are retried. If the public catalog remains unreadable, the run fails with a sanitized message and records details in RUN_SUMMARY.

Retailer websites can change markup, catalog rules, promotion labels, rate limits, and default online-store context. A successful run means the public pages were readable at that time; it does not guarantee physical-store inventory or checkout availability.

Start without a proxy. If a retailer repeatedly blocks Apify cloud traffic, enable a suitable proxy configuration. Proxy usage can increase run cost.

What are the current limitations?

• Prices come from the retailer's public Portuguese online catalog, not every physical branch.
• The Actor intentionally has no postal-code input and does not claim store-level local prices.
• Product availability can change between collection and checkout.
• Some loyalty, coupon, app-only, multibuy, or basket promotions may not appear as a simple product discount.
• Category, brand, size, unit price, or image can be absent when the retailer does not expose them consistently.
• Full-catalog runs depend on the products exposed through public pagination at run time.

How do I troubleshoot a Pingo Doce price run?

A brand search returns fewer products than expected

Try the brand name as Keyword and leave Brand empty. This broadens recall when a retailer omits the structured brand value.

A complete catalog run takes a long time

This is expected because the Actor follows every available page. Add a Keyword or Brand for a smaller recurring workflow.

The run has no results

Check RUN_SUMMARY and verify the same search on Pingo Doce's public site. Enable a proxy only after direct requests repeatedly fail.

A product has no discountPrice

The public card did not expose a lower promotional amount. The regular/current price remains in price.

How should I use the Actor responsibly?

Use this Actor in accordance with applicable law, retailer terms, and Apify policies. Choose reasonable schedules, avoid unnecessary full-catalog runs, and process only data you are entitled to collect.