FLEXA WISHLIST FOR WOOCOMMERCE
Flexa Wishlist for WooCommerce compatibility with REEID Translate
Flexa Wishlist for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a WooCommerce wishlist UX with one-tap save on product cards and product pages. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Flexa Wishlist for WooCommerce.
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
Flexa Wishlist for WooCommerce is documented in the WooCommerce category with 6 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 Flexa Wishlist for WooCommerce 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
- Provides a WooCommerce wishlist UX with one-tap save on product cards and product pages.
- Supports guest wishlists that persist without an account and merge into the account on login.
- Creates and renders a dedicated wishlist page via the shortcode `[flexa_wishlist]` (also available as a Gutenberg block and Elementor widget).
- Adds wishlist controls including a save button shortcode `[flexa_wishlist_button product_id="123"]` and a live saved-items counter shortcode `[flexa_wishlist_counter]` (also available as blocks and Elementor widgets).
- Allows adding wishlisted items to the cart from the wishlist, including an “Add all to cart” action and skip reasons for out-of-stock or variable products.
- Includes sharing for wishlists using a native share sheet on mobile and copy-link + channels on desktop.
CONTENT BOUNDARY
Flexa Wishlist for WooCommerce 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
Flexa Wishlist for WooCommerce and REEID Translate FAQ.
What does Flexa Wishlist for WooCommerce do according to the available plugin evidence?
Flexa Wishlist for WooCommerce has 6 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 Flexa Wishlist for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Flexa Wishlist for WooCommerce?
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 Flexa Wishlist for WooCommerce in a multilingual WordPress workflow.
REEID documents Flexa Wishlist for WooCommerce 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.