Platform · Shop Apotheke

Shop Apotheke Data Scraping

"Statt AVP" does not mean the shop used to charge that. It names a reference price from somewhere else.

Shop Apotheke data scraping covers product and price data from Germany's large online pharmacy, whose group has been called Redcare Pharmacy since 2023. OTC prices are shown against a crossed-out AVP or UVP — a reference price from the pharmacy price database or the manufacturer, not the shop's own previous price. So the reference is recorded with its label and basis, and a discount is never read as a price cut. No patient data, no prescriptions and no individual health information are collected, and reviews that disclose a condition are excluded.

Discount percentages in German pharmacy retail are measured against a benchmark. Knowing which benchmark is the whole question.

Get a free sample See sample data

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

shop_apotheke_sample.jsonl LIVE FEED

{"price":11.49,"reference_label":"AVP","reference_price_displayed":15.97} {"is_previous_price":false,"discount_displayed":"as stated"} {"our_price_change":-0.50,"derived_from_our_observations":true}

illustrative sample rows · DEwhich reference the discount is against · schema v1.0

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

Shop Apotheke at a glance

How we handle Shop Apotheke specifically

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

Pharmacy: Shop Apotheke — customer brand in Germany
Group: Redcare Pharmacy (renamed 2023)
Countries: DE, AT, FR, BE, IT, NL, CH — brands differ
Crossed-out price: AVP or UVP — a reference
So: reference_label and basis on every row
Not: The shop's own earlier price
Rx: Regulated in Germany; recorded for availability
Refresh: Daily for OTC

Platform specifics

Which reference the discount is against

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

AVP and UVP are references

The AVP (Apothekenverkaufspreis) is a reference retail price listed in the German pharmacy price database. The UVP is a manufacturer's recommended price. Online pharmacies show their own lower OTC price against one of these.

reference_label — AVP, UVP or other — recorded exactly as shown.
reference_price_displayed recorded as shown; never relabelled as a "was" price.
discount_displayed recorded as the shop states it; our own figure, if wanted, is derived and labelled.
Our observed price history is a separate series. A price cut is a change in the shop's own price, not a gap from a reference.

Brand, group and what we do not do

A brand is not the group

The group Shop Apotheke Europe renamed itself Redcare Pharmacy in 2023. The customer brand in Germany is still Shop Apotheke; other countries use other storefronts. market and storefront_brand are recorded, and each country is its own site.

Rx

German Rx prices are regulated, as our DocMorris page explains, so Rx is recorded for availability.

What we do not do

Relabel a reference as a previous price, compute discounts in place, submit prescriptions, or collect patient or health data.

Scope

What we collect on Shop Apotheke, 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

reference_label exactly as shown: AVP, UVP, other
reference_price_displayed as shown
discount_displayed as stated; ours derived and labelled
Our own price history as a separate series
market and storefront_brand on every row
rx_or_otc on every product
PZN recorded where displayed
Pack size and unit price as displayed
Daily OTC refresh

❌ What we do not, and why

A reference relabelled as a previous price
Discounts computed in place
Countries merged into one storefront
Prescriptions submitted or handled
Patient or health data

Core Shop Apotheke fields

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

Field	What it is on this platform
market / storefront_brand	Country and brand
product_id / pzn / name	As published
rx_or_otc	As classified
price / currency	As displayed
reference_label	AVP, UVP, other
reference_price_displayed	As shown
discount_displayed	As stated
our_price_change	From our own series, derived
pack_size / unit_price	As displayed
availability	As displayed
observed_at	Timestamp

Use cases

What teams do with Shop Apotheke data

German OTC pricing

Shop Apotheke prices as a daily series, reference kept apart.

Discount analysis done properly

Stated discounts against their reference, beside actual price changes.

European online pharmacy coverage

Each country's storefront as its own market.

Against DocMorris

The two large German online pharmacies on one schedule.

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

Send us a Shop Apotheke 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.

Shop Apotheke is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Shop Apotheke 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 healthcare & pharmacy data covers, and a Shop Apotheke-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

Shop Apotheke data scraping: frequently asked questions

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

It is a reference retail price from the German pharmacy price database, not the shop's own earlier price.

A manufacturer's recommended price. Also a reference, recorded with its label.

Yes, from our own observed series, which is separate from the reference.

Redcare Pharmacy is the group, renamed in 2023. Shop Apotheke is its customer brand in Germany.

Each country storefront, as its own market, on request.

It depends on OTC categories, countries and frequency.

Talk to us.

See real Shop Apotheke 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