Sumzy documentation

When a shopper lands on a product page, Sumzy renders a widget that shows a short summary, an overall sentiment signal (Mostly positive, Mixed reviews, or Mostly negative), and a set of ranked aspect chips. Each chip covers a product attribute and carries a proportion indicator (one, a few, or many mentions) so a minority complaint is never presented as a majority one. Clicking a chip opens a brief drill-down for that aspect.

Summaries are generated asynchronously in the background via WooCommerce’s built-in Action Scheduler. The widget reads from a local database table; there is no API call to the Sumzy backend on page load. Product pages stay fast and intact even if the backend is temporarily unreachable.

Every summary is clearly labelled as AI-generated, both visually (an [AI] pill) and in accessible text for screen readers. Summaries are always honest and proportional; Sumzy does not hide, omit, or minimise recurring complaints.

Features such as manual placement, approval workflow, and per-shopper multilingual summaries depend on which plan is active; see what each plan includes.

• WordPress. Version 6.6 or later.
• PHP. PHP 8.2 or later. PHP 8.4/8.5 are supported in development.
• WooCommerce. Version 10.0 or later (tested up to 10.8). HPOS (High-Performance Order Storage) is supported with no extra configuration.
• Product reviews enabled.WooCommerce must allow product reviews (WooCommerce → Settings → Products → “Enable product reviews”). Sumzy only summarises products that have approved reviews.
• WP-Cron or server cron. Action Scheduler relies on WordPress cron events to run background jobs. A standard shared-hosting cron or WP-Cron is sufficient.
• Outbound HTTPS. The plugin sends review data to the Sumzy API (api.sumzy.io) over HTTPS from scheduled background jobs (never from shopper page loads). Your server must be able to make outbound HTTPS requests.
• Single-site install. WordPress Multisite is not officially supported at launch. Single-site installations only.

Installing the plugin

• Download the Sumzy plugin ZIP from your account at sumzy.io/account.
• In your WordPress admin go to Plugins → Add New → Upload Plugin, choose the ZIP file, and click Install Now.
• Click Activate Plugin. The Sumzy menu appears in the left sidebar.

Activating your license

After activation, Sumzy shows a license-activation prompt. Enter your license key and click Activate License. Your license key is in your purchase confirmation email and on your Sumzy account page.

• Lost your key? Recover it here by entering your purchase email address.
• Free trial.Trials last 14 days and require a credit card. Your trial grants full access to whichever plan you selected, so you experience exactly what you’ll pay for. The trial includes enough summaries to cover your whole catalog, up to 1,000 as a fair-use cap.

Automatic updates

Once your license is active, Sumzy receives updates through the standard WordPress update mechanism (Dashboard → Updates). Freemius handles delivery; no manual ZIP downloads required for routine updates.

• Install and activate the license (see Install & license above). Sumzy is ready to generate summaries; no AI configuration needed.
• Choose your language and tone. Sumzy detects your store’s WordPress locale and pre-fills the output language. Set the language and the summary tone in Sumzy → Settings. Summaries are always written in the language you choose, regardless of what language your reviews are in.
• Review and apply your settings. The first generation runs only after you have reviewed and saved your settings. This is a deliberate settings-applied gate, so Sumzy never fires on a bare install before you have chosen your language and tone.
• Generate your first summaries. On the Settings screen Sumzy prompts you to generate summaries for your existing products. Click Generate summaries now. This queues all eligible products in the background, and a progress indicator tracks completion. You can also skip this and let summaries build up naturally as products are reviewed.
• Wait a few minutes. Summaries are generated in the background. Active products with enough reviews will populate within minutes on most hosting environments. Products with fewer reviews than your minimum threshold setting will be skipped.

Local render, zero page-load calls

The widget reads from a local wp_sumzy_summariesdatabase table. There is no call to the Sumzy API on a shopper’s product page load. The backend can be down and your product pages remain fast and intact. This is a core design constraint, not an optimisation.

Background generation via Action Scheduler

Generation happens through WooCommerce’s built-in Action Scheduler. When a summary needs to be created or updated, Sumzy schedules a background job. The job gathers the product’s approved reviews, sends them to the Sumzy backend, receives a job ID, and polls for the result. Shoppers never wait for it; everything runs in the background.

Debounce coalescing

When a review is added, approved, edited, or deleted, Sumzy waits a short window before firing a generation job. If another review change arrives within that window, the timer resets. This means a burst of review edits or approvals produces one generation job, not dozens.

Periodic background check

Sumzy periodically runs a background check across your catalog. It advances through your products progressively so large catalogs with thousands of products are covered over successive passes rather than all at once. Any product whose review set has changed since the last summary is re-queued. If the reviews are unchanged, a hash match skips the backend call so no generation is wasted.

Review changes trigger immediate regeneration

A new review, an approved or unapproved review, an edited review, or a deleted review all trigger a debounced regeneration for that product. You do not need to wait for the periodic sweep to pick up a significant review change.

Automatic placement

Available on all plans.

• Above the reviews (default). The widget appears above the reviews section on the product page. This is the recommended placement and works on classic themes, block/FSE themes, Elementor, Woodmart, Flatsome, Avada, and most other theme/builder combinations.
• After the review list. The widget appears below the last review in the reviews section. Useful when your design favours a post-review placement.

Automatic placement uses a cross-theme injection technique (comments_template filter at priority 11) that works reliably even on themes that bypass the standard WooCommerce tab callback, including Woodmart and other Elementor-based themes.

Manual placement

Available on Professional and Business.

Professional and Business plans unlock a third placement mode, Shortcode only, which disables automatic output entirely. Place the widget wherever you like using the shortcode, Gutenberg block, or PHP template tag.

If your plan lapses or you downgrade to Essentials, Sumzy automatically falls back to the Above the reviews placement so your product pages are never left blank.

Shortcode

Available on Professional and Business.

Use [sumzy_summary] anywhere a shortcode is accepted: in a WooCommerce product template, a page builder widget, or classic editor content.

• product_id (optional, integer). The product ID to summarise. Defaults to the current post ID, which is correct for all standard product page contexts.
• heading (optional, string). The heading element level for the widget title. Accepts h2 through h6. Defaults to h2. Use this to match the heading hierarchy of your product template. Example: [sumzy_summary heading="h3"]

Gutenberg block

Available on Professional and Business.

The Sumzy Review Summary block (sumzy/summary) is available in the block editor. Search for “Sumzy” in the block inserter. It is server-rendered: the same PHP renderer as the shortcode, with the same output. Use it in a WooCommerce product template or any block-editor context on a product page.

