Platform · PedidosYa

PedidosYa Data Scraping

Q: How do you handle the platform's changing footprint?

We record markets_observed per batch rather than working from a fixed list, so a withdrawal or entry appears as a structural change rather than as a silent coverage shift.

Several of these currencies move within the day. An FX rate applied at day's end describes a different price from the one displayed.

PedidosYa data scraping collects restaurant menus, pricing, fees and availability across Latin American markets. The handling that matters most: in several of these markets currency moves materially within a single day, so FX is stamped at the moment of observation rather than applied at a daily rate — and no inflation adjustment is applied inside the feed.

The same argument our Rappi Turbo page makes about LatAm quick commerce, applied to restaurant delivery across a wider set of markets.

Get a free sample See sample data

Free pilot on your own PedidosYa list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

pedidosya.jsonl LIVE FEED

{"platform":"pedidosya","country":"AR", "merchant_id":"py-44120","city":"Example city", "item_name_local":"as published, Spanish", "item_price":8400,"currency_local":"ARS", "fx_rate":0.00088,"fx_observed_at":"2026-08-25T14:22-03:00", "fx_source":"named in the deliverable"} {"fx_observed_at":"2026-08-25T19:40-03:00", "fx_rate":0.00085, "note":"same day, 5h later, 3.4% different. a daily closing rate describes neither"} {"inflation_adjustment":"not_applied", "payment_condition_text":"as published", "effective_price":"not_computed"}

3 of 2,604,880 merchant-item rows · LatAmFX stamped per observation · no inflation adjustment · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to PedidosYa or its owners. PedidosYa and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

PedidosYa at a glance

How we handle PedidosYa specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Platform: PedidosYa — Latin American markets
Currency: Moves within the day in several markets
So: FX stamped per observation, not daily
Inflation: No adjustment applied. Index choice is yours
Countries: Several, priced independently. country is a dimension
Language: Spanish and Portuguese. Names retained, not translated
Price setter: Merchant, as on any marketplace
Refresh: Daily standard; sub-daily where currency movement matters

Platform specifics

Currency, inflation and several markets

These are the reasons a PedidosYa dataset needs its own handling rather than a shared retail schema.

FX at the observation, not at the end of the day

In several Latin American markets the exchange rate moves materially within a single trading day. A converted price series built on a daily closing rate is therefore describing a conversion that did not apply when the price was displayed.

We stamp fx_rate and fx_observed_at at the moment of collection.
Local currency is always retained as the primary figure.
Converted values are derived, clearly labelled, and recomputable from the record.
Which rate source is recorded, since sources differ in these markets.

That last point matters more here than elsewhere. In markets with parallel or multiple official rates, the choice of rate source is an analytical decision, and embedding ours silently would put a judgement into a price column.

Inflation

We apply no inflation adjustment. A price series in a high-inflation market shows movement that is partly monetary, and the choice of index and base period is yours.

We deliver unadjusted local-currency figures with precise timestamps so any adjustment you make rests on an assumption you can state — the same position as our Rappi Turbo page.

Several countries, and they are not one market

The platform operates across Latin American markets that differ substantially in price level, currency regime, merchant mix and competitive structure.

country is a dimension on every record.
A regional average is a computed rollup, not a primary figure.
Currency regimes differ, so some markets need sub-daily collection and others do not.
Competitive position differs by country, so the platform's share in one says little about another.

Languages

Spanish across most markets and Portuguese in Brazil, with regional vocabulary differences within Spanish that matter for menu items. Names retained exactly, translation additive and dated, matching on structure rather than titles.

Standard marketplace mechanics

Merchant sets the price, modifier groups make the headline not the entry price, fees separate, availability address-level. As our Uber Eats page sets out.

Payment mechanics, and what we do not collect

Payment-linked discounts

Discounts tied to a payment method or wallet are common across these markets. As on our iFood page, those are conditions rather than prices.

We capture payment_condition_text as published and do not compute an effective price from it — whether a customer uses that method is not observable.

Market presence

Platform footprints in this region change. We record markets_observed per batch rather than working from a fixed list, so a withdrawal or an entry appears as a structural change rather than as a silent coverage shift — the discipline our foodpanda page established.

What we do not collect

An inflation-adjusted series. Index choice is yours.
An effective price from a payment condition.
Order volumes, merchant revenue or take rate.
Courier, customer or reviewer identity.

Scope

What we collect on PedidosYa, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

fx_rate and fx_observed_at stamped at the moment of collection
fx_source recorded, since sources differ in these markets
Local currency retained as the primary figure
No inflation adjustment applied inside the feed
country as a dimension, with regional figures as rollups
markets_observed recorded per batch, never assumed
payment_condition_text as published, with no effective price computed
Names retained in Spanish and Portuguese, translation additive
Modifier groups with minimum realisable price

❌ What we do not, and why

A daily FX rate applied to intraday observations
An inflation adjustment applied inside the feed
An effective price computed from a payment condition
A regional average presented as a price
Order volumes, revenue, courier, customer or reviewer data

Core PedidosYa fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
platform / country / markets_observed	Which market, and what the batch saw
merchant_id / merchant_name / city	A commercial entity, and where
item_name_local / language_detected	Retained exactly, with the language
item_price / currency_local	The primary figure
fx_rate / fx_observed_at / fx_source	Stamped, and which source
price_converted / conversion_basis	Derived and labelled
payment_condition_text	As published. Not a price
modifier_groups / min_realisable_price	The number a customer can pay
delivery_fee / service_fee	Each separately
address_id / serviceable	Availability is address-level
observed_at	Precise, with local offset

Use cases

What teams do with PedidosYa data

LatAm menu pricing with honest conversion

FX stamped at the observation with the source recorded, in markets where the rate moves within the day and where the choice of rate source is itself an analytical decision.

Multi-country competitive panel

Country as a dimension across markets that differ in price level, currency regime and competitive structure, with regional figures only as computed rollups.

Market presence monitoring

markets_observed per batch, so an entry or withdrawal appears as a structural change rather than as a silent coverage shift.

Menu pricing at realisable level

Modifier groups with minimum realisable price, so merchants listing identically are not treated as equivalent.

The 24-hour sample — run on your sources, not ours

Send us a PedidosYa item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

PedidosYa is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. PedidosYa data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what food & restaurant data covers, and a PedidosYa-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

PedidosYa data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Because in several of these markets the rate moves materially within a single trading day. A converted series built on a daily closing rate describes a conversion that did not apply when the price was displayed.

We stamp the rate and its timestamp at collection, retain local currency as the primary figure, and record which rate source was used.

Because in markets with parallel or multiple official rates, the choice of source is an analytical decision rather than a technical one.

Embedding ours silently would put a judgement into a price column. We record it so you can see and change it.

No. A price series in a high-inflation market shows movement that is partly monetary, and the choice of index and base period is yours.

We deliver unadjusted local-currency figures with precise timestamps so any adjustment rests on an assumption you can state.

No. A payment-linked discount is a condition rather than a price — whether a customer uses that method is not observable.

We capture the condition text as published and leave effective price to an assumption you can state.

We record markets_observed per batch rather than working from a fixed list, so a withdrawal or entry appears as a structural change rather than as a silent coverage shift.

We quote individually. Country count is the main driver, and markets needing sub-daily collection for currency reasons cost more than those that do not.

One scoping call, a free pilot within 24 hours, then a fixed monthly quote. Request a quote.

See real PedidosYa data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner