The Business That Lives Between Two Software Categories

You have three production units and nineteen outlets.

You roast coffee. You bake pastries. You press spices. You make furniture. You process something. You produce it yourself, and you sell it through outlets you own.

Each production unit has software. Or a spreadsheet. Or a memory.

Each outlet runs on a POS system. Petpooja. RestroWorks. Toast. Something.

You can see what sold at outlet 14 today. You can track billing at outlet 7. You can pull a report from outlet 3’s revenue.

But the moment you ask a question that spans production and outlets, you’re lost.

“Which batch of roasted coffee went to which outlet?”

You don’t know. Someone in the roastery knows. Maybe. Or they write it down in a notebook.

“How much raw material did we buy last month? How much finished product did we make? How much is left in inventory?”

Spreadsheet. WhatsApp. Memory.

“Why does outlet 14 have 50 kg of coffee that hasn’t sold in two weeks while outlet 5 ran out yesterday?”

You have to ask the outlet managers. They don’t know. The batch details are somewhere in the production unit’s records.

“A customer complained about the quality of a product they bought at outlet 7 on the 12th. Which batch was it? What raw material went into it? Who processed it?”

Nobody can tell you. Not because they’re incompetent. Because the thread connecting raw material to batch to outlet to customer doesn’t exist anywhere in your system.

This is the gap.

And it’s invisible.

Thanks for reading! Subscribe for free to receive new posts and support my work.

The Coffee Bean Moves

Here’s what happens when you roast coffee.

Raw material arrives. Supplier delivers 100 kg of Ethiopian beans. Someone weighs it. Someone records it. Somewhere.

It sits in the raw materials warehouse.

Then, one day, the roaster decides: today we roast the Ethiopian batch. He pulls 50 kg from warehouse. He roasts it. Two hours later, it’s done. He cools it. He packs it into 1 kg bags. He labels each bag with a date.

Now there are 50 bags of roasted Ethiopian coffee. Fifty 1 kg units.

These bags need to be tracked as a batch. Which raw batch did they come from? When were they roasted? What’s the expiry? Which outlet should get them?

But most operators don’t have a system for this. So what happens?

The bags sit in the production warehouse. A manager writes in a notebook: “50 bags of Ethiopian, roasted 15th July.” That’s the documentation.

Then, at some point, someone decides: outlet 7 needs coffee. They load 10 bags into a vehicle. They drive them to outlet 7. They hand them to the outlet manager.

The outlet manager stocks them on the shelf. At some point, a customer buys a bag. The POS rings it up.

But now there’s a problem:

The finished good (1 kg bag of roasted Ethiopian) exists in three systems simultaneously:

• The production unit’s notebook (which batch, when roasted, where is it)

• The outlet’s POS (which product was sold, to whom, when)

• Nowhere else

If a customer complains about the quality, you can’t trace it back to the raw material batch, the roasting date, the roaster who made it. The thread is broken.

If you want to know how much raw Ethiopian is left in inventory and when to reorder from your supplier, you have to manually count the production warehouse and subtract what was sent to outlets. That takes an hour.

If you want to know which outlets have what stock, you have to call each manager individually or check their POS reports one by one.

The batch of coffee exists at the roaster. Then it disappears. Then it reappears at the outlet as stock.

What happened in between lives in someone’s head.

Why This Is A Uniquely Indian Problem

Ask a founder running a furniture exporter if they have a supply chain problem. They’ll say no.

Ask them: “Do you know where every piece of raw material is right now? Which workshop it’s in? Which finished piece it belongs to?”

Pause.

Ask them: “How do you know when to reorder from your suppliers?”

Another pause.

Ask them: “Has a retailer ever complain about receiving damaged goods? And did you know which production batch it came from?”

Now they’re talking for twenty minutes.

The problem is real. But they don’t use the word “supply chain.”

“Supply chain” belongs to Walmart. To Unilever. To P&G. It implies ocean freight, third-party logistics, global procurement departments.

It doesn’t belong to someone running a roastery and 19 cafes. Or a workshop and 15 retail locations. Or a bakery and 22 outlets.

And yet.

The structural problem they’re solving every single day is exactly the same. Just compressed. Smaller scale. Faster velocity.

Raw material → Production unit → Finished good → Distribution → Outlet → Customer.

That’s a supply chain. They just don’t call it that.

The Software Gap

So this operator looks for software.

On one side: POS systems. Petpooja. RestroWorks. Toast. These see retail. They see what was sold at each outlet. They’re excellent at that. They manage billing, customer data, inventory at the outlet level.

But they stop at the outlet wall.

They don’t ask: where did this coffee come from? Which batch? When was it produced? What raw material is in it?

