移动代理零售数据
零售数据是商业领域中始终未脱离实体世界的一部分：即今天某家特定商店货架上实际陈列的商品及其具体价格。其中绝大多数数据都受限于邮政编码和本地访客的限制。
- 库存数量按门店计算，而非按网站计算 — 库存查询接口的响应结果针对具体分店，且必须指定具体门店位置才能返回结果。
- 邮政编码是查询内容的一部分——如果没有邮政编码，大多数杂货店和连锁店都不会显示任何有用的信息。
- 促销活动具有区域性 ——同一连锁品牌在同一国家的不同地区会推出不同的优惠活动。
- “每日”才是合适的节奏 ——货架每天都会变动，而门店终端并非为持续轮询而设计。
像附近的顾客那样查询库存情况。
查看仅在零售商应用程序中才有的库存和优惠。
Retail Data Beyond the Website
Retail data is the part of commerce that never moved online. It describes physical stores: what is on the shelf in a particular branch, at what price, today. The unit of analysis is the store rather than the catalogue, and almost everything interesting is gated behind a location.
That produces a specific access shape. Availability endpoints, click-and-collect slots and local pricing are all functions of a branch, so the retailer asks where you are before it will tell you anything. Supplying a postcode from a foreign address frequently returns a partial answer or a rejection, which is why a local exit and a local postcode go together — either alone tends to produce data that looks fine and is not.
| What varies by store | 为什么 |
|---|---|
| Stock and availability | Physical inventory sits in a building, not on a website |
| Price | Local competition, store format and regional cost all move it |
| Promotions | Chains run regional campaigns that never appear nationally |
| Range | Store size determines what is carried at all |
| Collection slots | Capacity is per branch and changes through the day |
Store-Level Stock and Availability
The most valuable field in retail data is one no retailer publishes: how long a product was actually unavailable at a given branch. Availability snapshots are commonplace and fairly uninformative. Out-of-stock duration is what tells you about supply reliability, distribution failures and demand spikes — and like time on market in property, it exists only if you were collecting continuously.
store_id … postcode_area … product_id … in_stock true | false | limited observed_at 2026-08-24T09:14:02Z market GB price … # per store, not per chain promotion … # regional campaigns show up here
Cadence should be daily. Availability and promotions turn over on that rhythm, and faster collection adds noise rather than signal — a product going out of stock at eleven and back in at three is not something anybody can act on. Store-level endpoints are also comparatively fragile and were never designed for constant polling, which is a second reason patience pays here.
Local Pricing and Promotions
In many markets, prices genuinely differ between stores in the same chain, and it is one of the more interesting things retail collection reveals. Convenience and forecourt formats frequently price well above the same chain’s supermarkets, and that is deliberate strategy rather than error. None of it is visible from the national website.
Regional promotions behave the same way. A chain may run a campaign in one part of a country to answer a local competitor, and the national site will show no sign of it. Collecting per region rather than per chain is what surfaces this, and it is usually the finding that justifies the programme to whoever is paying for it.
Scaling Retail Collection
The temptation is to cover every store. It is almost always wrong. A well-chosen sample — a handful of branches per region, spanning the formats the chain operates — captures the variation that matters at a fraction of the volume, and a smaller footprint is also considerably less likely to attract attention from endpoints that were never built for this.
- Sample stores, do not enumerate them — Variation comes from region and format, not from store count.
- Hold the store as part of the key — Chain-level aggregation destroys exactly the differences you collected for.
- Pair a local exit with a local postcode — Either on its own produces answers that look complete and are not.
- Watch the app surface too — Some chains expose stock and offers in their app that the website never shows.
- Alert on collection health — A store endpoint that starts returning empty looks identical to a store with nothing in stock.
For the online half of the same question see ecommerce data, and for continuous price watching, 价格监控.
像本地购物者那样查询商品
PXM2实时位置——选择您正在追踪的连锁店所在的国家，并从每个国家/地区内部收集门店级数据：
法国
印度
新加坡
常见问题解答
零售数据与电子商务数据有何不同？
电子商务数据指的是提供全国配送服务的网站。零售数据则指实体店铺，其分析单位是分店而非产品目录。这一点彻底改变了局面：库存按分店计算，同一连锁品牌下不同分店的售价可能存在差异，促销活动按地区开展，而真正有意义的问题是“特定顾客附近的货架上有什么商品”，而非“零售商原则上销售什么商品”。
为什么涉及邮政编码？
因为如果没有邮编，门店级别的服务端无法提供答复。库存情况、“线上下单、门店自提”的时段以及当地价格都与具体分店相关，因此零售商在提供任何信息之前，都会先询问您的所在地。 如果提供国外地址的邮政编码，通常会导致回复不完整或被拒绝，因此将本地出口与本地邮政编码配对才是真正有效的组合。
同一连锁店的不同分店之间，价格真的会有差异吗？
在许多市场确实如此，这也是零售数据所揭示的较为有趣的现象之一。连锁企业会根据当地竞争状况、门店业态和区域成本进行调整，而这些差异在全国官网上是看不出来的。尤其是便利店和加油站便利店，其定价往往远高于同一连锁企业的超市，这是一种刻意采取的策略，而非失误。
货架数据需要什么样的更新频率？
“每日”这一频率在库存情况和促销活动方面恰到好处，因为这两者都遵循这种更新节奏。更新频率过高反而会增加“噪音”而非“有价值的信息”——例如，某款产品上午11点缺货、下午3点又补货，这种信息并不能为你提供任何可付诸行动的参考。此外，门店级终端相对不稳定，且原本就不是为持续轮询而设计的，这也是在此情况下保持耐心会有所回报的另一个原因。
记录什么最有帮助？
各门店的缺货情况及其持续时间。库存状况快照很常见；但某款产品在特定分店实际缺货了多长时间却不常见，而正是这个数据能反映出供应可靠性、分销问题和需求激增的情况。就像房地产中的“在市时间”一样，只有持续收集数据，才能获得这一数据。
相关移动代理指南
Retail is the physical half of commerce; the online half and the pricing half sit next door.
商业应用场景
核心移动代理指南
Query Stores From Inside the Region
Dedicated 4G/5G modems with unlimited bandwidth and unlimited rotations — carrier IPs that make a local postcode return a real answer.
获取移动代理