Product Analytics
Product Analytics is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to the Product Analytics playbook…
What this skill helps you do
Use the Product Analytics playbook when you need to turn store, pricing, and performance data into operating decisions. It gives the operator a repeatable set of checkpoints.
Use the Product Analytics playbook when you need to turn store, pricing, and performance data into operating decisions. It gives the operator a repeatable set of checkpoints.
Before you start
- Choose one bounded, reversible decision-ready analysis to test.
- Prepare consistent exports, metric definitions, cost data, date ranges, and known data gaps, removing sensitive fields the trial does not need.
- Record the current data completeness, calculation accuracy, contribution margin, and decision follow-through, then name the approver and stop conditions.
How to test it safely
- Test one normal case, one edge case, and one case with a deliberately missing critical field.
- Compare the result with the pre-test baseline for data completeness, calculation accuracy, contribution margin, and decision follow-through; do not record time saved alone.
- Review errors, human edits, permissions used, and unresolved exceptions before expanding scope.
Operator-ready setup plan
Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where Product Analytics can help you turn store, pricing, and performance data into operating decisions.
Checkpoint: The input boundary, owner, and one primary measure from data completeness, calculation accuracy, contribution margin, and decision follow-through are written down.
Prepare the input and guardrails
Collect only the consistent exports, metric definitions, cost data, date ranges, and known data gaps needed for this test. Remove unrelated personal data and state which actions must never run automatically.
Checkpoint: Every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.
Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding Product Analytics to a separate test project. Keep commands and Skill text exactly as published.
Checkpoint: You have a decision-ready analysis that a responsible operator can inspect, and it stayed inside the approved boundary.
Review it against a baseline
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.
Checkpoint: data completeness, calculation accuracy, contribution margin, and decision follow-through has a pre-test baseline, and errors and exceptions are logged separately.
Expand in small batches with a stop rule
Increase one batch at a time and decide in advance what will stop the rollout. Add it to the regular SOP only after it repeatedly clears the quality bar.
Checkpoint: Wider use does not push error, complaint, or rework costs above the previous baseline.
Limits to account for
- We checked the public source and resource identity on 2026-07-19. That review does not cover every workflow result, and vendor performance claims are not treated as EcomAgentTools tests.
- A polished dashboard can still be wrong when attribution, costs, refunds, or time windows do not line up.
- This page reflects the review completed on 2026-07-19, not a permanent guarantee. Recheck the current documentation, pricing, and contract terms before production use.
Questions at this experience level
How do I add Product Analytics to the current SOP?
Map the input source, owner, approval point, and exception path, then replace one existing step. Do not rewrite the whole operation just to accommodate a new tool.
Which metrics show whether it is worth keeping?
Track data completeness, calculation accuracy, contribution margin, and decision follow-through. Pair quality and efficiency measures so output volume is not mistaken for a business result.
When is it not worth using?
It is usually a weak fit when volume is low, inputs stay incomplete, most cases need senior judgment, or review costs approach the cost of the old process.
Creator, original source, and platform proof
Alireza Rezvani
HealthTech CTO and open-source maintainer focused on applied AI, agentic coding, and practical skills for product, research, growth, and operations teams.