Working

Adapted build
Custom

SunnyERP

Farm to table, on one operating system.

[ where it started ]

First, the problem.

We are a vegetable processing business working across more than one facility. The work is procurement from contracted farms, batch traceability from raw material to finished product, quality checks on the floor, GST invoicing, and knowing what each batch actually costs us.
Existing ERPs were built for finance teams of fifty, in a Western context. We run lean, and we comply with regulations specific to this country — FSSAI, GST, e-way bills. Tally is for accounting, and it should stay that way — it was never meant to run operations. SAP is for someone else.
The people who would have to use anything we bring in are standing on the floor, on a phone, possibly wearing gloves — not sitting at a desk. We wanted something organised around the way our business actually flows, from the farm to the invoice, that our own people could use.
— Sunshine Vegetables Pvt Ltd

The business: A multi-facility vegetable processing business
Where it lived: Operations & productionInventory & procurementAccounts & compliance
Handled then: Software that does not fit us

Every solution here begins this way — with the problem written down in plain words, before any software. Write yours →

[ in production ]

Running at Sunshine Vegetables Pvt Ltd since 2024

Runs procurement from contracted farms, batch traceability, quality checks and GST-ready order-to-cash with per-batch costing for a multi-facility vegetable processing business.

The problem#

Existing ERPs were built for finance teams of fifty in a Western context. Indian SMB food processors run lean, comply with regulations specific to this country, and use tools that don't fit.

Tally is for accounting. SAP is for someone else.

The approach#

Vertical-first. Built around the actual flow of a food processing business — grower procurement, lot traceability, batch costing, warehousing, GST-ready order-to-cash. A web application, in the office and at the stations on the floor. Built to feel like consumer software, not enterprise wallpaper.

The premium-build standard isn't a luxury — it's what keeps people using the tool past month two.

— Build note, August

What it does#

Procurement from contracted farms — contracts with a price per crop and season, farm-gate intake with a QC gate, and settlements computed from the same rows the scale wrote.
Batch-level traceability from raw material to finished SKU — GS1-style lot codes generated at harvest, genealogy answered in both directions.
A shift-facing floor board — planned, ready, running, blocked, done — built for desktops and fixed terminals. A phone client is roadmap, not product.
Costing the owner actually checks — each finished batch resolves to a cost per kilo, split into farming, labour and materials.
One stock ledger across four facility types — every line carries lot, bin, quality state and expiry, and every movement records a reason.
Offline-first quality inspections — captured on a disconnected device, synced back with conflicts put in front of a person, never silently overwritten.
GST-ready order-to-cash — order to challan to tax invoice to journal entry, with GSTIN and place-of-supply on every partner. The printable GST invoice document is scoped work, named plainly in the FAQ.

What's next#

Pilot deployments across a handful of mid-sized food processors in Maharashtra and Karnataka. The two loudest gaps are named plainly in the FAQ — a phone client for the floor and a printable GST tax-invoice document. Both are scoped; neither has shipped.

If you run a food processing unit between 5–50 people and want a serious tool, the contact form is the right place to start.

[ what it does ]

The things it does well.

Grower procurement

Contracts carry a price and contracted area per crop and season; intake weighs gross and tare, records moisture and grade, and settles receipts against advances and deductions to a net payable.

Farm-gate intake with a QC gate

Every delivery moves weigh-in → QC → settle. One accepted quality reading decides the grade; a failed reading opens a hold that names the reason and withholds money against it.

Lot traceability

Saving a harvest lot generates a GS1 traceability code encoding farm, field, harvest time and grade — with the key data elements FSMA-style recall work expects.

Batch genealogy, both directions

Backward trace answers what fed a finished batch; forward trace answers where a raw lot went and which customers received it. Both resolve on the lot code, across blended runs.

Batch costing

A finished batch resolves to a total cost, a produced weight and a cost per kilo, split into farming lots, labour and raw materials — each slice traced to the records that produced it.

Warehouse execution

Facility, zone and bin hierarchy with capacity; stock lines carry lot, quality state, staging lock and expiry; an append-only inventory ledger records a reason for every movement.

Cold chain and quality control

Temperature profiles with tolerance windows per product class, excursions graded minor through critical, inspection orders raised against specifications, and non-conformance reports.

Offline-first field inspection

Inspections captured on a disconnected device sync back with deterministic conflict handling — conflict, duplicate, stale and version-conflict are distinct states a supervisor resolves.

Order-to-cash on a document chain

An order produces a challan, the challan a tax invoice, the invoice a journal entry — credit checked at order time, the whole chain visible from the order.

Multi-facility and role-based access

Four facility types scope stock, work centres, gate traffic and reporting; access is modelled through a department-role permission matrix rather than per-user flags.

[ how it arrives ]

Three ways to get it.

Adapted build
The base you see here, reshaped around your business — your branding, your workflows, your compliance details — and deployed to your infrastructure or mine. This is work I do for you, not a file you download.
Custom
Built around your problem from the start, using these parts where they fit.

[ requirements ]

What you'll need.

Platform	What you need
Office & floor	Any modern desktop browser — there is no phone layout yet
Server	Docker on a machine you control — Django with PostgreSQL + PostGIS
Hosting	Your own server or cloud account, or hosted by us

[ licensing ]

What you may do with it.

A deployment licence for your business: your data, your infrastructure if you want it, and no per-seat charge for the people on your floor. You are not locked in. Your data is yours and exportable in full at any time, including if you decide to stop working with me.

[ questions ]

What people ask.

Do I have to replace Tally?

No. Most businesses keep Tally for statutory accounting and use this for operations — procurement, batches, stock, costing, compliance. What flows between them is agreed during setup.

Is this a finished product I install, or a base you adapt?

