Pilot results and case studies
We are running our first store pilots now. We will only publish results that are real and measured, with the retailer’s permission, on this page. Until then, here is exactly what a pilot measures, so you know what you will get from yours.
How a pilot runs
| When | What happens |
|---|---|
| Week 1 | Setup: catalogue sync, QR standees, Razorpay live, staff training |
| Weeks 2 and 3 | Live express lane: shoppers scan and pay, guards verify, we tune it daily |
| Week 4 | Your numbers, measured against a similar store as the control |
What we measure
- Time to exit for app shoppers compared with the billing queue.
- Walkouts, the shoppers who see the queue and leave, before and during the pilot.
- Share of checkouts that moved to the app.
- Shrinkage from stock audits, compared with the control store.
- Exit checks: how many passes were flagged and what a full check found.
Working out your own loss today
You can estimate what the queue costs you before a pilot. A simple way: daily footfall, times the share of shoppers who reach the counter, times the share who walk out because of the queue, times your average bill, times 30 days. For example, a store where 60 shoppers a day walk out with an average bill of ₹450 loses about ₹8 lakh of sales a month. These are example figures. Your own numbers come from the pilot.
Try it in one of your stores. Be one of the first stores with published results. Pilots start with one store and a 30 day plan.
See how the pilot works or write to hello@qwikexit.com.
Common questions
Does QwikExit have case studies?
Pilots are running now. Results will be published only when they are measured, and only with the retailer’s permission.
What does a QwikExit pilot measure?
Time to exit, walkouts, the share of checkouts done in the app, shrinkage against a control store and the results of exit checks.