SMART PRODUCT EMAILS
Smart Product Emails compatibility with REEID Translate
Smart Product Emails compatibility with REEID Translate is being evaluated from available plugin evidence. Adds custom, product-specific content to WooCommerce Processing emails based on what customers purchase. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Smart Product Emails.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Smart Product Emails is documented in the WooCommerce category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Smart Product Emails compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds custom, product-specific content to WooCommerce Processing emails based on what customers purchase.
- Automatically displays assigned custom messages in the customer’s Processing order email when a customer purchases a product.
- Provides a “Smart Product Emails” tab in the WooCommerce Product Data area with a “Processing” section for message assignment.
- Allows selecting a message “Content Location” within the WooCommerce email (Email Header, before/after Order Details, Order Meta, Customer Details, or Email Footer).
- Includes a built-in Error Log feature with captured PHP errors, AJAX failures, and email sending issues, with filtering/search and CSV export.
- Supports dynamic placeholders in SPE message content, including {product_name} and {order_total}.
- Includes an import wizard to migrate existing Woo Custom Emails messages and product assignments into Smart Product Emails.
CONTENT BOUNDARY
Smart Product Emails capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Smart Product Emails and REEID Translate FAQ.
What does Smart Product Emails do according to the available plugin evidence?
Smart Product Emails has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Smart Product Emails?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Smart Product Emails?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Smart Product Emails in a multilingual WordPress workflow.
REEID documents Smart Product Emails functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.