Meena's First Week Running Her Shop From a Phone

Getting started with Mapis is not a weekend of data entry. Here is what the first seven days actually look like in a working kirana shop, and where people go wrong.

Meena runs a kirana store in a residential lane in Coimbatore. Her shop carries around 600 products, she serves roughly 180 customers a day, and until this year she ran all of it from a red register and a very good memory.

She had tried to move to an app twice before and stopped both times within a week. What follows is what the third attempt looked like, because the third one worked — and the only real difference was the plan.

Day One: Fifty Products, Not Six Hundred

The instinct is to enter everything before you begin. That is roughly ten hours of unrewarded work for a 600-product shop, and it is where both of Meena's earlier attempts died.

Instead she created her shop profile and added only the fifty products she sells most. Barcode scanning filled in names and details, so she typed prices and current quantities and nothing else. It took her fifty-five minutes, spread across the quiet parts of the morning.

Name, selling price and current quantity are enough for a product to be useful. Cost price, HSN code, category and reorder point can all be added later, when the item is in front of you at a delivery. Perfectionism at setup is the single most common reason a catalogue never gets finished.

Days Two to Four: Bill on the App, Keep the Register Open

This is the step people skip, and skipping it is why one bad afternoon ends the whole attempt.

Meena billed every sale involving her fifty products on the phone. She also kept writing in the register, exactly as before. Yes, that is the same work twice — for three days, and it means that when something confusing happens during a rush, with four people waiting, there is a fallback that does not involve apologising to a queue.

It was slower. She had expected that, which is the reason she got through it. For about the first three days the app is genuinely slower than a method you have used for eleven years, because you are learning it.

The first two times I quit, I thought the app was the problem. It was not. I had just expected day three to feel like day thirty.

Day Five: The First Thing She Did Not Know

On Friday evening she looked at the day's sales by item rather than as a total, and found that a brand of detergent she considered a strong seller had moved four units in five days. A cheaper brand she barely thought about had moved thirty-one.

She had been giving the better shelf position to the wrong one for about two years. This is the point at which the app stops being an obligation and starts being useful, and for most shopkeepers it arrives in the first week.

Days Six and Seven: Let the Catalogue Build Itself

Two suppliers delivered over the weekend. Every delivery arrives with product details already in front of you — the box, the invoice, the price — so Meena entered those items as she unpacked them.

This is the whole trick to a large catalogue. It builds out of work you were already doing, in ten-minute pieces, instead of out of a weekend you have to find.

Week Two: Closing the Register

By the second week the fifty products that make up most of Meena's daily sales were faster on the phone than in the book, and she had spent a fortnight checking the app's numbers against her own handwriting. Trust had been earned rather than assumed.

She stopped writing in the register on a Tuesday. It was not a decision so much as a thing she noticed she had already done.

The Five Minutes That Matter Most

The habit that separates shopkeepers who benefit from those who merely have an app installed is a daily glance at closing. Not a report — a glance.

Five minutes a day does more for decision-making than any monthly report, because a stockout found tonight costs one day and a stockout found on Saturday costs six.

The Three Mistakes to Avoid

All three are habits rather than software problems, and all three are far easier to avoid in week one than to correct in month six.

Mapis is built for exactly this pace: scan to add a product, a few taps to record a sale, and alerts that arrive without being configured. If you have tried before and stopped in the first week, starting with fifty products instead of six hundred is usually the only change required.

Frequently asked questions

How do I start using Mapis in my shop?

Create your shop profile, add your products with prices, then record sales as they happen. Stock updates itself from those sales, and the dashboard summarises the day. Start with your fastest-moving products rather than your whole catalogue — entering everything before you begin is the most common reason shopkeepers stall in the first week.

How long does it take to set up a shop on Mapis?

Around 30-45 minutes if you begin with your 50 fastest-moving products. Barcode scanning fills in most product details automatically, and the rest of the catalogue can be added gradually as supplier deliveries arrive, so it never becomes a weekend-long data entry job.

What should I check on the dashboard every day?

Five minutes at closing is enough: what sold, what ran out, what is close to running out, and what was lost to damage or expiry. That single daily habit does more for decision-making than any monthly report, because a stockout found today costs one day rather than a week.

What mistakes should I avoid when starting out?

Three: not updating stock regularly, so the numbers stop being trustworthy; ignoring the reports you are generating; and mixing personal and shop expenses, which makes real profit impossible to see. All three are habits rather than software problems, and all three are easier to avoid from day one than to correct later.