ITNET AI · Case study · Prebooking Management System

1,000 launch prebookings across 145 dealers. In two hours. Built in 24.

When an Apple Authorised Distributor for Kerala and Tamil Nadu needed to take iPhone launch prebookings through its dealer network — without ever holding the dealers' customer data — we built the Prebooking Management System and had it live before the launch window opened.

145dealers onboarded across two states
~1,000bookings in the first two hours
112part numbers from the Apple price list
24 hrsfrom first conversation to live

The problem

A launch prebooking used to mean WhatsApp messages, Excel sheets and phone calls: dealers collecting names on paper, the distributor guessing demand, and stock allocated by argument. Three things had to be true at once: dealers keep their own customers, the distributor sees demand by exact part number, and the whole thing is live on a phone with no app to install.

What we built

  • A branded booking page per dealer — logo, contact, WhatsApp; model, storage and colour in three taps; MRP and launch offers shown; a booking reference the customer can WhatsApp to the store.
  • A privacy wall, in the database — customer names and numbers are readable only with the dealer's private link. The distributor's admin has no function that returns them.
  • Distributor admin — dealer onboarding with one-time setup links, live demand matrix by part number and dealer, catalogue control, and a booking window that unlocks models on the second.
  • BDM tracker — who has sent links, who is live, who is driving bookings, split by state and zone.
  • Allocation planner — enter units available, auto-split by demand with largest-remainder rounding, override any cell, publish to dealers.
  • Bulk upload — paste the Apple dealer sheet, duplicates skipped by Apple ID.
Customer booking page on a phone
Booking confirmation with reference
Dealer dashboard with bookings
Customer page · confirmation · dealer dashboard (sample data)
Distributor admin overview
Distributor overview — demand by model, top dealers, latest bookings. No customer names anywhere.
BDM onboarding progress
BDM progress — live, awaiting setup, not sent, with a Kerala / Tamil Nadu split
Allocation planner
Allocation — available units split by demand, published to dealers when ready

How the launch went

  • Day 0, morningRequirements on WhatsApp. Database, admin, dealer and customer pages built; price list and 84 dealers loaded by afternoon.
  • Day 0, eveningIllustrated guides for admin, dealers and customers. Custom subdomain requested from the client's IT.
  • Day 1, morningDealer list grown to 145 with the bulk uploader. BDMs sending setup links; 100+ dealer pages live by lunch. Apple Watch and AirPods opened early; iPhone locked to 5:30 PM.
  • Day 1, 5:30 PMiPhone unlocked on the server at the second. 452 bookings in the first 30 minutes, ~1,000 units by 7:15 PM, zero duplicate customers across dealers, no downtime.

"The distributor sees exactly what it needs — demand by part number and dealer — and nothing it shouldn't. That line is enforced in the database, not in a promise."

ITNET AI, on the privacy design

Get one for your dealer network

Any brand, any product with a part number. Built multi-tenant, so a second distributor is configuration, not a rebuild. Hosted and supported by us; your own subdomain takes one DNS record.

From ₹25,000 + GST per launch seasonIncludes hosting and support through the launch. Dealer notifications, custom domain and further seasons quoted separately.
Talk to us on WhatsApp

Common questions

Can this work for brands other than Apple?

Yes. The catalogue is loaded from your price list — any product with a part number works. Attributes like storage, colour, size or band are read from the description and drive the customer's tap-through.

Does the distributor see customer names and numbers?

No. Customer details are stored against the dealer who took the booking and are retrievable only with that dealer's private link. The distributor sees model demand by dealer. This is enforced in the database, not hidden in the screen.

How fast can it be live?

This one went from first conversation to live in about 24 hours with the dealer list, price list and offers loaded. Most of the time after that is your dealers doing a two-minute setup each.

What about payments?

By design this takes no payment — it registers interest and place in the queue, and the dealer settles price and payment at the store. Token-amount collection can be added if your programme needs it.

A launch is a bad day to discover your booking sheet doesn't scale.

Send us one line about your dealer network and the launch date. We'll show you a working page before you pay a rupee.

WhatsApp +91 99958 00818