WT CATALOG
WT Catalog compatibility with REEID Translate
WT Catalog compatibility with REEID Translate is being evaluated from available plugin evidence. dynamically fetches wine and beer product data, images, and specifications from the WT Catalog API without storing a local copy of the assortment No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WT Catalog.
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
WT Catalog is documented in the Other category with 7 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 WT Catalog 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
- dynamically fetches wine and beer product data, images, and specifications from the WT Catalog API without storing a local copy of the assortment
- provides separate page templates for wine and beer listings with interactive JavaScript filters for country, color, bottle size, and producer that update result counts in real-time
- generates individual product pages displaying producer names, regions, ratings, badges, tasting notes, food pairings, and drink-specific technical specifications
- integrates with Yoast SEO or Rank Math to supply meta tags, Open Graph data, canonical URLs, and XML sitemap entries for catalog products
- allows administrators to restrict displayed inventory based on purchase history windows (last 3, 6, or 12 months) or show all available products
- offers a blocklist feature to hide specific base numbers from listings, product pages, and sitemaps across all vintages
- displays no pricing information as WT prices are customer-specific and excluded from the public-facing catalog display
CONTENT BOUNDARY
WT Catalog 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
WT Catalog and REEID Translate FAQ.
What does WT Catalog do according to the available plugin evidence?
WT Catalog has 7 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 WT Catalog?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WT Catalog?
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 WT Catalog in a multilingual WordPress workflow.
REEID documents WT Catalog 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.