Platform · Demae-can

Demae-can Data Scraping

Q: What will you do if that position changes?

Record platform_status_note in the deliverable and tell you if it changes materially — the same approach as the foodpanda page, which records the markets each batch actually observed rather than assuming a fixed list.

The domestic incumbent, with deeper nationwide reach than the international platforms — and a position worth knowing before you build a panel on it.

Demae-can data scraping collects restaurant menus, pricing and availability across Japan. It is the country's long-established domestic platform and the second-largest by share, with broader nationwide reach than the international operators — which makes it the more useful of the two outside the major metros, and the necessary second half of any Japanese competitive panel.

Most competitive panels need four or five platforms. In Japan, two gets you most of the market — and this is the one that reaches beyond Tokyo and Osaka.

Get a free sample See sample data

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

demaecan.jsonl LIVE FEED

{"restaurant_id":"dc-44120", "ward":"Example ward","coverage_tier":"beyond_metro", "item_name_ja":"as published", "item_price":880,"currency":"JPY", "min_realisable_price":980, "payment_methods":["card","cash_on_delivery"], "note":"beyond-metro coverage is the reason to include this platform"} {"coverage_tier":"metro", "also_on_other_platform":true, "note":"metro overlap is high. the value is in the rows above this one"} {"platform_status_note":"successive annual losses publicly reported", "prediction":"none_made", "caution":"a fact to weigh when scoping a long-horizon panel. not a forecast"}

3 of 2,884,220 restaurant-item rows · Japancoverage_tier recorded · platform note carried · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Demae-can or its owners. Demae-can 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

Demae-can at a glance

How we handle Demae-can specifically

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

Platform: Demae-can — Japan's long-established domestic service
Position: Second by share, and the wider nationwide footprint
Why that matters: International platforms concentrate in major metros
The record: A menu item, with modifier groups as anywhere
Addressing: Japanese address system. Same panel constraint as elsewhere in Japan
Text: Japanese retained as published
Worth knowing: Publicly reported successive annual losses. See below
Refresh: Daily standard; sub-daily where promotional intensity is the question

Platform specifics

Where Demae-can fits, and one thing worth stating

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

The nationwide reach is the reason to include it

Japanese food delivery is concentrated in Tokyo, Osaka, Yokohama and a handful of comparable metros. Below that tier, coverage differs between platforms.

The international platforms concentrate in the major metros, where density supports the economics.
Demae-can's footprint extends further, reflecting a longer-established domestic network.
So a metro-only panel understates what a national brand's delivery presence actually looks like.

For a restaurant chain, a food manufacturer or an investor looking at Japan beyond the big three cities, this is the platform that has the data. A panel built only on the international operator will be thin outside the metros and will read that thinness as absence.

Which shapes the scoping

We usually recommend Demae-can as the wider-coverage half of a two-platform Japanese panel, with the international platform providing metro depth. That is a different design from most markets, where platforms overlap heavily and the choice is about which four to take.

A financial position worth stating before you commission

This is not commentary on the business, and it is publicly reported rather than our assessment. But a client about to build a multi-year panel on a platform should know it.

Demae-can has publicly reported successive annual losses, and its share price has fallen very substantially from its pandemic-era peak. Reporting in 2026 described it as forecasting a further net loss for the financial year ending that August.

Why we are raising it

Earlier in this project we found live pages on this site selling collection from platforms that had shut down — Gorillas, Dunzo, Getir. The lesson was that a platform's continued existence is a fact worth checking rather than assuming.

We are not predicting anything here. Demae-can is operating, it holds substantial share, and it is the right platform for nationwide Japanese coverage today. We are saying that if you are scoping a long-horizon panel, this is a fact to weigh rather than discover.

What we will do about it

Record platform_status_note in the deliverable and tell you if the position changes materially, in the same way the foodpanda page records observed markets rather than assuming a fixed list.

Mechanics, and the Japanese constraints that apply here too

Menu structure