It is a working system for a vegetable processing business, shown here as a running reference — farm to invoice, every screen real. It carries the assumptions of the business it was written for: Indian tax vocabulary, a packhouse–plant–coldstore–warehouse shape, grower contracting as the primary inbound path. We adapt and deploy it around your business; it is not a licence you install yourself.

Does my data stay mine?

Yes. It is a Django application against your own PostgreSQL database, deployed wherever you choose. There is no vendor tenant, no phone-home, no usage metering — and each deployment is separate, so nothing about your operations is visible to any other business. One practical dependency to know: field boundaries are real geometry, so the database needs the PostGIS extension.

Can my floor staff use this on a phone?

No. There is no mobile layout — the interface is a fixed desktop grid, and at phone width the content is clipped. Floor use today means a desktop or a fixed terminal; the Manufacturing floor board is the closest thing to a shift-facing screen, a card kanban with large actions, and it is still a desktop screen. A genuine phone client is unbuilt work, not a configuration setting.

How does it handle GST?

Partly, and it is worth being precise. It stores GSTIN and place-of-supply on the partner, determines tax through configured tax codes, chooses intra-state or inter-state treatment, posts GST output to the ledger, and holds IRN and QR fields for e-invoice integration. It does not yet produce a GST tax-invoice document: no CGST/SGST/IGST breakdown on invoice lines, no HSN field, no print view — and a known defect posts an intra-state pair to CGST unsplit. Total tax is right; the split is not. Budget for that work in a deployment.

What happens when the network is down?

Quality inspections are designed for it: captured on a disconnected device, synced later, with conflicts resolved by a person rather than silently overwritten — conflict, duplicate, stale and version-conflict are distinct states showing the device, capture time and reason. Everything else assumes a live connection; there is no general offline mode.

What happens if you stop supporting it?

A fair question to ask any supplier you would depend on. Your deployment includes the source: a conventional Django and React codebase with Django tests, Vitest unit tests and a Playwright end-to-end suite — no proprietary runtime, nothing compiled away from you. The honest risks are the ordinary ones: intricate domain logic, some of it documented only in code, and the known gaps this FAQ names would land on whoever picks it up. Budget for a handover.

[ tell us the problem ]

Want SunnyERP shaped around your business?

Tell us how you work today. If this is the right starting point we’ll say so, and if it isn’t we’ll tell you that instead — in writing, within three working days.

Ask about SunnyERP Talk to me

[ adjacent ]

Closer experiments.

Working

FoodNode

The members' table for India's food & agriculture industry — every link of the value chain, verified and invite-only.

Working

Sunny SCADA

A browser-native SCADA — live P&ID mimics for an ammonia refrigeration and vegetable-processing plant, built from a strict asset tree.

Working

Chief of Staff

An AI chief of staff that runs on your own machine — email, calendar, money, tasks and commitments across every business you run.

First, the problem.

We are a vegetable processing business working across more than one facility. The work is procurement from contracted farms, batch traceability from raw material to finished product, quality checks on the floor, GST invoicing, and knowing what each batch actually costs us.
Existing ERPs were built for finance teams of fifty, in a Western context. We run lean, and we comply with regulations specific to this country — FSSAI, GST, e-way bills. Tally is for accounting, and it should stay that way — it was never meant to run operations. SAP is for someone else.
The people who would have to use anything we bring in are standing on the floor, on a phone, possibly wearing gloves — not sitting at a desk. We wanted something organised around the way our business actually flows, from the farm to the invoice, that our own people could use.
— Sunshine Vegetables Pvt Ltd

The business: A multi-facility vegetable processing business
Where it lived: Operations & productionInventory & procurementAccounts & compliance
Handled then: Software that does not fit us

Every solution here begins this way — with the problem written down in plain words, before any software. Write yours →

The approach#

The premium-build standard isn't a luxury — it's what keeps people using the tool past month two.

— Build note, August

What it does#

Procurement from contracted farms — contracts with a price per crop and season, farm-gate intake with a QC gate, and settlements computed from the same rows the scale wrote.

Batch-level traceability from raw material to finished SKU — GS1-style lot codes generated at harvest, genealogy answered in both directions.

A shift-facing floor board — planned, ready, running, blocked, done — built for desktops and fixed terminals. A phone client is roadmap, not product.

Costing the owner actually checks — each finished batch resolves to a cost per kilo, split into farming, labour and materials.

One stock ledger across four facility types — every line carries lot, bin, quality state and expiry, and every movement records a reason.

Offline-first quality inspections — captured on a disconnected device, synced back with conflicts put in front of a person, never silently overwritten.

GST-ready order-to-cash — order to challan to tax invoice to journal entry, with GSTIN and place-of-supply on every partner. The printable GST invoice document is scoped work, named plainly in the FAQ.

What's next#

If you run a food processing unit between 5–50 people and want a serious tool, the contact form is the right place to start.

Three ways to get it.

Adapted build

The base you see here, reshaped around your business — your branding, your workflows, your compliance details — and deployed to your infrastructure or mine. This is work I do for you, not a file you download.

Custom

Built around your problem from the start, using these parts where they fit.

Platform

What you need

Office & floor

Any modern desktop browser — there is no phone layout yet

Server

Docker on a machine you control — Django with PostgreSQL + PostGIS

Hosting

Your own server or cloud account, or hosted by us

What people ask.

Do I have to replace Tally?

No. Most businesses keep Tally for statutory accounting and use this for operations — procurement, batches, stock, costing, compliance. What flows between them is agreed during setup.

Is this a finished product I install, or a base you adapt?

Does my data stay mine?

Can my floor staff use this on a phone?

How does it handle GST?

What happens when the network is down?

What happens if you stop supporting it?