Scratch-to-reveal is the reveal nobody has to be taught. Drag a finger, silver comes away, something is underneath. That familiarity is the whole reason it converts: there is no instruction step between paying and playing.
Here is what a scratch card plugin is actually doing on a WooCommerce store.
It does not decide anything
Worth being clear about first, because it changes how you evaluate one. The scratch card does not determine whether somebody wins. Your giveaway plugin already did that when the order completed.
The card is a presentation layer over a result that already exists. That matters for fairness — nothing about how fast or slowly somebody scratches changes the outcome — and it matters technically, because the plugin needs a giveaway engine underneath it to have anything to show.
Two play modes
The same module runs two quite different games, and the choice is a real one.
Classic is a grid of panels you scratch off to reveal a straight win or no-win. Fast, obvious, and the right pick when people are buying twenty tickets and want to get through them.
Sums and Symbols is a match game. Either match two symbols, or find numbers adding to a target. It takes a few seconds longer per card and it feels more like a game and less like a lookup.
Rule of thumb: high ticket volume favours Classic, high ticket value favours Sums and Symbols. A £2 draw where people buy fifty is not the place for a puzzle.
Multi-ticket orders are the real test
Anyone can make one scratch card feel good. Thirty is the design problem.
Look for multi-card support that gives you a card-to-card flow rather than making people reload, and some form of reveal-all for people who have decided they are done scratching. Fifty cards at four seconds each is more than three minutes of dragging, and somewhere around card twelve the charm has worn off.
Respecting that is not a compromise. It is the difference between a mechanic people enjoy and one they endure.
What to check before you commit
- Does it work with your giveaway plugin? Not "with WooCommerce" — with the specific plugin issuing your tickets. This is where most disappointment starts.
- Is it touch-native? Scratching is a touch gesture. If it was built mouse-first and patched for touch, you will feel it.
- How much is actually configurable? Plenty of plugins let you change three colours and call it customisable. Ask whether you can change the artwork, the copy on the buttons, the card layout and the win and lose cards.
- Does it handle the confirmation email? If the result is in the inbox before the card is scratched, none of the rest matters.
The bit that gets overlooked
The win and lose cards. Everyone spends their time on the scratch surface and treats the result card as an afterthought, when the result card is the thing people screenshot and send to their group chat.
Make it show the actual prize — its artwork, its name, its value — rather than a generic panel with text. It is a five-minute change and it is the most-shared frame in the whole sequence.
