Explore the product feed diagnostics, correction review and planned monitoring tools behind feedrevive. Start with what exists in the private preview, then see where the product is heading.
Explore the workflow
A missing product identifier needs source research. A title that leaves out a confirmed color needs a different review. A price mismatch needs current storefront evidence, not a more complete description.
The useful result is a finding you can explain: what is missing, what supports the conclusion, and which person can take the next step.
Prepare for a first reviewThese workflows exist in the development preview. They are not a public signup or a guarantee of production readiness.
In private preview
Bring authorized store product records into a reviewable catalog. Shopify import has been validated with an owned development store. The import gives checks a source snapshot; it does not authorize changes to the store.
Use it to understand which products and variants the review is actually based on. WooCommerce live acceptance remains pending.
In private preview
Find missing product details such as titles, descriptions and identifiers. Review the affected product and the imported data that supports the finding.
A missing identifier is a prompt to investigate the source. It is not permission to invent a code, and an imported catalog check is not a Merchant policy decision.
In private preview
Bring proposed corrections together with the product record. Check the right variant, inspect the details and decide what to save for review.
AI-generated suggestions and image improvements are planned. The current store workflow requires making the source correction separately, then reimporting and checking again.
In private preview
Workspace roles and store scopes help separate access across teams and catalogs. Owner MFA and scoped invitations form part of the private development foundation.
These foundations do not establish that every production security control or agency workflow is finished. Read the security and data overview for the limits.
These capabilities describe the roadmap. They are not available as a public service.
Planned
Connect account diagnostics, policy evidence, source conflicts and sync history. The goal is to connect a warning to the source record that may explain it, while making missing or old evidence visible. Google Merchant Center integration is planned.
Planned
Generate titles, descriptions, attributes and controlled image proposals using confirmed product information. A suggestion should preserve the product’s actual identity. AI generation is planned; the examples on this website are authored demonstrations.
Planned
Compare price, stock, shipping and landing-page evidence, with checkout and structured-data checks. These checks need independent data: a complete catalog alone cannot establish that the storefront and checkout agree.
Planned
Tie an exact change to authorized review, then follow the source request with an outcome check. A request being processed should never be presented as confirmed platform acceptance. Direct source publishing is not available through this website.
Planned
Explore feed relevance, custom labels, opportunities and controlled experiments. Recommendations would need to distinguish estimates from observed results. No revenue lift, ad result or Merchant approval is guaranteed.
Planned
Track fresh findings, recurring overwrites and change history. The roadmap includes scheduled reports, client assignments, branded reporting and a client portal. Portfolio and reporting illustrations are not live customer results.
A quick comparison of development status. No capability here is offered as a public service yet.
| Question | Relevant capability | Current status |
|---|---|---|
| What did we import? | Store catalog and variant review | Private preview; Shopify read-only import validated with an owned development store |
| Which product details are missing? | Catalog checks and correction review | In private preview |
| Can AI draft the change? | Grounded generation | Planned |
| Does the storefront agree? | Price, stock, checkout and landing-page checks | Planned |
| Was the change accepted? | Source publishing and Merchant outcome verification | Planned; approval is not platform acceptance |
| Can we coordinate a client portfolio? | Assignments, portfolio oversight and branded reports | Planned, beyond the current workspace/store access foundation |
Different questions call for different evidence. That distinction stays visible as the product grows.
Start with imported catalog checks and source data. The product workflow explains how to review the finding and make a source correction today.
Read the product workflowThat needs a separate downstream outcome check. Planned publishing and Merchant verification must not be inferred from a saved proposal or a healthier catalog score.
Read about approval and verificationShare the checks, evidence or review steps that matter to your team.