Platform · H-E-B

H-E-B Data Scraping

One company, three price positions. Pool the banners and the average describes none of them.

H-E-B data scraping collects pricing, promotions and availability across this Texas grocer's banners. The structural point: the company operates separate banners at distinctly different price positions — a premium format, the core banner, and value formats — so a company-level price figure averages three deliberate strategies rather than describing a market.

Most multi-banner grocers run banners that compete in different places. This one runs banners that compete at different price points in the same places.

Get a free sample See sample data

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

heb_2026-08-25.jsonl LIVE FEED

{"retailer":"heb","banner":"banner-core", "banner_price_position":"core","store_id":"st-4412", "price":4.29,"currency":"USD", "is_own_label":true,"own_label_tier":"standard"} {"banner":"banner-premium","banner_price_position":"premium", "price":6.99,"cross_banner_gap_pct":62.9, "note":"same metro. this gap is the company spacing its OWN formats"} {"own_label_share_category":0.58, "matchable_share_category":0.34, "region_coverage_note":"Texas and adjacent. NOT a US figure", "caution":"own label is 58% of shelf. a branded-only index covers a minority of sales"}

3 of 1,404,220 banner-store-sku rows · Texasbanner is a PRICE POSITION here, not a store size · schema v1.0

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

H-E-B at a glance

How we handle H-E-B specifically

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

Retailer: H-E-B — Texas, and a strong regional benchmark
The structure: Banners at three distinct price positions
Premium: A specialty format with a different assortment entirely
Core: The main banner
Value: Formats positioned against discounters
So: banner is a dimension, and rollups are computed
Own label: Unusually strong penetration, across tiers
Geography: Texas-concentrated. Regional, not national

Platform specifics

Three price positions inside one company

These are the reasons a H-E-B dataset needs its own handling rather than a shared retail schema.

The banners are strategies, not store sizes

Many grocers run formats that differ by size. Here the banners differ by price position, deliberately, and frequently operate in the same metros.

The premium format carries a specialty assortment with limited overlap against the core banner.
The core banner is the mainstream competitive position.
Value formats are positioned against discount competitors, with a narrower range.
The same product can appear across banners at different prices, which is the point rather than an inconsistency.

So banner is on every record and a company-level figure is a computed rollup with store_count_observed and banner_mix stated — because the rollup moves when the banner mix moves, which is the failure our surface separation page describes in a different setting.

Cross-banner comparison is the interesting output

Where the same product appears in more than one banner, the gap is an observation about the company's own price architecture. We record it from paired records rather than asserting a positioning percentage.

Own label depth changes the matching problem

Own-label penetration here is unusually high, and the range spans tiers from value through to premium and specialty.

In several categories own label is the majority of the shelf, which means a branded-only comparison covers a minority of what is sold.
Own label does not match across retailers. No shared identifier, no equivalent product.
So a cross-retailer index here runs on a smaller matched set than at a chain with lighter own-label penetration.

We report matchable_share_category before quoting, flag own label with own_label_tier from range naming, and mark it unmatched across retailers — the same position as our Aldi and Mercadona pages.

Where own label is the finding

Because penetration is high and tiered, own-label range breadth and tier mix per category is frequently more informative than the price series. We deliver both.

Texas concentration, and what a panel here represents

Operations are concentrated in Texas and adjacent areas rather than spread nationally.

Within Texas it is a dominant competitive reference, which makes it essential for anyone competing there.
Outside Texas it is not a benchmark at all, because it does not trade there.
A US national panel needs it as one regional component, as our US regional grocery page argues.

region_coverage_note ships per batch so a Texas panel is never read as a US figure.

Store-level pricing

Prices vary by store within a banner, driven by local competition and format. store_id is recorded where the retailer exposes store-level pricing, and where a single online price per banner is published we record that level instead.

What we do not collect

Loyalty or app account data, sales, volumes, customer or employee data. No accounts created, in any market.

Scope

What we collect on H-E-B, 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

banner on every record, with rollups computed and banner_mix stated
Cross-banner price gaps from paired records, never asserted
matchable_share_category reported before quoting
own_label_tier from range naming, unmatched across retailers
Own-label range breadth and tier mix per category
store_id where store-level pricing is exposed
region_coverage_note per batch
Promotional mechanics as displayed
In-stock state distinct from not ranged

❌ What we do not, and why

A company-level price averaging three price positions
Own label matched across retailers
A Texas panel presented as a US figure
A positioning percentage asserted from one banner
Loyalty account data, sales, customer or employee data

Core H-E-B fields

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

Field	What it is on this platform
retailer / banner / store_id / city	The banner is the dimension that matters
banner_price_position	premium, core or value, as the company positions it
product_id / upc	Identifiers where published
price / price_loyalty / gated_reason	Shelf, member where shown, and why not
cross_banner_gap_pct	From paired records only
is_own_label / own_label_tier	From range naming
matchable_share_category	Reported before quoting
own_label_share_category	Where own label is the majority of shelf
banner_mix / store_count_observed	Stated on any rollup
region_coverage_note	So a Texas panel reads as Texas
observed_at	Timestamp

Use cases

What teams do with H-E-B data

Banner-level competitive positioning

Banner on every record with its price position, so a premium format is not averaged with a value format into a company figure describing neither.

Own-label depth analysis

Own-label share and tier mix per category, in a market where own label is the majority of shelf in several categories and therefore the majority of what is sold.

Texas competitive benchmarking

A concentrated regional panel with the coverage note stated, which is the right reference for anyone competing in that market.

Cross-banner price architecture

Gaps between banners on the same product from paired records, which shows how the company spaces its own formats.

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

Send us a H-E-B 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.

H-E-B is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. H-E-B 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 grocery data scraping covers, and a H-E-B-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

H-E-B data scraping: frequently asked questions

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

Because the banners differ by price position rather than by store size, and they frequently operate in the same metros.

A premium specialty format, a mainstream core banner and value formats positioned against discounters are three deliberate strategies. A company-level average describes none of them.

Because penetration is unusually high — in several categories own label is the majority of the shelf, which means a branded-only comparison covers a minority of what is sold.

And own label does not match across retailers, so a cross-retailer index here runs on a smaller matched set than at a chain with lighter penetration. We report that share before quoting.

Only as one regional component. It trades in Texas and adjacent areas rather than nationally, so outside that footprint it is not a benchmark at all.

region_coverage_note ships per batch so a Texas panel is never read as a US figure.

Where the same product appears in more than one banner, yes — computed from paired records.

What we do not do is assert a positioning percentage from one banner, which would be a model rather than an observation.

Yes, within a banner, driven by local competition and format. We record store-level price where the retailer exposes it and record which level it was where it publishes one online price per banner.

We quote individually on banners, store count, category scope and refresh. Banner count matters more than store count here, since each banner is a separate price position.

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

See real H-E-B 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