EU PARCEL TARIFF FOR WOOCOMMERCE
EU Parcel Tariff for WooCommerce compatibility with REEID Translate
EU Parcel Tariff for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Adds an “EU Product Type” taxonomy where each term maps to a TARIC/HS subheading. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for EU Parcel Tariff 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
EU Parcel Tariff 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 EU Parcel Tariff 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
- Adds an “EU Product Type” taxonomy where each term maps to a TARIC/HS subheading.
- Lets merchants assign a default EU product type per product category, with a per-product override and a per-product country of origin.
- At checkout, counts distinct (classification, origin) tuples in the cart and adds an N × 3 € fee when legal conditions are met.
- Charges a flat 3 € customs duty per type of goods for eligible low-value consignments shipped from outside the EU customs territory (including Ceuta and Melilla exclusions and Canary Islands inclusion as described).
- Provides developer filters: `eupt_duty_amount`, `eupt_is_applicable`, `eupt_goods_types_count`, `eupt_fee_args`.
- Adds the duty estimate as a fee at checkout for DDP-style checkouts, and does not handle customs declaration or payment to authorities.
CONTENT BOUNDARY
EU Parcel Tariff 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
EU Parcel Tariff for WooCommerce and REEID Translate FAQ.
What does EU Parcel Tariff for WooCommerce do according to the available plugin evidence?
EU Parcel Tariff 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 EU Parcel Tariff 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 EU Parcel Tariff 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 EU Parcel Tariff for WooCommerce in a multilingual WordPress workflow.
REEID documents EU Parcel Tariff 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.