Multi-accounting and raffle stuffing in Retail & e-commerce
Repeated entries distort allocation per customer and increase manual entry-review workload.
Try freeHow the attack works
- The reseller creates or prepares multiple accounts for a product raffle, using separate contact details for each entry. The objective is to increase their share of the draw before stock is allocated, rather than simply complete checkout faster at release.
- The operator varies delivery details, including small changes to the same underlying address, and distributes entries across proxies. These variations make the accounts appear separate to checks that compare only exact email, address or network values.
- Each identity submits an entry and keeps the necessary account access available for the result. Related devices, payment arrangements or address patterns can remain across the entries even though the visible account details differ.
- Winning entries proceed to purchase and are consolidated for resale. The operator can repeat the account preparation for the next raffle, while the brand's records show multiple entrants rather than the concentration of participation behind them.
Why it gets through
A raffle gives each eligible entry a chance, so the entry boundary is commercially important. If eligibility is reduced to a unique email address, the operator can buy more chances by registering again. A successful email check confirms contactability, not independent participation.
Exact-match checks miss variations in account and delivery fields. Broader matching can create another problem: households and shared delivery locations can be legitimate. Your team needs relationships and context rather than an automatic assumption that every similar address belongs to an abusive entrant.
A network limit sees where an entry came from, not the whole preparation behind it. Proxy changes can spread entries across addresses, while separate account records hide reuse elsewhere in the journey. Looking at each application alone leaves the operator's combined participation difficult to assess.
What it costs
Allocation per customer is the core measure. A one-entry or one-purchase rule has little commercial meaning if repeated identities receive independent treatment. A raffle can follow its draw procedure correctly while the underlying pool gives one operator more opportunities than intended.
Manual entry-review workload rises when the team tries to reconstruct relationships after registration closes. Comparing account, address and payment records across systems takes time, particularly when the release schedule leaves a short interval between the entry deadline and purchase invitations.
Fan participation and support contacts reveal the longer effect. Genuine entrants need confidence in the allocation process, while legitimate households should not be rejected simply because they share a device or address. The business needs evidence that supports a defensible review of those different situations.
How Kairal stops it
Kairal connects raffle registration and entry activity through session linking. Device and network context becomes part of the history around an entry, allowing the team to examine relationships between accounts instead of relying only on the fields supplied on the application form.
Where your integration supplies account, payment and address context, those references can be assessed alongside the session. Repeated participation may therefore remain visible when an email changes or a proxy supplies a new IP address. The connection is a reason to review the entries together, not definitive proof that they belong to one individual.
Kairal adds context to your existing raffle process. Your business continues to define eligibility, draw winners and decide how household participation is handled. Kairal does not replace those rules or guarantee that allocation will reach a particular kind of buyer.
Events and Sessions give the operations team request and session context for its investigation. Reviewing the entry endpoint alongside later account activity helps separate isolated submissions from repeated participation through linked identities. That gives the team a more coherent basis for applying its existing limits, while keeping your existing eligibility checks and legitimate household participation in view.
Deployment
Plan integration in days rather than months, connecting the raffle registration and entry paths with the account context your eligibility process uses. Session assessment runs in the background to preserve a frictionless entry journey for genuine fans while your team reviews connected participation.
Make your business a harder target.
Try Kairal Bot Protection free for three months to gain visibility into the threats facing your business.
Our team will prepare your account and contact you with the next steps.