Skip to content
FarMart OS cover

FarMart OS

Product Designer · 2022–continuing

Company

FarMart

Year

2022–continuing

Type

Product Design

FarMart’s internal operating system for the agri commodity B2B business. Designed since 2022, from basic orders to full trade, finance, and ops across the company.

Visit FarMart OS →Read coverage in BusinessLine →

Overview

FarMart OS is FarMart’s operating system for the whole agri commodity B2B business. FarMart does around YYY Cr of GMV every month. The orders behind that volume are processed on FarMart OS.

Only part of that, around XX Cr every month, comes through the FarMart app. The rest, which is still the main share of the business, happens offline: an on-ground agent goes to the supplier, discovers the supply, and creates the order on FarMart Pro. All of it still lands in the same operating system.

It is used by the business team across procurement, sales, finance, HRMS, and ops. People from different departments log in to handle their part of the same trade: from a buyer’s sales order to supply, payments, and access rights.

I started designing FarMart OS in 2022, and I have owned its design ever since as it grew from a few basic order screens into the platform the company runs on today.

Who uses it, and how it connects

FarMart OS is the place where the company runs what happens around the FarMart app.

  • Corporate / business teams use OS in the office to create orders, check work, raise payments, manage KYC, and control who can do what.
  • On-ground associates use a companion Android app called FarMart Pro. The name sounds fancy; it is not a “premium” version of the FarMart app. It is simply the app procurement associates and sales associates use in the field. When the business is offline, they go to the supplier, discover the supply, and create the order there so it enters the system.
  • In practice, field associates are the makers. Someone from the business team at the corporate office is the checker, reviewing and approving what comes in.

Supplier-facing KYC can also start from the FarMart app as self KYC, while teams can run onboarding and KYC work from OS too. I wrote the KYC and payout pieces up separately: Supplier KYC and Supplier Payout.

What we built in 2022

Year one was small on purpose. We started with the basics:

  • Creating purchase orders and sales orders
  • Basic procurement order flows

That was enough to begin running trades on one internal platform instead of scattered sheets and chats. Everything else came later as the business and the FarMart app grew.

What FarMart OS does today

Today it is one integrated platform the whole business uses end to end. A typical flow looks like this:

  • Take a sales order from a buyer: Capture what the buyer wants to buy.
  • Float that price on the FarMart app: Push the buying price out so suppliers on the app can see it.
  • Share on internal WhatsApp groups: Keep field and ops teams aligned while supply is being found.
  • Get the supply: Match demand with agri output suppliers who can fulfill it.
  • Raise a purchase order to the supplier: Formalize the buy from the agri output supplier.
  • Create dispatch orders against those POs: Break fulfillment into individual dispatch orders.
  • Onboard suppliers and run KYC: Bring suppliers onto the platform, including KYC from OS, with self KYC also available on the FarMart app.
  • Raise and make payments: Pay suppliers and transporters against the work done.
  • Create debit notes and credit notes: Record adjustments as deals move.
  • Reconcile payments from buyers: Match what buyers paid against what the system expects.
  • HRMS-style access and rights: Give people in the system the right permissions for their role.
  • Buyer credit checks: Support the people responsible for checking a buyer’s credit before the business takes risk.

From sales order to supply, dispatch, money, and access control, the same platform holds the work.

How I have worked on this

  • 2022: starting solo. I designed FarMart OS from the first screens. If it shipped in year one, I designed it.
  • 2023 onward: building with a team. I hired designers who started helping on OS and across other FarMart products. Over these four years, Jai, Mishthi, Simran, and Krati have all worked across the products. I set direction and the quality bar; they shipped real modules and flows; we reviewed before engineering took things forward.
  • Still shipping myself. Even with help, I have kept designing the central operating flows myself as the platform grew into what the business runs on every day.

So when I say FarMart OS shipped, I mean both: work I designed with my own hands, and work the team shipped that I directed and reviewed.

Outcomes

  • One internal operating system for FarMart’s agri commodity B2B business, used across procurement, sales, finance, HRMS, and ops.
  • A clear path from a few basic PO and sales-order screens in 2022 to a full trade and finance workflow today.
  • A working link between the FarMart app (suppliers), FarMart Pro (on-ground makers for offline discovery and order creation), and OS (office checkers and operators).
  • The platform that processes FarMart’s YYY Cr GMV / month, of which about XX Cr comes through the FarMart app and the rest still comes in offline through Pro.