Omnichannel Brand Price Monitoring

Problem

When a brand sells through Tmall, JD, Douyin, and Pinduoduo at the same time, the issue is rarely a single low price. It is channel drift: authorized stores, platform self-operated stores, and resellers may undercut the brand floor price, making manual patrol reviews slow and error-prone. A naive search can also miss stores, fabricate links, or return prices that cannot be verified. This skill turns that recurring price-compliance check into a repeatable workflow and produces a Markdown report that operators can act on.

How it works

The workflow is organized around configuration, search, comparison, and reporting.
- Monitoring config: products, platforms, stores, thresholds, and history directories are managed in YAML rather than hard-coded in scripts.
- Cross-platform search: maishou is used for product search and price lookup. For Tmall, searches should be done store by store using “store name + model number”, covering brand-owned stores, authorized stores, and platform channels. JD, Douyin, and Pinduoduo have their own search paths and known limitations.
- Price comparison: PriceMonitor loads config, fetches prices, checks thresholds, detects anomalies, records CSV history, and generates a risk-graded report.
- Report output: the MD file includes check time, data source, high/medium/low risk products, direct product links, current price vs threshold vs history, action suggestions, and monitoring trends.

Boundaries and caveats

This skill fits brand operations teams that already know the floor price, priority SKUs, and channel store list. The provided example is centered on Yuwell medical devices; other brands can reuse the workflow but must replace stores, SKUs, thresholds, and link strategy. Operators should be careful not to invent missing links, treat Douyin deep links as app-only, complete placeholder URLs before running, re-activate WorkBuddy scheduled tasks after reconnection, and treat fallback simulated prices as reference-only.