WOOCOMMERCE LEGACY REST API
WooCommerce Legacy REST API translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WooCommerce Legacy REST API does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Restores the removed WooCommerce Legacy REST API in WooCommerce 9.0 and later.
- Keeps existing user keys working with the Legacy REST API.
- Leaves WooCommerce 8.9 and earlier unchanged by detecting the built-in Legacy REST API and not initializing itself.
- Is not compatible with High-Performance Order Storage.
- Provides the same endpoints and behavior as the Legacy REST API in WooCommerce 8.9 and earlier.
Distinctive features
Restores access to the WooCommerce Legacy REST API after it was removed from WooCommerce core. Preserves existing user keys and matches the legacy endpoints and behavior available in WooCommerce 8.9 and earlier.
Dynamic content
The supplied evidence does not establish broader dynamic content behavior beyond restoring the Legacy REST API endpoints and behavior.
SEO and metadata
The supplied evidence does not establish SEO or metadata-specific behavior.
URLs and navigation
The plugin exposes the WooCommerce Legacy REST API endpoints; no broader URL or navigation behavior is established in the supplied evidence.
Forms and commerce
The supplied evidence does not establish forms behavior. It is tied to WooCommerce REST API access and is not compatible with High-Performance Order Storage.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WooCommerce Legacy REST API does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- Not compatible with High-Performance Order Storage. It is intended for WooCommerce 9.0 and later, while WooCommerce 8.9 and earlier already include the Legacy REST API and are left unchanged.
COMMON QUESTIONS
WooCommerce Legacy REST API and REEID Translate FAQ.
Does the current evidence establish translation scope for WooCommerce Legacy REST API?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.