A HealthDarpan productChefSathi

Product

The operating system behind your WhatsApp number

ChefSathi is built for cloud kitchens, tiffin operators, bakeries, catering-led businesses, and food brands that already sell on WhatsApp and now need structure: a real storefront, configurable checkout policy, financial discipline, owner control, safer launches, and a way to keep direct customer ownership instead of feeding aggregator commissions.

Storefront

A real ordering storefront opened from WhatsApp

Customers should be able to open a fast storefront from WhatsApp, browse the real menu, and place an order in a cleaner flow than free-form chat. ChefSathi keeps the storefront anchored to the reviewed catalog, so the business is not relying on guesswork to decide what was actually ordered.

  • WhatsApp webview-friendly storefront
  • Catalog-backed menu and item selection
  • Supports fixed menus and custom daily menus
  • Customer ordering without losing WhatsApp as the relationship channel
  • Reviewable catalog behavior before go-live

Checkout policy

The business decides how checkout should work

ChefSathi should not hardcode one order-confirmation model for every kitchen. Some businesses want manual confirmation. Some want auto-confirmation. Some want payment before confirmation. The product should let the tenant choose the operating policy instead of forcing a universal checkout flow.

  • Direct storefront order creation as the normal regular-order path
  • Manual confirm, auto-confirm, or prepaid-only confirmation
  • Pay later, pay after confirmation, or pay now
  • WhatsApp handoff and operator confirmation remain available where needed

Money

Payments, invoices, and dues behind the same number

ChefSathi keeps financial truth close to the customer relationship. Payments, invoices, and due tracking stay anchored to the same WhatsApp-led business instead of being rebuilt later from memory or screenshots. That matters for repeat tiffin customers and larger catering settlements just as much as daily orders.

  • Ledger-backed payment recording
  • Invoice and statement workflows
  • Razorpay-style pay-now links, pay-later flows, and manual rails where needed
  • Keep margin instead of giving away commission on customers you already own

Operations

Prep and reporting for businesses that already run on chat

The product is not a consumer app pretending to be an operations tool. It is a management layer for kitchens, tiffin operators, bakeries, and catering-led businesses that already sell on WhatsApp and now need consistency, prep visibility, storefront discipline, and end-of-day clarity.

  • Prep visibility and operator flow
  • Reporting shaped for owners and finance
  • Tenant-specific behavior, not one-size-fits-all logic

Launch

Onboarding, validation, and controlled rollout

A tenant should not jump from a sign-up form to full automation. WhatsApp connection, catalog review, storefront policy, payments, validation, and launch mode should be visible, staged, and safe.

  • Meta/WhatsApp status tracking
  • Storefront and payment policy readiness
  • Validation before go-live
  • Shadow, soft launch, and full automation modes

What it is not

Not a marketplace. Not a consumer app. Not AI theatre.

ChefSathi helps operators keep direct customer ownership while adding business discipline behind the same WhatsApp channel. The system should feel like kitchen infrastructure for cloud kitchens, bakeries, tiffin operations, fixed menus, custom daily menus, native-language ordering, storefront checkout, and catering workflows, not a glossy demo that collapses at first contact with production. The business case is simple: own the customer relationship, stop paying marketplace commissions on repeat demand you already generated, and keep manual control when the system is not confident enough to automate safely.