Block attributes mirror the shortcode: productId (integer, defaults to current post) and heading (string, defaults to h2).

PHP template tag

For theme developers who prefer direct PHP, use the template tag in any template file on a product page:

<?php sumzy_summary(); ?>

Optionally pass a product ID: <?php sumzy_summary( $product_id ); ?>. The tag echoes the widget directly and outputs nothing when the product has no summary or the store is not entitled; it never throws a fatal error.

Page builder notes

Sumzy works with any page builder. In addition to the shortcode (which works in any builder’s shortcode or code widget), native drop-in widgets are available for Elementor, Divi, Bricks, Beaver Builder, and WPBakery. The Gutenberg block editor has its own native block. A wp_footerfallback covers builders that fully replace the WooCommerce product layout, so automatic placement works even if the builder bypasses standard hooks. The widget’s scoped CSS loads only on pages where the widget renders; there is no style bleed.

Getting started

• Output language. The language your summaries are written in. Choose any of the 43 languages in the picker. Sumzy reads reviews in any language and always writes the summary in the language you choose. This setting is available on every plan; it is never gated.
• Minimum reviews. How many approved reviews a product must have before Sumzy summarises it. Default: 5. Minimum: 5 (the backend floor). Maximum: 100. Products below the threshold are marked Not enough reviews in the Summaries screen, which is not an error, just a status.

Publishing & display

• Placement. Where the widget appears on product pages. Options: Above the reviews (default, all plans), After review list (all plans), Shortcode only Professional. See the Placement section for full details.
• Summary tone. Professional The voice of your summaries. Six options: Balanced, Concise, Friendly, Professional, Vivid, and Elegant. Essentials is fixed to Balanced; Professional and Business unlock all six. Tone changes the writing style only; it never hides or down-weights a real complaint, and every tone names real negatives.
• Approval workflow. Professional When enabled, completed summaries land in Needs approval instead of going live automatically. You approve, edit, hide, or regenerate each summary before shoppers see it. Off by default (auto-publish). If you downgrade from Professional, any un-approved summaries continue to be held and cannot be approved until the plan is restored or re-upgraded.

Widget appearance

• Appearance mode. Essentials uses the default look (warm white), which fits most stores out of the box. Professional unlocks the full set of theme presets, Light, Paper, Ink, Dark, Lumen, and Aurora, plus Custom colors. The presets match most themes automatically; Custom lets you set five widget colors.
• Custom colors. Professional When appearance mode is set to Custom, five color pickers let you set the widget background, border, heading, body text, and accent colors. Sumzy runs a WCAG AA contrast check when you save and shows a non-blocking warning if any pair misses the threshold. The save proceeds regardless; you control the final decision.
• Widget max-width. An optional CSS width cap for the widget (e.g. 720px, 48rem). Leave blank for full-width. Available on all plans.
• Remove “by Sumzy”. Business Hide the small Sumzy attribution in the widget footer. The mandatory AI-generated disclosure ([AI] pill + accessible text) is always shown regardless of this setting; it cannot be removed.

Advanced

• Remove data on uninstall. When enabled, uninstalling the plugin will delete all Sumzy database tables and options. Off by default; your summaries are preserved across updates and deactivations. Only enable this if you are permanently removing Sumzy.
• Enable debug logging. Activates verbose logging to WooCommerce → Status → Logs (source: sumzy) for 24 hours. Automatically turns off after the window expires. Logs are PII-masked; license keys, email addresses, and raw review text are never written. Use this when troubleshooting with support.

How the language is chosen

On a fresh install, Sumzy reads your store’s WordPress locale and pre-fills the Output language setting automatically. A Romanian store gets Romanian; a Japanese store gets Japanese. You can change it at any time in Sumzy → Settings → Output language. The setting applies to all summaries from that point forward; existing summaries are not changed unless you choose to regenerate them.

“Out of the box” means the translation files for all 43 languages are bundled inside the plugin ZIP and load automatically. You do not need WPML, Polylang, Loco Translate, or any other translation plugin to get a fully localised widget.

RTL scripts (Arabic, Hebrew, Farsi, Urdu) are fully supported. The widget uses CSS logical properties throughout, so layout mirrors correctly without extra configuration.

All 43 supported languages

European (Latin script)

• English
• Spanish (Español)
• French (Français)
• German (Deutsch)
• Italian (Italiano)
• Portuguese (Português)
• Dutch (Nederlands)
• Romanian (Română)
• Polish (Polski)
• Swedish (Svenska)
• Danish (Dansk)
• Norwegian (Norsk)
• Finnish (Suomi)
• Icelandic (Íslenska)
• Czech (Čeština)
• Slovak (Slovenčina)
• Slovenian (Slovenščina)
• Croatian (Hrvatski)
• Hungarian (Magyar)
• Estonian (Eesti)
• Latvian (Latviešu)
• Lithuanian (Lietuvių)
• Turkish (Türkçe)

Cyrillic

• Russian (Русский)
• Ukrainian (Українська)
• Bulgarian (Български)
• Serbian (Српски)

Greek

• Greek (Ελληνικά)

RTL (right-to-left)

• Arabic (العربية)
• Hebrew (עברית)
• Persian / Farsi (فارسی)
• Urdu (اردو)

CJK

• Chinese (中文)
• Japanese (日本語)
• Korean (한국어)

Indic & South Asian

• Hindi (हिन्दी)
• Bengali (বাংলা)
• Tamil (தமிழ்)

Southeast Asian

• Thai (ไทย)
• Vietnamese (Tiếng Việt)
• Indonesian (Bahasa Indonesia)
• Malay (Bahasa Melayu)
• Filipino (Tagalog)

The Summaries screen (Sumzy → Summaries)

The Summaries screen is a review-ops worklist. A status rail down the side both shows your counts and acts as the filter: All, Live, Needs approval, Not enough reviews, Failed, and Hidden. Pick a rail item to scope the list to that status.

Alongside the rail you have a search box (match by product name, ID, or SKU), a sentiment filter, a sort control, and a per-page control for working through a large catalog.

Summary statuses

• Live. Generated and shown on your storefront.
• Hidden. The summary exists but is not shown. You set this with the Hide action, and Show reverses it.
• Needs approval. Generated and waiting for you to approve it before it goes live. Only appears when the approval workflow is on.
• Generating… The summary is being created or updated in the background.
• Failed. Sumzy could not generate the summary. It shows a reason and can be retried.
• Not enough reviews. The product has fewer approved reviews than your minimum-reviews threshold. This is a status, not an error.
• Outdated. Newer approved reviews arrived since the summary was generated. This is a derived view, not a stored status: the current summary can keep showing, or you can regenerate it to fold in the new reviews.

