Definition
Time-based divergence of price, availability, shipping, or policy facts across PDP, structured data, product feed, Merchant Center, and checkout cart, caused by asynchronous updates rather than a single point-in-time error.
StoreSteady treats offer drift as a reference term because Pipeline lag: The merchant's update pipeline is too slow for agent-grade offer freshness.
Why it matters
- Pipeline lag changes what a crawler, shopping channel, or AI assistant can safely infer about the merchant surface.
- Without a named category, operators tend to treat offer drift as generic AI noise instead of a reproducible finding with evidence and a validation path.
Evidence sources
- lag between PDP and feed; lag between feed and Merchant Center; lag between merchant inventory system and PDP; price/availability divergence at confirm time.
How StoreSteady detects it
Sample all four surfaces (PDP, structured data, feed, Merchant Center, checkout) at the same timestamp. For changes detected on any one surface, measure the time-to-converge across the others. Flag drift windows that exceed the merchant's documented tolerance (or, in absence of documentation, > 60 minutes for price/availability).
False positive risks
- A static, persistent feed-vs-PDP mismatch with no time component - that is a parity violation, not drift.
- A planned, synchronized price change that becomes effective at a specific timestamp.
How to fix it
- Identify the merchant-controlled source that creates the offer drift signal.
- Reconcile visible copy, machine-readable data, policy text, feed state, and checkout behavior where the term applies.
- Keep the fix high-level in public docs; detailed remediation belongs inside paid scan workflows.
How to validate it
Rerun the same evidence capture used for detection. The finding is validated only when the original offer drift signal no longer reproduces and adjacent source surfaces still agree.
Example finding
Pipeline lag
Observed: A merchant updates a price in their PIM at 12:00. The PDP reflects it at 12:01, the feed updates at 12:15, Merchant Center processes it at 12:45. Between 12:01 and 12:45, the offer is drifting across surfaces.
Likely impact: Pipeline lag: The merchant's update pipeline is too slow for agent-grade offer freshness.
Probable fix location: Public commerce source of truth
Related StoreSteady issue codes
| Code | Title | Scanner mapping |
|---|---|---|
| TRU-002 | PDP/feed/checkout price mismatch | price_mismatch_shopify_vs_merchant |
| TRU-003 | Availability drift | availability_mismatch_shopify_vs_merchant |
| OFF-005 | Feed/markup parity gap | shopify_products_missing_from_merchant |
Related standards
See also
Sources
Run a scan against this category
StoreSteady scans public commerce evidence and maps findings back to documented taxonomy terms.
Run a free scan