Preserve evidence before generating insights
Record the sampling scope, actual review count, duplicate rate, source and page anomalies before producing a summary.
Separate product, fulfillment and service issues
Classify capacity, performance, materials and durability separately from packaging damage, shipping delays and after-sales service.
Measure impact, not only frequency
A pain point should include its frequency, affected-product count, representative evidence and trend so teams can prioritize product changes.
Local data by default
Review records stay in the app-specific local database unless the user exports or sends them to a configured external service. Sharing the app does not copy the local database.