ODEVA BOOKING
Odeva Booking compatibility with REEID Translate
Odeva Booking compatibility with REEID Translate is being evaluated from available plugin evidence. WordPress integration that embeds an Odeva reservation widget on pages via a Gutenberg block and a classic-editor shortcode. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Odeva Booking.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Odeva Booking is documented in the Other 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 Odeva Booking 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
- WordPress integration that embeds an Odeva reservation widget on pages via a Gutenberg block and a classic-editor shortcode.
- Frontend widget behavior: the visitor’s browser connects to Odeva only when the Odeva Booking block or shortcode is rendered and used.
- Backend configuration: plugin provides a Settings page where an organisation slug can be entered as global defaults, with per-block/per-shortcode overrides.
- Frontend customization options for the widget, including theme colors, border radius, and font family (configurable globally and overrideable per block/shortcode).
- Widget uses bundled JavaScript and communicates with Odeva endpoints including `https://booking.odeva.app/graphql` for accommodation/availability/pricing and reservation checkout session creation.
- Widget uses `https://booking.odeva.app/checkout` when a visitor proceeds to the hosted checkout flow, and uses image URLs returned by the Odeva API to display accommodation/unit images.
CONTENT BOUNDARY
Odeva Booking 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
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Odeva Booking and REEID Translate FAQ.
What does Odeva Booking do according to the available plugin evidence?
Odeva Booking 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 Odeva Booking?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Odeva Booking?
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 Odeva Booking in a multilingual WordPress workflow.
REEID documents Odeva Booking 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.