Grocery chains under measurement, each counted once however many ways it sells. Eight marketplace and delivery platforms are measured alongside them, for 31 retailer identities in all.
Coverage
23 grocery chains and 8 marketplace and delivery platforms, measured the way they actually sell.
Basket Bee independently measures the major grocery retailers operating in Egypt, together with the marketplaces and delivery platforms selling alongside them. Each is measured on the channels it actually sells through, and 10 of them are read on both the in-store and the delivery side. These are captured observations of a real catalog at a stated date, not a live-price guarantee.
Listings carrying a price in the most recent complete capture, counted exactly rather than estimated. 99.8% of the capture's listings carry one.
The figure that decides whether a price can be compared between rivals: distinct products with a price at two or more different retailers. The catalog holds far more products than this; most are sold by only one of them.
Catalog as of 2026-08-23 · exact counts over that capture, not estimates
One chain is not one price.
A single retailer does not have a single price. The same chain can charge differently depending on where you are and how you buy, and treating that as one national figure produces a number that is true nowhere.
So each chain is measured on each of the ways it actually sells, and those observations are kept apart rather than averaged together. Counting chains is how breadth is reported; keeping their surfaces distinct is what makes a comparison honest.
Depth, not just breadth
359,260 priced listings in the latest capture, and every capture before it.
Past captures are kept rather than overwritten, so the catalog accumulates a price history instead of replacing itself. History is what turns a price into a trend, and it is the part a new entrant cannot buy or catch up on quickly.
What sits behind the coverage.
Breadth is only useful if the data behind it is trustworthy. These are the parts of the system that make the coverage mean something.
A working measurement fleet
Collection runs across the major Egyptian grocery chains and the platforms selling alongside them, on whichever channels each one actually sells through, producing a catalog that is rebuilt cycle after cycle.
Cross-retailer product identity
The catalog resolves listings into comparable products rather than stopping at a pile of rows, which is what makes any comparison possible at all.
Accuracy that is measured
Match quality is scored against barcode evidence withheld from the matcher, and the result is written down — including the share of matches no independent check can reach.
Licensed access model
The client data model, per-client scoping and package structure for the B2B product are built and running in a controlled environment.
Operator control plane
An internal console runs collection, review and publication, and keeps the risky actions explicit.
Governance scaffolding
Access boundaries, retention rules and automated checks sit alongside the pipeline rather than being left to habit.
Coverage is the start of the moat, not the whole of it.
Breadth alone is reproducible given enough time and money. What is not easily reproducible is the layer that decides when two rival retailers are selling the same product, the accumulated history behind every one of those decisions, and the discipline of stating what accuracy has actually been measured on rather than rounding it into a boast.
Coverage figures are counted from the catalog itself at the date shown above. Collection is operator-run, so no refresh cadence is promised.