LocalFarmers operations console

The part nobody demos. Catalogue, bazars, centres and farmer onboarding — the console the operations team opens every morning.

Client: Sanjivini Eco Solutions
Category: Internal admin application
Platforms: Admin consoleCatalogue opsSchedulingOnboarding

What we built

A marketplace with no operations console can be demonstrated but not run. Every catalogue change, every new bazar, every farmer joining becomes a developer ticket — and the platform stalls at exactly the point it starts working.

So we built the console first. Everything the business changes week to week — products, categories, bazar schedules, delivery centres, farmer applications — is configurable by the operations team without engineering involvement.

Built before the buyer surfaces, not after
Catalogue and category management with bulk operations
Bazar scheduling that drives what shoppers can order
Delivery centre and coverage configuration
Farmer application review and onboarding workflow
Operated daily by non-technical staff

What the console runs

Each area maps to a decision the business makes on its own schedule.

Product & category management: Create and edit products, assign categories, set pricing and availability, and manage the imagery buyers see.
Bazar scheduling: Open a bazar for a locality and date window, choose which products it carries, and control when ordering closes.
Centre configuration: Define delivery centres and the areas they serve, which is what makes pincode serviceability answerable.
Farmer onboarding: Review applications, verify details and approve producers into the catalogue with an auditable trail.
Farmer & listing management: Maintain producer records and their listings as seasons and availability change.
Role-based access: Separate what operations staff, catalogue staff and administrators can each see and change.