EU WITHDRAWAL COMPLIANCE
EU Withdrawal Compliance compatibility with REEID Translate
EU Withdrawal Compliance compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a two-step public withdrawal request flow with a dedicated confirmation step before the request is registered. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for EU Withdrawal Compliance.
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
EU Withdrawal Compliance is documented in the Forms 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 EU Withdrawal Compliance 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 two-step public withdrawal request flow with a dedicated confirmation step before the request is registered.
- Generates and displays an Annex I.B model withdrawal form as a collapsible block with a printable view.
- Implements WooCommerce checkout consents for Article 16(m) digital content and Article 14(4)(a) services started within the 14-day window.
- Stores withdrawal requests as a private custom post type (`ayudawp_withdrawal`) and supports a request status lifecycle with admin tooling including CSV export.
- Issues a SHA-256 receipt hash as durable-medium proof and includes it in the acknowledgement/receipt handling described in the documentation.
- Supports multilingual stores via WPML and Polylang, including language-following links and translatable customer-facing texts via bundled configuration.
CONTENT BOUNDARY
EU Withdrawal Compliance 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
EU Withdrawal Compliance and REEID Translate FAQ.
What does EU Withdrawal Compliance do according to the available plugin evidence?
EU Withdrawal Compliance 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 EU Withdrawal Compliance?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for EU Withdrawal Compliance?
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 EU Withdrawal Compliance in a multilingual WordPress workflow.
REEID documents EU Withdrawal Compliance 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.