JSM SHOW ORDER METADATA FOR WOOCOMMERCE HPOS
JSM Show Order Metadata for WooCommerce HPOS compatibility with REEID Translate
JSM Show Order Metadata for WooCommerce HPOS compatibility with REEID Translate is being evaluated from available plugin evidence. Displays WooCommerce order metadata keys and unserialized values in a metabox on HPOS order editing pages. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for JSM Show Order Metadata for WooCommerce HPOS.
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
JSM Show Order Metadata for WooCommerce HPOS 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 JSM Show Order Metadata for WooCommerce HPOS 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
- Displays WooCommerce order metadata keys and unserialized values in a metabox on HPOS order editing pages.
- Shows the order metadata metabox at the bottom of the WooCommerce HPOS order editing page.
- Shows the order metadata metabox on WooCommerce Subscriptions editing pages.
- Provides developer filters to control which order meta is shown in the metabox (including excluding meta keys via regular expressions).
- Provides developer filters to control required capabilities for showing and deleting order meta in the metabox.
- Provides a developer filter for the delete order meta button icon class.
CONTENT BOUNDARY
JSM Show Order Metadata for WooCommerce HPOS 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
JSM Show Order Metadata for WooCommerce HPOS and REEID Translate FAQ.
What does JSM Show Order Metadata for WooCommerce HPOS do according to the available plugin evidence?
JSM Show Order Metadata for WooCommerce HPOS 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 JSM Show Order Metadata for WooCommerce HPOS?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for JSM Show Order Metadata for WooCommerce HPOS?
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 JSM Show Order Metadata for WooCommerce HPOS in a multilingual WordPress workflow.
REEID documents JSM Show Order Metadata for WooCommerce HPOS 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.