Petpooja is designed for a restaurant that buys finished goods from suppliers. Perfect for that. But you’re not buying finished goods. You’re making them.

On the other side: ERP systems. Odoo. SAP. ERPNext.

These see production. They manage procurement, GRN (goods received notes), production orders, batch tracking, serial numbers, inventory at the production level.

But they cost ₹5L-25L to implement. They take 2-12 months to go live. They require a dedicated IT team to run them. They’re built for manufacturers with an IT department, not for a founder managing three production units and nineteen outlets simultaneously.

ERPNext (the free, Indian-friendly option) is technically possible. But the implementation complexity is identical to Odoo. You still need a technical team. You still need 6-12 months. You still face the disruption.

And the founder in question doesn’t have a technical team. He has a business that’s growing, and he’s managing it by sheer force of will and good judgment.

So he can’t use POS (it doesn’t see production).

He can’t use ERP (it’s too expensive, too slow, too technical).

So he uses what he can stitch together manually. A notebook in the production unit. A spreadsheet for accounts. WhatsApp for communication between units. Memory held by one or two people who know the whole operation.

This works. Until it doesn’t.

The Moment It Breaks

You’re in a meeting with your operations person.

She says: “We made 500 kg of our signature blend last week. This week, we’ve only sold 180 kg across the nineteen outlets. Where’s the rest?”

You don’t know.

You call the production manager. He says: “Should be in the warehouse. Let me check the notebook.”

Twenty minutes later: “180 kg went to outlets. 150 kg is sitting in the warehouse waiting for outlet 7 to reorder (they have plenty in stock). The rest is... I’m not sure. Let me ask.”

It turns out 50 kg was sent to outlet 12, but outlet 12’s POS doesn’t show it clearly (maybe they mis-entered the SKU, or the outlet manager recorded it differently). 40 kg was damaged during transport. It’s written in someone’s WhatsApp, not recorded anywhere official.

So you have: 180 kg sold, 150 kg in warehouse, 50 kg at outlet 12 (but not visible), 40 kg damaged and written off, and 80 kg completely unaccounted for.

That’s ₹80,000 worth of coffee beans.

You have no idea where they are.

This is not a business failure. Your business is successful. But you can’t see your own inventory.

That’s the moment.

That’s when you realize the gap isn’t theoretical.

What This Gap Costs

For a three-production-unit, nineteen-outlet operator doing ₹8Cr combined revenue:

Inventory blindness: You can’t see raw materials, work-in-progress, or finished goods accurately. So you over-buy some raw materials (spoilage, waste) and under-buy others (stockouts, missed orders). 3-5% margin hit. ₹24L-40L annually.

Traceability nightmare: When a customer complains or there’s a quality issue, you can’t trace it to the batch, the production date, the raw material supplier. You can’t do root-cause analysis. You can’t improve. You just replace the product and apologize. ₹8L-15L annually in quality issues + customer refunds.

Distribution coordination chaos: Moving products from production units to outlets is manual. You don’t have unified demand visibility. Outlet 7 is overflowing with inventory. Outlet 14 ran out yesterday. You’re constantly doing emergency transfers, expedited shipping, manual rebalancing. ₹10L-20L annually in inefficiency.

Time waste: The founder and operations person spend 15-20 hours weekly answering questions that should be automatic: “How much do we have?” “When should we make more?” “Which batch is this?” “Why is outlet 5 low on stock?” ₹5L-8L annually (opportunity cost of their time on data work instead of strategy).

Growth ceiling: You could scale to 30-40 outlets, but the manual system would break. You know it. So you don’t grow. You leave market opportunity on the table. ₹50L-1Cr in lost revenue opportunity annually.

Reorder and raw material optimization: You can’t forecast what you’ll need because you can’t see consumption patterns across outlets. So you order conservatively. You have safety stock sitting around (waste). Or you run out and face urgent orders (disruption). 2-3% supply chain inefficiency. ₹15L-25L annually.

Batch rotation and expiry management: Without visibility, you don’t know which batches are oldest. Coffee that’s been roasted for 90 days (and is past prime) sits on a shelf while fresher batches move faster. You don’t rotate inventory optimally. ₹5L-10L annually in freshness loss.

Total annual cost of living in the gap: ₹72L-137L annually.

For a ₹8Cr business, that’s 9-17% of revenue trapped in the gap.

Why The Gap Exists

Software companies are rational. They optimize for their market segment.

POS vendors optimize for restaurants (or salons, or gyms) that buy finished goods from suppliers and sell them to customers. That’s a massive, clear market. Tens of thousands of outlets. Simple model: buy finished → sell at retail.

ERP vendors optimize for manufacturers large enough to afford a dedicated IT team and a 12-month implementation. That’s a high-value segment.

