Yotpo charges $79/mo
just for reviews.

What Yotpo actually costs over time

Yotpo charges $79–399/mo. That sounds manageable month to month — until you run the math. Over a year that comes to $948–$4,788/year. Stretched over five years — a reasonable lifespan for a healthy Shopify store — the total reaches $4,740–$23,940. None of that money builds equity in your store. None of it makes the software yours. It buys access, and access ends the moment you stop paying.

The features that matter — photo reviews, automatic request emails, SEO schema — require Yotpo's $79+/mo plans. You're paying a SaaS premium for functionality you could own outright.

What a custom photo reviews & automated requests app actually includes

The assumption most merchants make is that replacing Yotpo requires a developer, a long timeline, and a significant budget. That was accurate until AI builders trained on actual Shopify documentation changed the economics. A Shopivibe-generated photo reviews & automated requests app ships as a complete, deployable application — not a prototype. OAuth, Shopify Billing API, webhook handlers, and App Bridge come built in before you describe a single feature specific to your store.

The comparison table above breaks down exactly what you get. Specifically: Monthly fee, Photo reviews, Automated review emails, SEO schema markup, Review data ownership. These are not paid add-ons or plan upgrades — they're the baseline of every app built through Shopivibe.

When the math tips in favor of building

At $79–399/mo, the payback period on a custom build is typically three to six months — after which every month is margin recovered rather than rent paid. The rule most merchants use: if you've been paying for Yotpo for longer than six months and it costs more than $50/month, building your own version is almost always the cheaper option over a two-year window.

Beyond the cost math, there's a strategic case for ownership. Yotpo holds your photo reviews & automated requests data — customer records, transaction history, any accumulated state — in their infrastructure. If a vendor raises prices, gets acquired, or shuts down, migrating that data is painful by design. Owning the code means owning the data, and the ability to extend or change the logic without asking permission or paying for a higher tier.

When to keep paying instead

Not every store should replace Yotpo. If you're in the first few months of trading and still validating your product, app costs are a minor variable compared to everything else on your plate. If the app costs under $30/month and works perfectly, the time investment isn't worth it. The decision becomes clear when Yotpo is a meaningful recurring line item, when you've hit a plan ceiling, or when you want the photo reviews & automated requests experience to feel fully native to your brand rather than a vendor widget embedded in your store.

See how Shopivibe pricing works or browse all the apps you can replace to map out what your full replacement stack would look like, or explore all Shopify photo reviews & automated requests apps.

What a Shopify photo reviews & automated requests app actually has to do

A Shopify reviews app requires the read_products scope to attach reviews to product records and write_metafields to store aggregate ratings as product metafields — queryable from the Storefront API without extra requests. The read_orders scope lets the app verify that a customer purchased a product before flagging a review as "verified." Photo reviews require write_files to upload images to Shopify's Files API and receive CDN-backed URLs. The orders/fulfilled webhook is the correct trigger for sending review requests — not orders/create, which fires before the order ships. Three GDPR webhooks are mandatory: customers/data_request, customers/redact, and shop/redact. Shopify suspends apps that don't respond to these within 30 days.

The data model behind photo reviews & automated requests on Shopify

The minimum data model has three tables. A Review table stores the core record: product_id (Shopify GID), customer_id, order_id for the verified-purchase check, rating (1–5), title, body, status (pending/approved/rejected), and created_at. A ReviewMedia table links photos and videos to reviews: review_id, shopify_file_url, media_type, display_order. A ReviewRequest table tracks outreach: order_id, sent_at, email_address, clicked_at, submitted_review_id. The product_id is a Shopify Global ID (gid://shopify/Product/123), not a numeric ID — queries must handle GID format throughout. Aggregate ratings (average, count) are cached as product metafields so storefronts can render star ratings without a server request.

Edge cases most photo reviews & automated requests apps get wrong

• Verified purchase timing: the order must be in fulfillment_status: fulfilled and financial_status: paid before marking a review verified — unfulfilled orders must not count
• Photo upload latency: Shopify Files API enforces a 20MB limit per file and processes uploads asynchronously — the CDN URL is not available instantly after upload
• Schema.org Product markup: the aggregateRating property must use the Shopify product URL as the url field, not your app's URL, or Google won't associate the rating with the product page
• Google Shopping syndication: feeding reviews to Google Shopping requires a separate Product Ratings XML feed submitted through Google Merchant Center — this is distinct from on-page Schema.org markup
• Review request timing: the orders/fulfilled webhook (not orders/create) is the correct trigger; sending review requests before fulfillment drives complaints and opt-outs
• Moderation workflow: auto-approval surfaces negative reviews immediately — most stores want manual review for 1–2 star ratings before they go live
• Multi-language stores: review request emails must use the customer's locale from the order object, not the store's default language setting

Migrating off Yotpo without losing data

Exporting your data: Yotpo provides a CSV export from the dashboard (Reviews > Export). The export includes review text, rating, reviewer name, email, product ID, and submission date. Photos are not in the CSV — they link to Yotpo's CDN URLs, which expire after your subscription ends.

Mapping to your new app: Yotpo product IDs are Shopify product IDs — the mapping is 1:1. Reviewer emails can be matched to Shopify customer records. Photo assets must be re-uploaded to Shopify Files API before the Yotpo CDN link expires; plan a migration window where both systems run simultaneously.

Parallel-run period: Run both systems for 2–4 weeks: Yotpo collects reviews from orders placed before the cutover date, the new app collects from orders after. Merge the CSV export into the new database at the end of the parallel period, then disable Yotpo.

Frequently asked questions