INVOICE-API.XHUB FOR WOOCOMMERCE
Invoice-api.xhub for WooCommerce compatibility with REEID Translate
Invoice-api.xhub for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Connects WooCommerce to the invoice-api.xhub.io e-invoicing service to generate compliant e-invoice files. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Invoice-api.xhub 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
Invoice-api.xhub 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 Invoice-api.xhub 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
- Connects WooCommerce to the invoice-api.xhub.io e-invoicing service to generate compliant e-invoice files.
- Generates invoices when an order reaches a configured trigger status (default: completed) or when manually triggered from the order meta box.
- Stores the generated invoice file and metadata on the WooCommerce order using custom fields prefixed with `_invoice_api_xhub_`.
- Attaches the generated invoice file to the customer-facing email automatically (configurable).
- Provides an order edit meta box to manually generate, re-generate, and download the invoice.
- Supports multiple e-invoice output formats including PDF, UBL / Peppol BIS 3.0, XRechnung, ZUGFeRD, Factur-X, and FatturaPA.
CONTENT BOUNDARY
Invoice-api.xhub 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
Invoice-api.xhub for WooCommerce and REEID Translate FAQ.
What does Invoice-api.xhub for WooCommerce do according to the available plugin evidence?
Invoice-api.xhub 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 Invoice-api.xhub 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 Invoice-api.xhub 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 Invoice-api.xhub for WooCommerce in a multilingual WordPress workflow.
REEID documents Invoice-api.xhub 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.