CUSTOMS
Customs – EU Import Duty for WooCommerce compatibility with REEID Translate
Customs – EU Import Duty for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Adds an EU import duty estimate as a dedicated fee line at WooCommerce cart and checkout. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Customs – EU Import Duty 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
Customs – EU Import Duty 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 Customs – EU Import Duty 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 import duty estimate as a dedicated fee line at WooCommerce cart and checkout.
- Calculates the duty estimate based on the number of distinct tariff lines in the cart multiplied by a configurable per-line amount.
- Counts tariff lines from a per-product tariff code, falling back to the product category, then the product.
- Shows the duty line via the native WooCommerce fees API and supports both classic checkout and the Cart and Checkout Blocks (HPOS compatible).
- Provides configurable settings including per-line amount, threshold, store origin country, EUR conversion rate, fee label, and whether the fee is taxable.
- Adds taxes on top by showing the duty as its own line in addition to VAT.
CONTENT BOUNDARY
Customs – EU Import Duty 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
Customs – EU Import Duty for WooCommerce and REEID Translate FAQ.
What does Customs – EU Import Duty for WooCommerce do according to the available plugin evidence?
Customs – EU Import Duty 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 Customs – EU Import Duty 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 Customs – EU Import Duty 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 Customs – EU Import Duty for WooCommerce in a multilingual WordPress workflow.
REEID documents Customs – EU Import Duty 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.