# A Custom App for Your Trade: KiloChand, from Fruit Market to Phone

**Which calculation in your trade is still done with a calculator and a guess? That calculation might be the idea for an app that saves you money.**

> To build a custom app for a trade, first go to the workplace and find the pain that repeats, then calculate just one number that matters. In KiloChand that number is the true cost per kilo of produce, including transport and spoilage. The app is offline and still in field testing, so it is not ready for everyone.

Author: Saman Ghahreman · Published: 2026-10-19 · Updated: 2026-10-19 · Canonical page: https://solocodelab.com/en/blog/custom-app-for-your-trade-kilochand-case-study/

At five in the morning in the fruit and vegetable market, a wholesale buyer buys from several stalls, hires a pickup and cannot tell until noon what each kilo really cost. We built [KiloChand](https://solocodelab.com/en/products/kilochand/) for this. This article shows where an app for a trade starts and where you must stay honest.

## Why doesn’t a wholesale buyer know their real profit?

Because three costs are scattered: each stall’s price with its quality grade, the pickup fare for the whole load, and the produce that spoils and earns nothing. They usually add up in the head or on the back of an invoice, and the selling price is a guess.

| By hand at the market | Problem | In KiloChand |
| --- | --- | --- |
| Summing invoices from several stalls | Separate invoices added up mentally | One invoice per stall with grade, weight and amount |
| Spreading the pickup fare | The fare covers the whole load, not one item | Automatic split by weight or value |
| Selling price per kilo | A guess that ignores the fare | Worked out from your margin, discount and fare, then rounded |
| Spoiled produce | The money is gone but not in the books | Spoilage is recorded and subtracted from profit |

### From market pain to app
1. **Go to the market**: See the real work instead of guessing from a desk.
2. **One key number**: The true cost per kilo, with fare and spoilage.
3. **Design offline**: There is no signal at five in the morning; everything stays on the phone.
4. **A small first version**: Invoices and prices first, then sales and spoilage.
5. **Field test**: Try it with a real buyer and fix it from their feedback.

## How do you spread the pickup fare across items?

Finance calls this “landed cost”: side costs such as freight are added to the price of the goods. There are two ways to spread the fare and the answers differ. The example below is made up and only shows the method.

- Say you bought 100 kg of tomatoes at 20,000 toman per kilo and 50 kg of cucumbers at 40,000 toman per kilo, and the total fare is 150,000 toman.
- Spreading by weight: the fare is 1,000 toman per kilo, so 100,000 toman for the tomatoes and 50,000 for the cucumbers. Because a pickup charges for weight, this is usually the more sensible way.
- Spreading by value: both items are worth 2 million toman, so the fare splits in half: 75,000 toman each. That is 750 toman per kilo of tomatoes and 1,500 toman per kilo of cucumbers.
- The takeaway: the spreading method must match how your trade really works. KiloChand has both and defaults to weight.

## Why must the app be offline?

Because the market hall has weak signal and the buyer has no time to wait. “Offline-first” design means all the work happens on the phone and the internet is optional; Android’s own guidance recommends this approach. KiloChand has no account, no server and no monthly fee.

## Where should you not rely on KiloChand?

- It is not publicly released yet and is in field testing; it may have bugs.
- It is not official or tax accounting; it is only your own buying and selling notebook.
- It was not built for other trades: the grading and the 54 ready items are for fruit and vegetables.
- The suggested selling price is a guide; you and the market set the final price.
- It has no automatic sync between several phones.

## How do I start for my own trade?

1. Follow your own work for a full day and note every place you used paper, a calculator or a guess.
2. Pick the one that would make you money if it were exact.
3. Build only that, as a small first version. For costs, read the [mobile app cost guide](https://solocodelab.com/en/blog/mobile-app-cost-guide/).
4. See a live sample before you pay; that is what [live sample first, then pay](https://solocodelab.com/en/blog/show-live-sample-before-you-pay/) means.
5. Try it yourself with one or two colleagues for a month, then refine it.

More apps that one person built for one specific problem are in the [case study of four Persian offline apps](https://solocodelab.com/en/blog/solo-built-persian-apps-case-study/).

> Run a trade with a repetitive, painful bit of bookkeeping? [Send a short brief](https://solocodelab.com/en/contact/?service=android-app-development) and get a written proposal and a live sample for [Android app development](https://solocodelab.com/en/services/android-app-development/); you see the sample first, then you pay.

## Frequently asked questions

### How do you build a custom app for a trade?

Go to the workplace first and find the repeating pain, then calculate just one key number, build offline, test the small version with a real user and only then expand it.

### Who is KiloChand for?

Wholesale buyers of fruit and vegetables who buy from several stalls. It records each stall’s invoice, the pickup fare, the selling price per kilo, sales and spoilage, and shows real profit.

### Does KiloChand work without internet?

Yes. All data stays on the phone, with no account and no server.

### Where can I get KiloChand?

It is not publicly released yet and is in field testing. If you are a wholesale fruit buyer and want to try the beta, write via the contact page.

## Sources

- [Landed cost](https://en.wikipedia.org/wiki/Landed_cost) — Wikipedia
- [Build an offline-first app](https://developer.android.com/topic/architecture/data-layer/offline-first) — Android Developers
- [Data layer: offline-first design](https://developer.android.com/topic/architecture/data-layer) — Android Developers
