Paz
AI shopping visibility and reviewable product-data recommendations.
AI shopping visibility and reviewable product-data recommendations. Pricing documents monitoring, catalog corrections and human approval workflows. Does not replace merchant approval or guarantee ranking and sales. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes
The documented role and version scope in the source ledger.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Claim-to-source mapping
- description: AI shopping visibility and reviewable product-data recommendations. · verified · Checked 2026-09-28 · Sources: paz-pricing
- role: Pricing documents monitoring, catalog corrections and human approval workflows. · vendor-claim · Checked 2026-09-28 · Sources: paz-pricing
What is documented today.
Each state applies to a named capability and scope. Native describes the product’s own role; it does not mean your merchant account has a live integration.
Shipped / publicly documented
Shopping visibility measurement native / live
Paz: visibility in the documented product role only. Not proof of a live merchant account, connector or AI-surface deployment. Confirm plan, market and onboarding.
Product-content improvement native / live
Paz: optimization in the documented product role only. Not proof of a live merchant account, connector or AI-surface deployment. Confirm plan, market and onboarding.
Announced / roadmap
Cannot verify
What it does not solve: Does not replace merchant approval or guarantee ranking and sales.
What it helps with
Pricing documents monitoring, catalog corrections and human approval workflows.
What it does not solve
Does not replace merchant approval or guarantee ranking and sales.
The merchant work
- Identify which existing capability this would replace or complement.
- Confirm region, plan, data access and integration effort.
- Request a scoped proof of fit before purchasing.
Merchant fit: Teams able to fund recurring visibility and product-data work.
Individual merchant eligibility and deployed configuration require confirmation.
| Onboarding | Vendor consultation; job-specific permissions. |
|---|---|
| Surfaces | Unknown |
| Protocols | Unknown |
| Pricing | Essentials: USD 1,000/month; Growth: USD 2,500/month; Enterprise custom |
| Regions | Unknown |
| Integrations | Confirm exact platform and connector; no blanket support inferred |
| History | First observed September 2026 |
What we observed, and when.
First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.
First observed 28 September 2026. One baseline snapshot; no subsequent change is recorded.
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Essentials and Growth plans
Monthly USD; Essentials $1,000, Growth $2,500; Enterprise custom. No annual commitment for listed plans.