Modifier groups apply as on any delivery platform. Required selections make the headline item price not the entry price, so we deliver min_realisable_price with the basis recorded.

Addressing

The same constraint as everywhere in Japan: addresses are not street-based, so panels are built from address points with coordinates, and ward and district travel as labels rather than as the panel unit.

Payment

Cash on delivery remains a meaningful payment option on this platform, which is unusual among modern delivery services. Where payment methods are displayed we capture them, because payment availability is part of the offer in a market where it still matters to a share of customers.

What we never collect

Customer, courier or restaurant-staff data. Review counts and ratings only, never reviewer identity. Restaurant name is a commercial entity; individuals are not collected, in this market or any other.

Scope

What we collect on Demae-can, 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

Menu items with modifier groups and minimum realisable price
Nationwide coverage, including markets the international platforms thin out in
Address-point panels with ward and district as labels
Japanese names retained exactly, with no translation into the name field
Payment methods where displayed, since availability is part of the offer
Delivery and service fees as separate fields
Store open state distinct from an item being unavailable
platform_status_note in the deliverable
Review counts and ratings, without reviewer identity

❌ What we do not, and why

A metro-only panel presented as national coverage
Machine translation written into name fields
A prediction about the platform's commercial future
Sales, order volumes or restaurant revenue
Customer, courier, reviewer or staff data

Core Demae-can fields

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

Field	What it is on this platform
restaurant_id / restaurant_name / ward / district	A commercial entity, and where it is
address_id	Panel point with coordinates
item_id / item_name_ja	Retained exactly as published
item_price / currency	As displayed
modifier_groups / min_realisable_price / price_basis	The number a customer can actually pay
payment_methods	Where displayed. Part of the offer in this market
delivery_fee / service_fee	Each separately
store_open / item_available	Two distinct states
coverage_tier	Metro or beyond, so panel thinness is visible
platform_status_note	Where a material change is publicly reported
observed_at	Timestamp

Use cases

What teams do with Demae-can data

Nationwide Japanese coverage

The platform with reach beyond the major metros, so a national brand's delivery presence is measured rather than inferred from a metro-only panel that reads thinness as absence.

Two-platform competitive panel

Paired with the international operator for metro depth, which between them covers most of this market — a different design from the four-or-five-platform panels most countries need.

Menu pricing at realisable level

Modifier groups with minimum realisable price, so a comparison reflects what a customer pays rather than a headline that required selections will exceed.

Payment-method availability

Captured where displayed, since in this market payment options including cash on delivery remain part of the offer rather than an implementation detail.

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

Send us a Demae-can 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.

Demae-can is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Demae-can 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 Demae-can-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

Demae-can data scraping: frequently asked questions

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

Because its footprint extends further beyond the major metros, reflecting a longer-established domestic network. A panel built only on the international operator will be thin outside Tokyo, Osaka and Yokohama — and will read that thinness as absence.

For a national brand or an investor looking at Japan beyond the big three cities, this is the platform that has the data.

Because earlier in this project we found live pages on this site selling collection from platforms that had shut down. The lesson was that a platform's continued existence is worth checking rather than assuming.

Demae-can has publicly reported successive annual losses. We are not predicting anything — it is operating, holds substantial share and is the right choice for nationwide Japanese coverage today. If you are scoping a long-horizon panel, it is a fact to weigh rather than discover.

Record platform_status_note in the deliverable and tell you if it changes materially — the same approach as the foodpanda page, which records the markets each batch actually observed rather than assuming a fixed list.

From address points with coordinates, with ward and district carried as labels rather than used as the panel unit. Japanese addresses work by ward, district, block and building, and most streets have no name.

Same constraint applies to every Japanese source.

Because cash on delivery remains a meaningful option on this platform, which is unusual among modern delivery services. Payment availability is part of the offer in a market where it still matters to a share of customers.

We quote individually. The useful scoping question is coverage breadth rather than volume — the value here is reach beyond the metros, so a panel that stops at Tokyo and Osaka is buying the wrong half.

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

See real Demae-can 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