Both are rational bets.

But there’s a gap in between: the operator who produces and sells. The roastery with 19 cafes. The workshop with 15 retail locations. The bakery with outlets.

In India, this category contains hundreds of thousands of businesses.

Estimates suggest roughly 600,000 mid-market operators sit in this gap—too complex for POS, too small (or too fast-moving) for traditional ERP.

Manufacturing software opportunity in India: $4.6B in 2025, projected $13.5B by 2034.

But no software has been built specifically for this produce-and-sell segment.

So they stitch things together. Tally for accounts. Spreadsheets for inventory. WhatsApp for coordination. Memory for traceability.

The Vocabulary Problem

Here’s something interesting: if you ask these operators if they have a “supply chain problem,” most will say no.

Ask them if they know how much coffee they have in inventory across all locations.

They’ll pause.

They don’t use the word “supply chain.” That word belongs to Fortune 500 companies.

They say “my production” and “my outlets” and “my stock.”

But the structural problem they’re describing is exactly supply chain: the visibility and coordination required to move goods from raw material through production through distribution to point of sale.

The vocabulary is the cage.

Because if a founder thinks they don’t have a supply chain problem (because “supply chain” is a Walmart word), they don’t go looking for a supply chain solution.

They go looking for better POS software. Or they hire an operations person and hope they can hold it together in their head.

But the real problem isn’t in the POS. It’s in the gap between production and POS.

Who Lives Here

Multi-location F&B chains with production units (bakeries, coffee roasters, spice brands, ice cream makers, juice brands).

Furniture and leather exporters with owned retail distribution.

Medical device manufacturers with owned retail channels.

Ceramic and pottery producers with retail outlets.

Specialty chemical processors with B2B + B2C distribution.

Dairy and dairy product processors.

Textile manufacturers with retail locations.

Agri-processors (spice mills, rice mills, oil mills).

Pharmaceutical manufacturers with owned clinics or distribution.

D2C/FMCG brands manufacturing their own products and selling through owned outlets.

All of them face the same structural problem: they operate across the gap. They produce and sell. They need to see the whole chain. But no software sees the whole chain.

There are roughly 600,000 such operators in India.

They all live in this gap.

The Catch-22

You know what you need.

You need software that:

• Connects production data (raw materials, production batches, finished goods) to outlet data (sales, stock, customer feedback)

• Gives you visibility into where every batch of product is right now

• Lets you trace any finished good back to the raw materials and production date

• Helps you optimize inventory across production units and outlets

• Doesn’t require a six-month implementation or an IT team

• Costs something reasonable (not ₹25L)

That software doesn’t exist.

Or rather: you could theoretically string together Tally (for accounts) + ERPNext (for production) + Petpooja (for outlets) + a BI tool (for dashboards).

But implementing and maintaining three different systems, training your team on each, handling integrations when they break, paying for three subscriptions?

That’s its own implementation nightmare.

So you don’t do it.

You stay in the gap.

Using spreadsheets and WhatsApp and memory.

Making decisions based on incomplete information.

Leaving ₹72L-137L annually on the table.

The Opportunity

Here’s what’s interesting: the gap is not a technology problem. It’s a market structure problem.

There’s massive demand in the gap. Hundreds of thousands of Indian operators that would pay handsomely to solve this problem.

But there’s almost no supply.

The software that could serve this market would need to:

• Connect production to retail visibility (not replace POS, not require enterprise ERP)

• Make batch traceability native to the system

• Provide unified inventory and demand visibility across all nodes

• Enable automated insights (not just dashboards)

• Be designed for founder-scale complexity (not enterprise IT)

• Deploy in weeks, not months

That’s a real opportunity.

But almost nobody’s building it.

So the gap remains.

And hundreds of thousands of operators continue to live in it, paying the price.

The Future

The operators that escape this gap first will win.

They’ll have visibility. They’ll optimize production. They’ll reduce waste. They’ll improve quality through traceability. They’ll make data-driven decisions about inventory, reordering, and distribution.

They’ll grow faster than the operators who stay stuck in spreadsheets.

The gap won’t exist forever.

Someone will build for it.

The question is: when they do, will you still be stuck in the gap?

Or will you be one of the operators who escaped?

Note: This gap isn’t hypothetical. If you’re running 2-10 production units and 5-30+ outlets, you’re living in it right now. You might not call it that. You might just call it “how our business works.” But that ₹72L-137L annual cost is real. It’s paid through inventory inefficiency, quality issues, distribution chaos, time waste, and growth you’re not capturing.

The gap is real.

The question is: how long will you live in it?

Thanks for reading! Subscribe for free to receive new posts and support my work.