Overview
Supplier KYC is how FarMart brings agri output suppliers onto the platform with identity, tax, and bank checks that finance and ops can trust.
Before this redesign, onboarding took about fifteen minutes per supplier. Procurement associates uploaded documents by hand. KYC executives reviewed everything by comparing images to manually entered data. The new flow pulls verified data from government APIs, asks for fewer uploads, auto-approves clear cases, and sends the rest to human review.
I owned end-to-end product design for this module across FarMart Pro (field onboarding), FarMart OS (ops review), and the link to self KYC on the FarMart app. It sits inside the broader FarMart OS operating system that runs FarMart’s agri commodity B2B business.
What it was like before
- Similar checks were repeated across PAN, GST, bank, Aadhaar, and MSME documents, with no single automated path.
- Field teams collected more than they needed for some supplier types, which slowed onboarding and cluttered review.
- KYC turnaround depended on matching document images to data typed in by hand.
- Clear cases and messy cases all sat in the same manual queue.
What we aimed for
- Cut onboarding time from roughly fifteen minutes to under three.
- Free KYC executives from repetitive verification so they spend time on exceptions.
- Get more reliable supplier data through API-backed checks, not photo uploads alone.
- Keep an audit trail when something is approved, rejected, or sent back for edits.
The constraints that shaped the design
Field reality. Procurement associates work on FarMart Pro with suppliers who may not have every document ready, or may have documents that do not match what the APIs return. The flow had to handle incomplete paperwork without becoming a dead end.
Compliance still matters. Auto-approval only when PAN, GST, bank, and name-matching criteria pass. Everything else goes to a person. We could not trade speed for a weaker check.
Two products, one journey. Field capture lives on Pro. Review and decisions live on OS. Suppliers can also start self KYC on the FarMart app. The same supplier identity has to stay consistent across all three.
How I worked on this
I designed this end to end: the Pro onboarding journey, OS verification and decision screens, error and edge cases (duplicate PAN or GST, API failures, consent pending), and the status model engineering needed to keep Pro, OS, and the FarMart app in sync.
This was not a long solo-to-team arc like the main FarMart app. It was a focused module redesign inside FarMart OS and Pro, with me owning the product design through shipping.
What we built
- FarMart Pro (field onboarding): A guided flow for procurement associates. Capture PAN (or Aadhaar for individuals), fetch linked GST and bank details, optional MSME, then supplier consent before submission. Document uploads drop sharply where APIs can verify identity, tax, and bank information.
- FarMart OS (ops review): A review layer for KYC executives to approve or reject suppliers who do not auto-qualify, with fetched API data visible alongside the case instead of scattered document images.
- Automation: Auto-accept when PAN, GST, bank, and name-matching criteria pass. Everything else goes to manual review. Draft states, consent via WhatsApp, and edit flows for GST and bank after approval sit in the same system.
- Self KYC on the FarMart app: Suppliers can also complete KYC themselves on the app, so onboarding is not only a field-associate path.
Outcomes
- Faster onboarding for field teams and for suppliers who pass automated checks.
- KYC effort shifts from re-typing and image matching to exception handling.
- Stronger audit trail from API-sourced fields and explicit approval states.
- A clearer link between FarMart Pro (makers in the field), FarMart OS (checkers in the office), and self KYC on the FarMart app.