1) If procurement requires publicly documented SOC 2 / ISO 27001
- The vendor does not prominently publish these certifications. Highly regulated buyers may prefer vendors with a public trust center and standard security collateral.
2) If the business requires inventory truth rather than observed availability
- Public reviewer comments note instances where the vendor's out-of-stock dashboard does not match internal on-hand inventory. For inventory-truth use cases, POS or inventory integrations may be required.
3) If transparent, self-serve pricing is required
- The product is sold via sales-assisted contracts with no public pricing tiers; teams seeking published entry pricing may find alternatives better aligned to that need.
4) If eCommerce-only monitoring is the primary requirement
- The product's differentiation in vendor materials is oriented toward store-level coverage; organizations focused solely on online marketplaces may find other tools that are more tailored and potentially lower cost.
1) Scraping instability
- Retailer site structure changes can disrupt extraction and continuity. This class of risk is common among providers that rely on public site crawling and scraping.
2) Availability / out-of-stock inconsistencies
- Public reviews indicate the out-of-stock signals reported by the product do not always match internal on-hand data.
3) Public information gaps
- Security certifications (SOC 2/ISO) are not clearly published in vendor materials.
- Pricing is not published.
- Public methodology documentation for key metrics (observations, per-store SKU coverage, refresh frequency) is limited.
4) Integration surface questions
- Public API documentation indicates exports and ingestion webhooks, but common buyer questions about SSO/SCIM support, audit logs, role granularity, rate limits, and SLAs require direct vendor engagement.