RIGHT OF WITHDRAWAL FLOW FOR SHOP
Right of Withdrawal flow for shop compatibility with REEID Translate
Right of Withdrawal flow for shop compatibility with REEID Translate is being evaluated from available plugin evidence. Adds a customer "Withdraw from order" action that opens a withdrawal modal to select items, enter an IBAN, and choose a withdrawal reason. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Right of Withdrawal flow for shop.
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
Right of Withdrawal flow for shop 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 Right of Withdrawal flow for shop 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 a customer "Withdraw from order" action that opens a withdrawal modal to select items, enter an IBAN, and choose a withdrawal reason.
- Supports full or partial withdrawals by letting customers select specific items and quantities.
- Tracks withdrawal requests and refund status, including an admin metabox with status updates.
- Provides a "Withdrawal" column and "All withdrawal states" filter in **WooCommerce → Orders** to view pending and processed requests.
- Includes a guest checkout withdrawal form via the `[rowfs_withdrawal_form]` shortcode and a signed withdrawal link sent to the billing email.
- Processes refunds using IBAN details and can optionally create a WooCommerce refund record automatically.
CONTENT BOUNDARY
Right of Withdrawal flow for shop 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
Right of Withdrawal flow for shop and REEID Translate FAQ.
What does Right of Withdrawal flow for shop do according to the available plugin evidence?
Right of Withdrawal flow for shop 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 Right of Withdrawal flow for shop?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Right of Withdrawal flow for shop?
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 Right of Withdrawal flow for shop in a multilingual WordPress workflow.
REEID documents Right of Withdrawal flow for shop 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.