Read about product feed review, platform connections, AI, pricing and data practices. These answers distinguish the private development preview from the capabilities planned for public launch.
Ask a different questionTry a broader word such as “store”, “pricing” or “data”, or ask us directly.
What the product is, who it is for and when you can use it.
feedrevive is a product feed review tool in development for merchants and agencies. Its private preview brings imported catalog data, missing-field findings and proposed corrections into a review flow. The longer-term direction connects catalog, storefront and Merchant evidence, with authorized publishing and separate outcome checks. Those planned capabilities are not all available today.
Public signup is not open. The private preview is used for development and validation; this website is an introduction with fictional demonstrations. You can discuss your catalog through the contact page. The form sends your enquiry to our team; it does not subscribe you to marketing.
The intended customers are merchants responsible for product data and agencies working across client stores. The review workflow is useful when a team needs to understand an issue, identify the source of a correction and keep a reviewer in control. It is not a promise of advertising management or managed Merchant account appeals.
We intend to serve businesses in the US, Europe, Australia and other markets. Public availability, regional terms, billing and privacy arrangements are still being finalized. Customer location and storage location are different: USA storage remains the current launch direction; an EU or Australian residency option is not offered by this preview.
The source data and boundaries behind a useful finding.
Read-only Shopify catalog import has been validated with an owned development store in the private preview. WooCommerce live validation is pending. A Google Merchant Center connection is planned. This marketing site cannot connect a store, import products or authorize access to your accounts.
The private preview checks imported product details for gaps such as missing titles, descriptions and identifiers. Findings reflect the data that was imported and the coverage of that check. They are not a Google Merchant Center decision, a live checkout test or proof that a product is eligible for Shopping ads.
An audit describes a particular version of the imported data. If the source product changes, an earlier finding or proposal may need another review. The current workflow calls for correcting the source store, reimporting its data and checking again. A previous healthy result should not be read as a permanent guarantee.
No. Platform policy decisions remain with the platform, and sales depend on factors beyond product data. Source publishing, downstream processing, platform acceptance and commercial performance are separate outcomes. A successful action at one stage does not establish success at the next.
Who decides, what changes, and what still needs checking.
No product changes happen through this website. The private preview does not write corrections back to Shopify. AI generation and source publishing are planned. The intended workflow keeps suggestions grounded in real product facts and requires authorization before changes; optional low-risk automation would need explicit permissions and defined budgets.
Check the exact product, brand, material, color and variant against your source information. A longer title is not automatically better. If a fact is unknown or unsupported, do not add it merely to make the title sound more complete. The fictional tote example demonstrates reviewing supplied facts; it is not evidence of live AI generation.
Approval records an authorized decision about a proposed change. Verification checks what happened afterward. In the planned publishing flow, a source can receive a request while a downstream platform is still processing or rejecting it. The sample walkthrough deliberately keeps approval distinct from platform acceptance.
Workspace and store access controls exist in the private preview. The agency roadmap adds a portfolio view, assignments, branded reports and a client portal. Those portfolio tools are illustrative on this website and are not generally available. Custom-domain white-label and branded communications are outside the current scope.
Commercial and data arrangements, with open decisions kept visible.
The provisional monthly plans are Starter $49, Growth $149, Pro $399 and Agency $999 USD. Planned limits vary by active SKUs, stores and included AI credits. These are planning figures, not an offer you can buy today. The pricing page shows proposed annual totals and the assumptions behind each allowance.
Each active variant/SKU is planned to count once per store, including active published out-of-stock variants. Repeating a feed or market within the same store would not count that variant again. A product with multiple variants can therefore use more than one SKU of its allowance. Limits remain provisional until commercial validation.
The plan separates the subscription from metered AI work, with a monthly credit allowance. Paid tasks would show an estimate before approval. Core monitoring is intended to continue within the plan when credits run out. Final task costs, top-ups, rollover and credit terms must be confirmed before checkout becomes available.
The planned trial runs for 14 days from the first audit results, with one store, up to 1,000 active SKUs and 25 title or description previews. It is intended to be read-only with no card and no automatic charges. This is the planned offer; there is no trial activation on this website.
USA storage is the current launch direction for application-managed content. EU and Australian residency choices are not available in this preview. Supplier processing locations, transfer safeguards, retention and deletion arrangements must be finalized and disclosed before public launch. See the security page and draft privacy documents for the current boundaries.
The current marketing build has no analytics, advertising pixels or external tracking scripts. Cookie preferences in the footer can save or remove a simple browser preference. It is not consent to future tracking. If optional tools are added, their disclosures and consent controls must be updated before those tools run.
Tell us what you need to understand before trying feedrevive.