Row actions

• View product. Open the product on your storefront.
• Edit summary. Professional Edit the summary text inline. Saving pins the edit.
• Approve. Move a summary from Needs approval to Live. Available when the approval workflow is on.
• Hide / Show. Hide removes the summary from the storefront without deleting it, so the widget shows nothing for that product. Show puts it back. Hidden is a real saved status, not a one-off toggle.
• Regenerate. Discard the current summary and queue a fresh generation. Any pinned manual edits are cleared. If the product had hit the automatic-retry cap after repeated failures, Regenerate resets that budget.
• Reset to AI. Clear a pinned manual edit and return the product to the AI-generated summary.
• Remove. Delete the stored summary for that product.
• Retry failed. Re-queue a product that is in the Failed status.

Bulk actions

• Regenerate, Hide, Show. Apply to every selected row at once.
• Regenerate all failed / Clear all failed. Available on the Failed view. Regenerate all failed re-queues every failed product; Clear all failed resets them so the next background check can retry them.

Selecting any row opens a detail drawer with the full summary, its status, and the actions above, so you can review and act without leaving the list.

The per-product meta box

On any WooCommerce product edit screen you will find a Sumzy Summary meta box in the sidebar. It shows the current summary status, the summary text (when live), and the same Approve / Hide / Regenerate actions. You can also edit the summary text directly in the meta box.

Pinned manual edits

If you edit a summary text in the meta box and save it, the summary is pinned. A pinned summary is never overwritten by automatic refresh, review changes, or the periodic sweep. The pin is shown in the meta box. Click Regenerate to clear the pin and return the product to fully automatic operation.

Editing is intended for correcting wording or adding context, not for removing or softening real recurring complaints. Summaries that misrepresent what customers actually said are inconsistent with Sumzy’s honest-representation guarantee and with consumer-protection rules.

When summaries update

An existing summary is refreshed when:

• A new review is approved on the product.
• An existing review is edited.
• A review is deleted.
• You change the output language or summary tone and regenerate.
• You click Regenerate.
• A periodic background check finds the review set has changed.

Manual edits are pinned and are not overwritten automatically. Use Regenerate (or Reset to AI) to clear a pin and return the product to automatic.

The Failed view

Products in the Failed status show a plain-English message describing what went wrong and a suggested next step. See the Troubleshooting section for a full list of error codes. Use Clear all failed to bulk-reset them and let the next background check retry them.

Stuck generations

Sumzy detects generations that have been stuck for an extended period, which typically means a background worker failed to fire. These are moved to Failed automatically on the next background check, so they stop showing a permanent “Generating…” spinner and become retryable. If you see this on a healthy store it usually means WP-Cron is not running reliably; see the Troubleshooting section.

Every plan includes a 14-day free trial (credit card required, cancel any time during the trial and you pay nothing), subject to fair use. Plan pricing, a full feature comparison, and trial details are on the pricing page, which is the single source of truth and is always up to date.

What happens on lapse

• While your subscription is active, including any paid-through period after cancelling and any dunning grace window on a failed payment, your summaries display normally.
• On a full lapse, Sumzy stops displaying summaries on your storefront and stops generating new ones.
• Your stored summaries are not deleted. They display again if you reactivate the subscription.
• A temporary backend outage does not remove summaries, because the widget renders from local data.

Billing, invoices, and payment updates are managed at sumzy.io/account (via Freemius, Sumzy’s Merchant of Record). Sumzy never stores your payment details.

What Sumzy sends to its backend

For each product being summarised, Sumzy sends the following fields to the Sumzy backend (api.sumzy.io) via HTTPS from a background job, never from a shopper page load:

• The product ID (a numeric reference, not the product name or URL)
• Each review’s star rating (1 to 5)
• Each review’s text content
• A coarse recency band derived from the review date (one of: recent, older, historical), never the exact date
• Your configured output language and summary tone

Sumzy does not send: reviewer names, reviewer email addresses, IP addresses, the exact review date, the product title or URL, the verified-purchase flag, billing or shipping addresses, order data, or any other customer-identifying information. The plugin assembles the payload from review text and rating only; none of those fields are ever included.

What Sumzy stores on your server

The generated summary text, sentiment, and theme labels are stored in a local wp_sumzy_summaries table in your WordPress database. Raw review text is not stored in this table; only the AI-generated output is kept.

AI disclosure

Every summary on your storefront is clearly labelled as AI-generated. The widget shows a visible [AI] pill and includes a screen-reader accessible phrase (“AI-generated summary”) so assistive technology announces the AI authorship correctly. This disclosure cannot be removed, even on the Business plan with branding removal enabled.

GDPR & regional compliance

Because Sumzy processes review text on its backend (as a data processor), you should reference Sumzy in your privacy policy as a subprocessor if required by your applicable data protection regulations. Sumzy provides a Data Processing Addendum (DPA) for stores that need one.

See also: Privacy Policy · Data Processing Addendum · Subprocessors

Tools → Site Health

Go to Tools → Site Health → Status. Sumzy adds five checks to the background tests:

• Backend connection. Reports whether the last generation attempt saw a subscription or license issue.
• License / entitlement. Checks whether your license is active and the plan is correctly registered.
• WooCommerce product reviews. Confirms that product reviews are enabled and that WooCommerce is active.
• Action Scheduler queue. Reports the backlog of pending generation jobs. A very large backlog may mean WP-Cron is running too slowly or not at all.
• WP-Cron / background processing. Checks whether WP-Cron is running. If DISABLE_WP_CRON is defined, this test reminds you to set up a server cron.

Widget not showing on a product

Work through this checklist in order:

• Does the product have at least as many approved reviews as your Minimum reviews setting (default: 5)?
• Is the product’s summary status Live in Sumzy → Summaries? If it shows Not enough reviews, add more reviews. If it shows Failed, see the error codes below.
• Is your license active? Go to Sumzy → Account and confirm the license status.
• Are product reviews enabled in WooCommerce? Check WooCommerce → Settings → Products → Enable product reviews.
• If you are on the Essentials plan, is the placement set to Above the reviews or After review list? Shortcode-only requires Professional.
• If using the shortcode or block, is it actually present on the product page template?
• Is a page caching plugin (WP Rocket, LiteSpeed Cache, etc.) serving a stale page? Purge the cache for that product page and reload.
• Check Tools → Site Health for any Sumzy-specific warnings.

