Storefront & checkout
Make entering the competition the easy part.
The customer experience should be clear. See the prize. Understand the odds. Choose the entries. Complete the required checks. Pay. Get the receipt.
Beaver keeps the storefront simple while the platform manages the operational state underneath it.
The customer journey
Six steps. No surprises.
See the prize
Prize detail, photography and competition information.
Understand the odds
Published odds on the competition page.
Choose the entries
Preset ticket bundles.
Complete the checks
Skill question validated on the server, where used.
Pay
Inside the spending controls.
Get the receipt
VAT itemised.
The storefront
Show the customer what is real.
-
Competition grid
Show what is live.
Live
The competition grid lists active competitions using the operator's branding. Draft competitions stay out of the public experience until they are ready.
If it is not live, the customer does not need to see it.
-
Competition page
Give the prize enough room to sell itself.
Live
Prize detail, photography, ticket selection, sales progress, published odds, competition information and a percentage sold indicator.
The countdown control and an absolute tickets remaining display are not currently wired, so we do not present them as live.
-
Ticket bundles
Make common choices easy.
Live
Preset bundles such as 1, 5, 10, 25 or 50 entries give clear purchasing choices without an unnecessarily complicated selector.
Lucky dip and manual number picking are not current live storefront behaviours.
-
Reservation
Hold the inventory while the customer checks out.
Live
Selected tickets are reserved for a fixed period. If payment is not completed, they return to the available pool automatically.
Reserved is not sold. Beaver knows the difference.
Skill questions
Validate before payment.
Where the operator uses a skill question, Beaver can serve and validate the answer on the server before payment. The question is not trusted to client side browser logic.
Software enforcement does not determine whether a question meets the legal test for a genuine prize competition. That is a separate question, and an important one.
The browser does not mark its own homework.
Free entry routes
Free entries belong in the same competition.
Live The storefront supports postal and online free entry routes, with accepted entries allocated into the same competition pool as paid entries.
Different route in. Same pool at the end.
- Eligible entry pool
- Draw
-
Published odds
Live
Tell the customer the chance they are buying. Published odds form part of the competition page and the draw record.
Transparency starts before the draw.
-
Receipts
Live
Send a proper record of the purchase. VAT itemised receipts treat prices as VAT inclusive, with the tax component shown rather than added unexpectedly at the end.
-
SEO foundations
Live
Sitemaps, robots handling and canonical behaviour, with draft competitions kept out of both the sitemap and public indexing.
Structured data exists as a switch in the registry but is not wired, so we do not sell it.
Payment status
What works today.
Payments are where claims get expensive, so here is exactly where they stand.
| Capability | Status | What that means |
|---|---|---|
| Complete sandbox payment journey | Live | Works end to end through Beaver. |
| Cashflows integration | Built | Built against the published reference. |
| Stripe adapter | Built | Exists in the product. |
| Production card processing | Not available | Real merchant validation has not happened yet. |
| Apple Pay and Google Pay | Roadmap | Specced, not implemented. |
| Saved cards | Roadmap | Specced, not implemented. |
| Guest checkout | Roadmap | The current journey is account based. |
Live proven on the deployed platform. Built in the product with passing tests, not yet proven with live customers. Roadmap planned, not a working feature.
Checkout architecture is built. Production proof still has to earn the claim.
Customer experience
Keep the front end simple. Let Beaver handle the state underneath it.
