Features
Competition ticket management for WordPress
raffleWP connects competition ticket numbers to WooCommerce orders. Let customers choose numbers or use Lucky Dip, reserve availability during checkout, and keep confirmed paid and postal entries in the same competition record.
What you can do
Number selection and Lucky Dip
Offer customer-selected numbers or automatic allocation. Configure the competition’s number range and entry options, then show customers the numbers attached to their order.
Bundles and entry limits
Set minimum and maximum quantities and quantity-based bundles. Give customers a clear purchase choice while accounting for the limits configured for your competition.
Paid and postal entries
Take payment through your WooCommerce checkout and process valid postal requests in admin. Keep the entry source visible without treating postal tickets as paid sales.
How a ticket moves from checkout to confirmation
- Create the competition product with its prize, ticket range, price, entry limits, opening time and entry closing time. Add any bundle offers before testing checkout.
- A customer chooses available numbers or Lucky Dip. A temporary reservation protects availability while the order is being placed; a reservation alone is not a confirmed entry.
- Successful payment handling confirms the order’s tickets. raffleWP responds to WooCommerce payment completion and processing/completed order states, so test the payment methods your store actually uses.
- Confirmed numbers appear with the order and in customer ticket records. Review entries in admin and preserve an export when preparing the main draw.
For example, a customer may select three available numbers while another chooses a five-entry bundle using Lucky Dip. Both orders join the same competition record after confirmation. The bundle changes the purchase price; it does not create a separate winner pool.
Keep closing dates and postal records clear
You can stop entries before the advertised main draw by setting a separate closing date. The competition countdown follows the entry deadline. Future-start competitions can remain visible as “Coming soon” while purchasing and ticket allocation stay closed.
Record eligible postal requests with their receipt details. Timely postal entries can be entered after closing and before a winner is drawn; requests received at or after the deadline are rejected. Existing timely reservations continue through the normal payment-confirmation workflow.
Closing entries does not automatically select the main winner. Leave time to reconcile orders, refunds and valid postal entries before reviewing the final pool. Failed, cancelled and fully refunded order states require the corresponding ticket handling; a partial refund needs a separate eligibility review.
The educational guide to WooCommerce entries and tickets explains the wider lifecycle and the checks to run before launch.
Common questions
Can customers choose their own ticket numbers?
Yes. raffleWP supports customer-selected numbers and Lucky Dip. Choose the entry options appropriate to the competition and test the experience on mobile as well as desktop.
Does every number in a basket count as an entry?
No. A temporary reservation protects availability during checkout. Confirmed entry status follows the order and payment workflow; an abandoned basket is not proof of eligibility.
Can I guarantee one entry limit per household?
Set the supported customer and purchase limits, then check the identifiers and guest-checkout behaviour against your terms. A software quantity limit is not independent household or identity verification.
Build the rest of your workflow
Connect confirmed tickets to instant wins, prepare winner records and fulfilment, or model the effect of bundles and postal capacity.
This feature is included with every current raffleWP licence. WordPress and WooCommerce are required. Optional addons are separate plugin downloads included with your licence.
Product information reviewed on 8 September 2026 against raffleWP 1.4.2 and the relevant addon documentation. Published by raffleWP.