
TICKETDRUM
TicketDrum – Event Tickets & QR Check-in compatibility with REEID Translate
TicketDrum – Event Tickets & QR Check-in compatibility with REEID Translate is being reviewed using official plugin documentation. Sell event tickets directly on WordPress pages using a dedicated block or shortcode without requiring WooCommerce. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What TicketDrum – Event Tickets & QR Check-in does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
TicketDrum – Event Tickets & QR Check-in is documented in the Forms category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How TicketDrum – Event Tickets & QR Check-in compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Sell event tickets directly on WordPress pages using a dedicated block or shortcode without requiring WooCommerce.
- Process payments via Stripe Connect, sending funds directly to the site owner's account with an all-in transaction fee.
- Generate PDF tickets with unique QR codes attached to automatic confirmation emails sent by WordPress.
- Provide door check-in functionality allowing staff to scan QR codes or enter ticket codes using a mobile device.
- Manage promotions and availability with promo codes, usage limits, expiry dates, and automated waitlist notifications.
- Track sales performance through a dashboard featuring revenue, ticket counts, daily sales metrics, and recent orders.
- Export attendee lists and purchase data in CSV format for external reporting or management.
- Handle tax configuration including modes (none, included, added), custom labels, and default rates per ticket type.
TRANSLATION BOUNDARY
TicketDrum – Event Tickets & QR Check-in capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No specific content shown to visitors was confirmed for translation in this integration.
FREQUENTLY ASKED QUESTIONS
TicketDrum – Event Tickets & QR Check-in and REEID Translate FAQ.
What does TicketDrum – Event Tickets & QR Check-in do?
TicketDrum – Event Tickets & QR Check-in has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does TicketDrum – Event Tickets & QR Check-in have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from TicketDrum – Event Tickets & QR Check-in?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate TicketDrum – Event Tickets & QR Check-in in a multilingual WordPress workflow.
REEID documents TicketDrum – Event Tickets & QR Check-in functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.