A summary is not updating

• Summaries update automatically when reviews change, but there is a short debounce delay before a new generation job fires. Wait a minute and reload.
• Is the summary pinned (manually edited)? A pinned summary is never overwritten automatically. Use Regenerate in the meta box to unpin it.
• Is WP-Cron running? If your server has DISABLE_WP_CRON set in wp-config.php, ensure a proper server cron is configured to call wp-cron.php.

A summary shows as Outdated

Outdated means newer approved reviews arrived after the summary was generated. It is not an error: the current summary can stay live as-is, or you can regenerate it to fold in the new reviews. To refresh it:

• Go to Sumzy → Summaries.
• Filter to Outdated.
• Open the product and click Regenerate.

Error codes explained

• no_reviews - No approved reviews were found for this product when generation ran. Add approved reviews and regenerate.
• backend_unreachable - The Sumzy API could not be reached (DNS, timeout, or connection refused). Retries happen automatically. If persistent, check your server’s outbound HTTPS connectivity.
• backend_timeout - The generation job was submitted but the backend worker did not respond within the polling window. Use Regenerate to retry.
• ai_parse_failure - The backend could not produce a clean summary for this product (malformed AI output or format mismatch). Use Regenerate. If it repeats, contact support with the reference ID shown.
• rate_limited - Too many requests in a short window. Sumzy’s automatic backoff will retry. Wait a few minutes, then use Regenerate if needed.
• limit_reached - Your plan's summary generation limit was reached. This error applies to older plugin versions only. Current paid plans have unlimited generation. If you see this, update your plugin to version 1.11.0 or later.
• trial_limit_reached - Your trial summary quota is exhausted. Upgrade to a paid plan to continue.
• subscription_canceled - The subscription has lapsed or been cancelled. Visit sumzy.io/account to resubscribe.
• license_invalid - The license is absent, expired, or otherwise not entitled. Visit sumzy.io/account to reactivate.
• cache_stale - The license status has not synced yet. This usually clears on its own within a few minutes; use Regenerate to retry.
• account_paused - Generation is on hold for this account. Contact support to restore it.
• unknown - Something unexpected went wrong. Use Regenerate to retry. If it persists, contact support with the reference ID.

Support report

On the Settings screen, a Copy support report button generates a sanitised snapshot of your Sumzy configuration (plugin version, license status, summary counts, scheduler state, PHP/WP versions). The report never contains your license key, review text, or customer data. Paste it into a support ticket so our team can diagnose faster.

Debug log

Go to Sumzy → Settings → Advanced and enable debug logging. This activates verbose logging to WooCommerce → Status → Logs (filter source: sumzy) for 24 hours, then auto-disables. The log is PII-masked: license keys, email addresses, and raw review content are never written.

Themes

Sumzy works with any WooCommerce-compatible theme out of the box. The list below covers themes we have confirmed directly; the wp_footer fallback means the widget appears even on themes we have not listed.

• Storefront. Fully compatible. The default WooCommerce theme; automatic placement works as expected.
• Astra. Fully compatible with both the free and Pro versions.
• Block / FSE themes. Compatible. Sumzy uses a dedicated block-theme injection path (render_block filter) that prepends the widget before the woocommerce/product-details or woocommerce/product-reviews block.
• Flatsome. Compatible. Sumzy uses the comments_template filter at priority 11, which fires reliably on Flatsome regardless of how the reviews section is built.
• Woodmart. Compatible, including Woodmart’s Elementor-based product page builder. Woodmart calls comments_template() directly; Sumzy’s priority-11 filter intercepts it correctly.
• Avada. Compatible via the same comments_template priority-11 technique.
• Any other theme. The wp_footer fallback ensures the widget renders correctly even on themes that bypass both the standard WooCommerce tab callback and the comments_template flow.

Page builders

Sumzy works with any page builder, guaranteed by the wp_footerfallback that covers builders which fully replace the WooCommerce product layout. In addition, native drop-in widgets are available for the builders below, so you can place the summary directly from your builder’s panel rather than using the shortcode.

• Elementor. A native Sumzy Summary widget is available in the Elementor panel. Drag it onto your product template. Automatic placement also works on standard Elementor WooCommerce templates.
• Gutenberg / block editor. A native sumzy/summary block is available in the block inserter. Use it in a WooCommerce product template or any block-editor context. Pin a product to see a live preview of that product’s real summary while editing.
• Divi. A native Sumzy Summary module is available in the Divi builder. You can also use the shortcode [sumzy_summary] in a Code module.
• Bricks. A native Sumzy Summary element is available in Bricks Builder. Automatic placement via wp_footer also works on any Bricks product template.
• Beaver Builder. A native Sumzy Summary module is available in Beaver Builder. Automatic placement via wp_footer also works on standard Beaver Builder product page layouts.
• WPBakery. A native Sumzy Summary shortcode element is available in WPBakery. Automatic placement via wp_footer also covers WPBakery product pages.
• Any other builder. Use the shortcode [sumzy_summary] in any shortcode-accepting widget, or rely on automatic placement, which works via wp_footer regardless of which builder powers the product page.

HPOS (High-Performance Order Storage)

Sumzy declares HPOS compatibility. It does not read or write WooCommerce order tables; HPOS has no effect on summary generation or display.

Page caching

• WP Rocket. Compatible. The widget is rendered server-side into the page HTML; there is no dynamic JavaScript data fetch that caching would break. If a new summary is generated while a page is cached, clear the cache for that product page to show the updated widget immediately.
• LiteSpeed Cache. Compatible, same approach as WP Rocket.
• Other full-page caches. Compatible. Sumzy’s widget is static HTML injected server-side; full-page caching works normally. Purge product page caches after a summary is regenerated if you need the update to appear immediately.

Browsers

The widget uses standard HTML, CSS custom properties, and no JavaScript. It displays correctly in all modern browsers (Chrome, Firefox, Safari, Edge). On older Safari versions (pre-2020) that do not support color-mix(), theme chip tint colors gracefully degrade to the base chip style; content and proportionality remain fully intact.

Manual placement using a native module, the shortcode, or the Gutenberg block is available on the Professional plan and above. On Essentials, Sumzy places the summary automatically using standard WooCommerce hooks and the universal floor placement, which runs at the page footer level and catches layouts where the builder bypasses the standard hooks.

