Platform · END.

END. Data Scraping

Limited launches go to a draw. A price shown on a launch page is real — and it is not a price you can simply pay.

END. data scraping collects menswear, streetwear and footwear listings, prices, availability and launch information. The mechanic that decides how the data is read: limited releases are allocated by draw rather than sold first-come. So a launch item's displayed price is a retail price for a chance, and its availability is not an in-stock state. Treating launch items like normal stock produces sell-out and availability figures that describe nothing.

Every other page in this hub treats listed and buyable as the same thing. For launch product here, they are not.

Get a free sample See sample data

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

end.jsonl LIVE FEED

{"retailer":"end","brand_name":"brand-a", "sale_mechanic":"draw","price":180.00, "draw_opens":"2026-09-18T08:00Z","draw_closes":"2026-09-20T08:00Z", "excluded_from_availability":true} {"sale_mechanic":"draw","resale_value":"not_estimated", "entry_count":"not_published", "note":"the price is real. nobody could simply pay it"} {"sale_mechanic":"standard","brand_style_code":"as published", "price":95.00,"size_availability":"per size, as normal stock"}

3 of 404,880 product rows · globala draw is not a sale · resale never inferred · schema v1.0

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

END. at a glance

How we handle END. specifically

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

Retailer: END. — UK-based, ships globally
Range: Menswear, streetwear, footwear
The mechanic: Limited launches sold by draw
So: sale_mechanic on every record
A draw price: Real, but not simply payable
Launch availability: Not an in-stock state
Resale value: Not inferred, ever
Refresh: Daily; launch calendar events tracked as they publish

Platform specifics

Draws, launches and ordinary stock

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

A draw is not a sale

For limited releases, customers enter a draw during a window, and winners are allocated the right to buy. The listing shows a price and a size run.

The price is a retail price, and it is real — winners pay it.
But nobody can simply pay it; access is by allocation.
Size availability on a draw listing describes what can be entered for, not what is in stock.
"Sold out" after a draw closes is the end of the draw, not a demand signal we can size.

So sale_mechanic is standard, draw or unstated on every record, with draw_opens and draw_closes where published. Draw items are excluded from availability and sell-through figures by default, and reported as their own launch series.

And resale value is never inferred

The gap between a draw price and the secondary market is widely discussed. We do not estimate it from this source, and we do not attach resale figures to launch records — that is a different source with its own handling, on our resale page.

Ordinary stock, brands and markets

Ordinary stock behaves normally

Outside launches, the range is a multi-brand stockist of menswear and streetwear. Style-code matching, markdown timing and size availability apply as on our John Lewis page.

Launch calendar

launch_announced_at, launch_date and sale_mechanic as published, retained after the launch passes — the launch history is a record of which brands allocate by draw and how often.

Markets

Prices are shown for the visitor's market. market_observed_from travels with every price, and draw eligibility can differ by market — recorded as published, not assumed.

What we do not collect

Draw entrant data, winners, entry counts (not published), customer data, or resale estimates.

Scope

What we collect on END., 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

sale_mechanic as standard, draw or unstated on every record
draw_opens and draw_closes where published
Draw items excluded from availability and sell-through by default
Launch history retained after each launch passes
Style-code matching for ordinary stock
Markdown timing on a shared schedule for ordinary stock
market_observed_from on every price
Draw eligibility by market as published
Size availability per size for standard items

❌ What we do not, and why

A draw item's size run treated as stock
A post-draw sell-out read as a demand signal
A resale value estimated or attached to a launch record
Draw entrant, winner or customer data
Entry counts, which are not published

Core END. fields

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

Field	What it is on this platform
retailer / market_observed_from	Where the price was seen from
brand_name / brand_style_code / colourway	Match keys
price / currency	Retail price, including on draws
sale_mechanic	standard, draw or unstated
draw_opens / draw_closes	Where published
launch_announced_at / launch_date	The launch calendar
draw_eligible_markets	As published
size_availability	Standard items only
excluded_from_availability	True on draw items by default
markdown_started_at / markdown_observed	Ordinary stock
observed_at	Timestamp

Use cases

What teams do with END. data

Launch calendar tracking

Launch announcements, dates and allocation method retained over time, showing which brands release by draw and how often.

Honest availability figures

Draw items excluded from availability and sell-through by default, so those figures describe ordinary stock.

Streetwear stockist parity

Ordinary multi-brand stock matched on style code, with markdown timing.

Market-level launch access

Draw eligibility by market as published, showing where a release could be entered.

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

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

END. is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. END. 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 fashion & apparel data covers, and a END.-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

END. data scraping: frequently asked questions

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

Because access is by allocation. The price is real — winners pay it — but nobody can simply pay it, and the size run shows what can be entered for rather than what is in stock.

Treating them like normal stock produces availability and sell-out figures that describe nothing.

No. Entry counts are not published and we do not estimate them.

Not from this source, and we do not attach resale estimates to launch records. The secondary market is a different source with its own handling.

Yes. Outside launches it is a multi-brand stockist, and style-code matching, markdown timing and size availability apply.

Draw eligibility can differ by market. We record it as published rather than assuming a launch was open everywhere.

We quote individually on categories and refresh. Launch tracking adds calendar monitoring, which is light; ordinary stock is priced like any stockist.

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

See real END. 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