SayIn5 — Simple Product Reviews

Description

SayIn5 helps small WooCommerce stores collect, approve and display product reviews without a separate SayIn5 account. Reviews remain on the merchant’s WordPress site. This is an early testing release.

Includes 10 free looks, three display formats, order-specific review forms and optional consent-based invitations through the existing WordPress mailer.

Requirements

WordPress 6.5 or newer; PHP 8.0 or newer; WooCommerce active. PHP mbstring is required for nickname and review text processing. Photos additionally require OpenSSL and either GD or Imagick. Test on staging first. Traditional product review tabs are supported by the current integration; custom/block-only templates are not universally verified.

Included

10 free looks; cards, quote and slider formats; light/dark/accent settings.
One private form per completed order; partial item submissions; optional ratings; optional text; a rating or text required per selected item.
Optional up to 3 JPG/PNG/WebP images per review. GD or Imagick plus OpenSSL required for photos. Server resizes to at most 1600px and compresses to at most 500 KiB; 10 MiB/24MP original limits.
All submissions wait for manual approval, regardless of rating. Nickname defaults to masked first name. New reviews use native WooCommerce comments and rating metadata.
Photos are encrypted at rest in this store’s uploads and served through an approval-checked endpoint. Back up the database (including sayin5_media_key) together with uploads; losing the key makes photos unreadable.
Deactivation preserves reviews, photos and settings and cancels SayIn5 invitation jobs. No uninstall cleanup or bulk data deletion is included.

Boundaries of this testing build

No billing, subscriptions, marketplace publishing, external review imports, social-sharing images or external email service.
The display integration uses WooCommerce’s traditional product-review tab hook. Block-only/custom product templates may need separate integration; they have not been verified. The prior standalone prototype is not embedded in this plugin.
Checkout consent supports classic and Additional Checkout Fields APIs, but production checkout compatibility has not been tested across themes or gateways. HPOS compatibility is declared using WooCommerce APIs; HPOS is not exercised in the local suite.
WordPress scheduled-task timing and mail deliverability depend on the host. A successful wp_mail call is not proof of delivery. Gmail invitation delivery was confirmed on a Windows Local test store after manually running the scheduled action. A local queued action was also processed after its scheduled time by a fresh Action Scheduler worker process. The production host’s unattended cron trigger and broad deliverability are not verified.
No paid plan or usage quotas are finalized. Image limits above are technical safeguards, not pricing limits.

Privacy

Data remains on the merchant’s WordPress site; there is no SayIn5 service connection. Invitation consent and opt-outs are stored locally. Public reviews expose nickname, content, rating if supplied, and approved photos. Private order email remains in the native review record. Existing native reviews retain their existing author names. Private review links are bearer credentials: share only with the intended purchaser; renew to invalidate an old link.
Use the store’s existing WordPress/WooCommerce data management processes. This build does not add dedicated privacy export/erasure tooling.

Support

For early testing support, email yhu9625@gmail.com. Include your WordPress, WooCommerce, PHP and SayIn5 versions and steps to reproduce. Do not send passwords, app passwords, private review links or customer records.

Beta verification

2026-10-30: 28 local HTTP checks passed, including rejection of missing nonces for admin actions. PHP and JavaScript syntax checks passed. Plugin Check 2.1.0 reported no errors; remaining warnings were reviewed in context. This does not certify compatibility with every host, theme or checkout. The current UI is English. Native browser and WordPress controls follow their own language settings.