Using the shortcode with any builder

The shortcode [sumzy_summary] works in any builder’s shortcode or code widget on the Professional plan and above. Pass product_id (optional, defaults to the current post) and heading (optional, e.g. h3) to match your template hierarchy.

Will the summary show up twice?

No. Sumzy checks whether you have placed the widget manually. If you have, automatic placement is suppressed and the summary shows exactly once, in the spot you chose. If you have not placed it manually, Sumzy places it automatically using one of the standard WooCommerce hooks.

Does the summary load from an API call on page load?

No. The summary is stored in your own WordPress database and rendered locally. Sumzy’s servers are not contacted on page load, so the widget is fast and works even if the backend service is temporarily unavailable.

What this covers

This guide explains how to edit the widget’s fixed labels: headings, labels, section titles, and the AI disclosure phrase. These are the WordPress translation strings that Loco Translate handles.

The AI summary text itself (the summary paragraph, the sentiment label, and the theme chips) comes from the Sumzy backend and is generated in whichever output language you have set in Sumzy → Settings → Output language (see the Settings reference). Those strings are not in the plugin translation files and cannot be edited with Loco Translate.

The visible [AI] pill is a brand mark and is intentionally not translated.

Step-by-step: editing translations with Loco Translate

• Install Loco Translate. In your WordPress admin go to Plugins → Add New, search for Loco Translate, install, and activate it. Loco Translate is free and published by Tim Whitlock.
• Open the Sumzy translation. Go to Loco Translate → Plugins. Find Sumzy in the list and click it.
• Create a new language or open an existing one. If your language is not listed yet, click New language, choose your locale from the dropdown, and continue. Loco Translate automatically loads Sumzy’s bundled sumzy.pot template, which lists every translatable string in the plugin. If your language is already listed, click it to open the editor.
• Translate the strings. The Loco editor shows the original English string on the left and a text field for your translation on the right. Click any string, type your translation, and move to the next. You can search for a specific string using the filter box.
• Save. Click the Save button. Loco Translate compiles your strings and writes the translation files.

Checking your work

After saving, load a product page on your storefront and confirm the widget strings reflect your changes. If you do not see them, clear your page cache (if you use a caching plugin) and reload.

The AI summary text and output language

Loco Translate handles the fixed widget labels only. If you want the AI-generated summary text itself (the paragraph, the sentiment label, the theme names) to appear in a different language, change the Output language setting in Sumzy → Settings and re-generate your summaries. See the Settings reference for details.

Filters

• sumzy_should_render_summary - ( bool $should, int $product_id ). Return false to suppress the widget for a specific product without touching placement settings. Checked after the entitlement gate; a returning true cannot bypass plan-level gating, only suppress rendering.
  Example: hide the widget on products in a specific category.
• sumzy_summary_text - ( string $summary, int $product_id, array $result ). Filter the summary text before it is output. Use to localise, truncate, or add custom framing. The returned string is always passed through esc_html(); do not emit raw HTML through this filter.
• sumzy_frontend_wrapper_classes - ( string[] $classes, int $product_id ). Filter the CSS classes on the widget’s root <div>. The base class sumzy-summary is always present. All returned classes are sanitised with sanitize_html_class() before reaching the DOM.
• sumzy_review_payload_before_send - ( array $reviews, int $product_id ). Filter the review payload just before it is sent to the backend. Use to integrate an alternative review provider or enrich with additional metadata. Each entry must remain in the contract shape: [ 'text' => string, 'rating' => int, 'recencyBand' => string ]. Never add PII (names, emails, IPs) to this payload.
• sumzy_settings_capability - ( string $cap ). Filter the WordPress capability required to access the Sumzy Settings page. Default: manage_options. Return a different capability to remap who can access settings without modifying the plugin.
• sumzy_manage_capability - ( string $cap ). Filter the capability required to access the Sumzy Summaries management screen. Default: manage_woocommerce. Allows Shop Managers access to manage summaries separately from general settings.
• sumzy_allow_dev_backends - ( bool|null $override ). Return true to allow non-allowlisted backend URLs (e.g. a local development deployment). Must never be used on production. Controlled via the SUMZY_ALLOW_DEV_BACKENDS constant (see below) or this filter.
• sumzy_backend_url - ( string $base_url ). Filter the backend base URL. The value is allowlisted by the URL guard; arbitrary internal hosts are rejected unless sumzy_allow_dev_backends is truthy. Default: https://api.sumzy.io. Prefer the SUMZY_BACKEND_URL constant for static overrides.

Actions

