Online kuji · Quote prep
Building an online kuji site: 5 things to decide before getting a quote
Even among ‘kuji sites,’ development scope varies with how you sell and how prizes are delivered. Before counting screens, decide how a single order flows from payment to draw to shipping—that makes quotes much easier to compare.
KUJI BUILDER · Last reviewed
1. Start with the rules for a single kuji board
Selling through a finite set of tickets requires a different inventory design than drawing at set odds each time. For example, for an 80-ticket board with 2 Prize A tickets, the spec should first state whether all tiers add up to 80 and whether the buyer of the last ticket receives the Last One prize. Decide the prize lineup and purchasable quantities at the same time.
- Prize names, images, and quantities per tier, plus total tickets
- Pick-your-number, random, or pack format—whichever you need
- Price per draw, quantity per purchase, and purchase limits
- Last One conditions and handling for paused or sold-out boards
2. Design for failed payments and duplicate requests
Opening a payment screen doesn't mean you're ready to sell. Even if a customer closes the window after approval or the same request repeats, the order and draw must be processed only once. Payment methods are finalized based on PG review and contracts, and test mode and live payments are tested separately.
- Who holds the PG contract and which payment methods you need
- Inventory holds during pending payment and when they expire
- Order recovery after approvals, cancellations, and timeouts
- How to reconcile payment amounts, order totals, and settlements
3. Decide on storage, shipping, and pickup after a win
Order screens and day-to-day operations differ depending on whether each draw ships right away or winnings are kept in the customer's prize storage for combined shipping. If you also offer store pickup, you need to decide on pickup code expiry, proxy pickup, and preventing reuse of codes already redeemed.
- Shipping fees, combined shipping rules, and storage period
- Address change cutoff, tracking number entry, and damage or misdelivery claims
- Store pickup location, hours, and verification steps
- Cancellation and return rules both before and after the draw
4. Separate what operators can do and see
Product listing, shipping, and settlement staff each need different permissions. Also decide whether prize quantities or prices can be changed during a sale, and whether to log who changed what and when. For public win history, agree on a scope that doesn't unnecessarily expose information that identifies customers.
- Permissions to list products and boards, schedule sales, and stop sales
- Separate permissions for order lookup, shipping, and refund approval
- Logs of draws, inventory changes, and admin actions
- Access to personal information, retention periods, and deletion procedures
5. Compare build costs and operating costs separately
A quote should list included features, external integrations, acceptance criteria, number of revisions, and deliverables. Check server, domain, PG, identity verification, and notification costs separately from build costs. The registrations, filings, product rights, and policies that apply to your sales structure should be confirmed by the operator with the relevant authorities and professionals, then reflected in the launch scope.
- Must-have features vs. features to add later
- Build costs vs. monthly fixed costs vs. per-transaction or per-message costs
- Who owns the domain, source code, cloud, and PG accounts
- Warranty period, rates for additional development, and data handover method