• sumzy_after_summary_generated - ( int $product_id, array $result ). Fires after a summary is successfully persisted to the database. $result is the full decoded SummaryResult payload. Use this to bust a product page cache, trigger a webhook, or update a search index. Only fires when the write actually succeeded; a malformed/oversized payload that fails to persist does not fire this action.
  Example: add_action( 'sumzy_after_summary_generated', function( $product_id, $result ) { // purge cache }, 10, 2 );

Template tag

• sumzy_summary( int $product_id = null ): void - Renders the widget for a product. Defaults to the current post ID. Returns nothing (echoes directly). Safe to call from any template file on a product page; degrades silently to no output when the product has no published summary or the store is not entitled.

Kill-switch constants

Define these in wp-config.php for operational control. All are opt-in (no effect unless defined truthy).

• SUMZY_DISABLE_FRONTEND_WIDGET - Disables all automatic and manual widget output site-wide. Product pages are unaffected in every other way. Use during maintenance or to temporarily suppress the widget while investigating a display issue.
  define( 'SUMZY_DISABLE_FRONTEND_WIDGET', true );
• SUMZY_DISABLE_AUTO_REGEN - Halts all automatic summary generation: the periodic refresh sweep and per-review debounce triggers. Manual Regenerate (from the admin UI) is unaffected and remains the only way to trigger new generation while this constant is set.
• SUMZY_DISABLE_BACKFILL - Prevents the first-run backfill from enqueueing new jobs. Useful on a staging clone of a production database where you do not want to trigger real API calls.
• SUMZY_DISABLE_BACKEND_DRAIN - Disables the backfill fast-drain call (the backend-accelerated batch drain triggered during the backfill progress polling). The backfill itself still works via standard Action Scheduler.
• SUMZY_DISABLE_DASHBOARD_LINKS - Hides the Sumzy account dashboard deep-links in the WordPress admin (the links to the per-license account view). Has no functional effect on generation or display.
• SUMZY_ALLOW_DEV_BACKENDS - Allows the sumzy_backend_url filter or SUMZY_BACKEND_URL constant to be set to a non-allowlisted URL (e.g. http://localhost:3000). Never define this on a production site.
• SUMZY_BACKEND_URL - Override the backend base URL in code. Takes precedence over the sumzy_backend_url filter. Useful for pointing a staging environment at a staging backend.
  define( 'SUMZY_BACKEND_URL', 'https://staging-api.sumzy.io' );

Will Sumzy slow down my store?

No. The widget renders from a local database table. There is no API call on a shopper’s product page load; the Sumzy backend is never in the critical path for a page render. Even if the Sumzy backend is entirely unreachable, your product pages load at their normal speed and display whatever summary is already stored locally.

What data leaves my site?

For each product being summarised, Sumzy sends the following (from a background job, never from a shopper page load):

• The product reference ID (numeric)
• Each review’s star rating
• Each review’s text content
• A coarse recency band derived from the review date (recent / older / historical)
• Your configured output language and tone

Reviewer names, email addresses, IP addresses, the exact review date, the product title, the verified-purchase flag, billing and shipping data, and order information are never sent.

Does Sumzy hide negative reviews or spin the summary?

No.Sumzy is built around proportional, honest representation. A complaint that genuinely recurs in your reviews will always appear in the summary. The proportion indicators (one mention / a few mention / many mention) ensure a minority complaint reads as a minority complaint rather than a majority problem, but it is never silently buried. Sumzy does not offer a “positive-only” mode, and such a mode will never be added. Hiding real recurring complaints would make Sumzy a deceptive-marketing tool; that is not what it is.

Can I edit a summary?

Yes, on the Professional plan and above. Open the product in WooCommerce, find the Sumzy Summary meta box, and edit the text directly. Save the product to pin your edit. The summary will not be overwritten by automatic regeneration while it is pinned. Use Regenerate in the meta box to clear the pin and return to automatic.

Which themes and page builders does Sumzy work with?

Sumzy works with any WooCommerce-compatible theme and any page builder. A wp_footer fallback ensures the widget renders correctly even when a builder or theme fully replaces the standard WooCommerce product layout. Native widgets are available for Elementor, Divi, Bricks, Beaver Builder, WPBakery, and the Gutenberg block editor. See the Compatibility section for details.

Can I use Sumzy with WPML or Polylang?

You can set a single output language for your store on any plan, choosing from 43 built-in languages. The Business plan adds per-shopper multilingual output, where each visitor sees the summary in their own language on a WPML or Polylang multilingual store. See the Supported languages section for the full list.

My store has thousands of products. Will Sumzy cover all of them?

Yes, progressively. Sumzy’s periodic refresh sweep advances through your catalog using a cursor, so each sweep covers a window of products and successive sweeps advance further. Large catalogs are covered over time rather than all at once. Products with the most recent review activity are always prioritised by the debounce trigger.

What happens to my summaries if I cancel?

When a subscription is active, including the period you have already paid for after cancelling and the dunning window on a failed payment, your summaries display normally. Once it fully lapses, Sumzy stops generating new summaries and the storefront widget stops displaying them. Your summaries remain in your local database and are never automatically deleted; they reappear if you reactivate. Only a manual uninstall with the “Remove data on uninstall” option enabled will delete them.

Does Sumzy require me to set up AI keys?

No. You do not bring your own OpenAI, Anthropic, or other AI key. Sumzy’s backend handles all AI processing. Your store connects only via a Freemius license key.

Is Sumzy compatible with HPOS?

Yes. Sumzy declares HPOS compatibility and does not read or write WooCommerce order tables. You can enable HPOS without any effect on Sumzy’s operation.

Will summary generation slow down my admin?

No. All generation happens via Action Scheduler background jobs that run outside of normal page requests. The wp-admin UI is unaffected. The only admin-visible activity is the progress bar while you generate your first summaries, which is opt-in.

When a shopper lands on a product page, the Sumzy widget shows a short summary, an overall sentiment signal (Mostly positive, Mixed reviews, or Mostly negative), ranked aspect chips with proportion indicators (one, a few, or many mentions), and an at-a-glance verdict header with average rating and review count. Every feature that recurs in reviews surfaces, whether positive or negative.

Summaries are generated asynchronously in the background. The widget reads from a Shopify metafield stored on the product; there is no API call to the Sumzy backend on page load. Your product pages stay fast and intact even if the backend is temporarily unreachable.

Every summary is clearly labelled as AI-generated, both visually (an [AI] pill) and in accessible text for screen readers. Recurring complaints surface at the same threshold as praise; Sumzy does not hide, omit, or skip themes that genuinely recur in the review data.

Features such as approval workflow, tone control, and per-shopper multilingual summaries depend on which plan is active; see what each plan includes.

• Shopify store. Any Shopify plan. Online Store channel required (the widget is a theme app extension).
• A review app. Sumzy reads reviews from Judge.me. Judge.me is free and widely used; it works out of the box. Support for Loox, Yotpo, Okendo, and Stamped is on the roadmap.
• Online Store 2.0 theme. The widget is a theme app block added via the Shopify theme editor. Any Online Store 2.0 theme supports app blocks. Vintage themes are not supported.

Installing from the App Store

• Go to the Sumzy listing on the Shopify App Store and click Install.
• Shopify asks you to approve the permissions Sumzy needs. Click Install to confirm. Sumzy is added to your store.
• The Sumzy onboarding wizard opens in your Shopify Admin. Follow the steps: choose a plan, connect your review app, configure your language, and add the widget to your theme.

Choosing a plan and trial

Every plan includes a 14-day free trial (credit card required via Shopify Billing; cancel any time during the trial and you pay nothing). Select the plan that fits your store in the onboarding wizard or in Shopify Admin → Apps → Sumzy → Billing.

• Billing is handled entirely by Shopify. Sumzy never stores your payment details. Your subscription appears on your standard Shopify bill.
• Plan prices are displayed excluding VAT. Shopify (Merchant of Record) adds and remits VAT at checkout where required.

Adding the widget to your theme

After install, Sumzy prompts you to add the widget block to your product page template:

• In the onboarding wizard, click Add to your theme. This opens the Shopify theme editor on your product template.
• In the theme editor, click Add block in the product page sections and select Sumzy Review Summary. Drag it to the position you prefer.
• Click Save. The widget is now live on your product pages.

• Install and subscribe (see Install above). The onboarding wizard guides you through the remaining steps.
• Choose your language and tone. In the onboarding wizard, or later in Shopify Admin → Apps → Sumzy → Settings, set the output language and the summary tone. Sumzy reads reviews in any language and always writes the summary in the language you choose.
• Generate your first summaries. The wizard prompts you to kick off the first sync. Click Generate summaries now. Sumzy queues your eligible products in the background and shows you a progress indicator. Products with fewer than your minimum-reviews threshold are skipped and summarised as reviews accumulate.
• Add the widget block to your theme (see Install above). Once the block is in place and summaries are generated, shoppers see the widget on every product page that has enough reviews.

Metafield render, zero page-load API calls

The widget reads from a Shopify product metafield (app--388011163649.summary) that Sumzy writes after each generation. There is no call to the Sumzy API on a shopper’s product page load. The Sumzy backend can be unreachable and your product pages remain fast; the metafield data is served by Shopify’s CDN alongside the rest of the page.

Background generation

Sumzy polls your Judge.me reviews in the background on a regular schedule. When new reviews arrive or an existing review changes, Sumzy queues a regeneration job. The job gathers the product’s reviews, sends them to the Sumzy backend, receives a result, and writes the summary back to the product metafield. Shoppers never wait for it.

Debounce coalescing

A short debounce window coalesces review bursts so a sudden wave of new reviews produces one generation job, not dozens. The debounce resets if further changes arrive before the job fires.

Review changes trigger regeneration

A new review published or updated on Judge.me triggers a debounced regeneration for that product. You do not need to wait for a periodic sweep to pick up a significant review change.

Theme app block

Available on all plans.

The Sumzy Review Summaryblock is available in the Shopify theme editor under your product page template. Add it, drag it to any position within the product template, and save. The block renders the widget using your theme’s fonts and text color, so it blends naturally with your existing design.

To access the theme editor: in your Shopify Admin go to Online Store → Themes, click Customize on your active theme, navigate to the product page template, and add the Sumzy block.

Theme appearance

The widget has three themes selectable in the block settings panel in the theme editor:

• Adapt to my store (default). The widget inherits your theme’s font family, font size, and text color. Neutral surfaces derive from currentColor. The widget blends with any theme automatically.
• Sand. A warm card style with a light beige background.
• Ink. A dark card with lifted semantic colors for the sentiment and chips.

An accent color picker in the block settings lets you match your store’s primary brand color.

General

• Output language. The language your summaries are written in. Choose any of the 43 supported languages. Sumzy reads reviews in any language and always writes the summary in your chosen language. Available on every plan; never gated.
• Minimum reviews. How many published reviews a product needs before Sumzy summarises it. Default: 5. Products below the threshold appear as Not enough reviews in the dashboard.
• Verdict header.Show or hide the at-a-glance average rating and review count at the top of the widget. On by default. This is a display-only setting and never affects JSON-LD structured data (Sumzy never emits AggregateRating schema, to avoid duplicating your review app’s schema).

Publishing & display

• Summary tone. Professional The voice of your summaries. Six options: Balanced, Concise, Friendly, Professional, Vivid, and Elegant. Essentials is fixed to Balanced; Professional and Business unlock all six.
• Approval workflow. Professional When enabled, completed summaries land in Needs approval instead of going live automatically. You approve, edit, hide, or regenerate each summary before shoppers see it.

Widget appearance

• Theme and accent. Set in the Shopify theme editor block settings panel, not here. See the Placement section.
• Appearance presets. Professional Unlocks the Sand and Ink themes in the block settings. Essentials is fixed to Adapt to my store.
• Remove “by Sumzy”. Business Hide the small Sumzy attribution in the widget footer. The mandatory AI-generated disclosure ([AI] pill + accessible text) is always shown regardless of this setting.

Multilingual (Shopify Markets)

• Per-shopper multilingual. Business When enabled, Sumzy generates a separate summary for each active locale in your Shopify Markets setup. Each shopper sees the summary in their active locale. Your default-language summary is generated up front; each additional locale is generated on demand the first time a shopper views it in that locale, then kept fresh. Only locales enabled in Shopify Markets are generated.

Single-language stores

Set your Output language in Shopify Admin → Apps → Sumzy → Settings. Sumzy reads reviews in any language and writes every summary in your chosen language. All 43 supported languages are available on every plan.

Multilingual stores (Shopify Markets)

On the Business plan, enable Per-shopper multilingual in Settings. Sumzy detects your active Markets locales and generates a summary for each one. Shoppers see the summary in their active locale automatically. Locales not enabled in Shopify Markets are never generated, so your generation usage scales with the locales you actually serve.

RTL scripts (Arabic, Hebrew, Farsi, Urdu) are fully supported. The widget uses CSS logical properties throughout.

All 43 supported languages

European (Latin script)

• English
• Spanish (Español)
• French (Français)
• German (Deutsch)
• Italian (Italiano)
• Portuguese (Português)
• Dutch (Nederlands)
• Romanian (Română)
• Polish (Polski)
• Swedish (Svenska)
• Danish (Dansk)
• Norwegian (Norsk)
• Finnish (Suomi)
• Icelandic (Íslenska)
• Czech (Čeština)
• Slovak (Slovenčina)
• Slovenian (Slovenščina)
• Croatian (Hrvatski)
• Hungarian (Magyar)
• Estonian (Eesti)
• Latvian (Latviešu)
• Lithuanian (Lietuvių)
• Turkish (Türkçe)

Cyrillic

• Russian (Русский)
• Ukrainian (Українська)
• Bulgarian (Български)
• Serbian (Српски)

Greek

• Greek (Ελληνικά)

RTL (right-to-left)

• Arabic (العربية)
• Hebrew (עברית)
• Persian / Farsi (فارسی)
• Urdu (اردو)

CJK

• Chinese (中文)
• Japanese (日本語)
• Korean (한국어)

Indic & South Asian

• Hindi (हिन्दी)
• Bengali (বাংলা)
• Tamil (தமிழ்)

Southeast Asian

• Thai (ไทย)
• Vietnamese (Tiếng Việt)
• Indonesian (Bahasa Indonesia)
• Malay (Bahasa Melayu)
• Filipino (Tagalog)

The Summaries dashboard (Shopify Admin → Apps → Sumzy)

The dashboard shows all your products with a status indicator: Live, Needs approval, Not enough reviews, Generating, Failed, or Hidden. Filter by status, search by product name, and page through large catalogs.

Clicking a product row opens a detail panel with the full summary text and the available actions.

Row actions

• View on storefront. Open the product on your live store.
• Edit summary. Professional Edit the summary text. Saving pins the edit so automatic regeneration will not overwrite it.
• Approve. Move a summary from Needs approval to Live. Available when the approval workflow is on.
• Hide / Show. Remove or restore a summary from the storefront without deleting it.
• Regenerate. Queue a fresh generation for this product. Clears any pinned manual edit.

When summaries update

An existing summary is refreshed when:

• A new review is published or updated in Judge.me.
• You change the output language or summary tone and regenerate.
• You click Regenerate.
• A periodic background sync finds the review set has changed.

Pinned manual edits are never overwritten automatically. Use Regenerate to clear a pin.

Every plan includes a 14-day free trial (credit card required via Shopify Billing, cancel any time and pay nothing). Plan pricing and a full feature comparison are on the pricing page.

Billing and account

Billing is managed entirely by Shopify. Go to Shopify Admin → Apps → Sumzy → Billing to see your current plan, switch plans, or cancel. Your subscription appears on your standard Shopify invoice; Sumzy never stores your payment details.

What happens on lapse

• While your subscription is active, including any paid-through period after cancelling and any dunning grace window, your summaries display normally.
• On a full lapse, Sumzy stops displaying summaries on your storefront and stops generating new ones.
• Your stored summaries are not deleted. They display again if you reactivate.

What Sumzy sends to its backend

For each product being summarised, Sumzy sends the following fields to the Sumzy backend (api.sumzy.io) via HTTPS from a background job, never from a shopper page load:

• A product reference (the Shopify product GID)
• Each review’s star rating (1 to 5)
• Each review’s text content
• A coarse recency band derived from the review date (recent, older, or historical), never the exact date
• Your configured output language and summary tone

Sumzy does not send: reviewer names, reviewer email addresses, IP addresses, the exact review date, the product title or URL, any order data, or any other customer-identifying information.

What Sumzy stores

The generated summary text, sentiment, and theme labels are stored as a Shopify product metafield. Raw review text is not stored; only the AI-generated output is kept.

AI disclosure

Every summary is clearly labelled as AI-generated: a visible [AI] pill and an accessible screen-reader phrase. This disclosure cannot be removed, even on the Business plan with branding removal enabled.

GDPR & regional compliance

Because Sumzy processes review text as a data processor, you should reference Sumzy in your privacy policy as a subprocessor if required by your applicable data protection regulations. Sumzy provides a Data Processing Addendum (DPA) for stores that need one.

See also: Privacy Policy · Data Processing Addendum · Subprocessors

Widget not showing on a product

• Is the Sumzy block added to your product page template in the theme editor? See the Placement section.
• Does the product have at least as many published reviews as your Minimum reviews setting (default: 5)?
• Is the product’s summary status Live in the Sumzy dashboard? Check Shopify Admin → Apps → Sumzy.
• Is your subscription active? Check Shopify Admin → Apps → Sumzy → Billing.
• Is Judge.me installed and has it synced reviews to your store?

A summary is not updating

• There is a short debounce delay after a review change before a new generation job fires. Wait a minute and reload.
• Is the summary pinned (manually edited)? A pinned summary is never overwritten automatically. Use Regenerate in the dashboard to unpin it.

Error codes

• no_reviews - No eligible reviews were found. Ensure Judge.me has published reviews for this product.
• backend_unreachable - The Sumzy API could not be reached. Retries happen automatically.
• ai_parse_failure - The backend could not produce a clean summary. Use Regenerate. If it repeats, contact support with the reference ID shown.
• rate_limited - Too many requests in a short window. Sumzy’s automatic backoff will retry.
• trial_limit_reached - Your trial quota is exhausted. Upgrade to a paid plan to continue.
• subscription_canceled - The subscription has lapsed or been cancelled. Resubscribe via Shopify Admin → Apps → Sumzy → Billing.

Themes

Sumzy works with any Online Store 2.0 theme that supports app blocks (all themes built after 2021 do). The widget inherits your theme’s font family, font size, and text color in Adapt mode, so it blends naturally without any CSS customization. Vintage (non-2.0) themes are not supported.

Review apps

• Judge.me. Fully supported. Sumzy reads Judge.me reviews directly via the Judge.me public API. Judge.me is free and works out of the box.
• Loox, Yotpo, Okendo, Stamped. Support is on the roadmap. Sumzy is designed with an adapter seam so adding each provider requires a single adapter file, not an architecture change. Timeline depends on owner availability to provide real-payload API credentials for contract-first development.

Shopify Markets (multilingual)

Sumzy’s Business plan generates a separate summary per active Shopify Markets locale. All locales you have enabled in Shopify Markets are covered. You do not need any additional translation apps; Sumzy generates the summary text directly in each locale’s language.

Will Sumzy slow down my store?

No. The widget reads from a product metafield served by Shopify’s CDN alongside the rest of the page. There is no API call to the Sumzy backend on page load. The Sumzy backend can be entirely unreachable and your product pages load at their normal speed.

Which review app do I need?

Sumzy currently works with Judge.me, which is free and the most widely used review app on Shopify. Support for Loox, Yotpo, Okendo, and Stamped is on the roadmap.

Does Sumzy work with Shopify Markets?

Yes, on the Business plan. Enable Per-shopper multilingual in Settings and Sumzy generates summaries for each locale you have active in Shopify Markets. Shoppers see the summary in their active locale automatically.

Does Sumzy hide negative reviews or spin the summary?

No.Sumzy applies the same threshold to negative themes as to positive ones. A complaint that genuinely recurs in your reviews will always appear in the summary. There is no “positive-only” mode, and such a mode will never be added.

Can I edit a summary?

Yes, on the Professional plan and above. In the Sumzy dashboard, open any product and click Edit summary. Saving pins the edit so automatic regeneration will not overwrite it. Use Regenerate to clear the pin and return to the AI-generated version.

What happens to my summaries if I cancel?

While your subscription is active, your summaries display normally. Once it fully lapses, Sumzy stops displaying summaries and stops generating new ones. Your stored metafield data is not deleted; summaries reappear if you resubscribe.

Does Sumzy require me to set up AI keys?

No. You do not bring your own OpenAI, Anthropic, or other AI key. Sumzy’s backend handles all AI processing. Your store connects only via your Shopify subscription.

Where do I manage billing?

In Shopify Admin → Apps → Sumzy → Billing. Billing is handled entirely by Shopify; your subscription appears on your standard Shopify invoice.