Customer stories
Curefoods logo

How a service ticket and preventive maintenance system was set up around Curefoods' own sites, assets and approvals

Curefoods, which calls itself a House of Food Brands, builds and runs food brands out of a shared network of cloud kitchens and dine-in stores. Fieldproxy set up a mobile system for equipment service tickets and preventive maintenance around its own sites, assets, priorities and cost approvals, with both modules built a week apart in September 2025.

2020

Year Curefoods was founded (curefoods.in)

8

Food brands in the Curefoods portfolio, run from shared kitchens (curefoods.in)

1 week

Between the ticket module and the preventive maintenance module

At a glance

The challenge

Curefoods runs several food brands from a shared network of kitchens and stores, and the equipment in those sites needs both repairs when something breaks and planned maintenance before it does. Each repair can involve spare parts, local purchases and an escalation, and each needs a cost decision.

What we built

Fieldproxy set up two mobile modules around Curefoods' own way of working: a ticket flow with its own priority levels including Code Red, spare parts consumption and cost approval, and a preventive maintenance flow with scheduled, overdue, in progress and closed views. Both were built within one week in September 2025.

The results

  • Tickets accepted, rejected or reassigned with a reason
  • Spare parts and purchases recorded against each ticket
  • Before and after photos on every job
  • Overdue maintenance listed with days of delay

Want yours built around how you work, the same way?

Get Demo

A house of food brands, run from shared kitchens

Curefoods is a house of food brands, founded in 2020. Its portfolio includes Eatfit, Sharief Bhai, Olio Pizza, Arambam, Nomad Pizza, CakeZone, Frozen Bottle and Krispy Kreme, and it builds and scales these brands out of a shared network of cloud kitchens and dine-in stores.

Curefoods describes its model as kitchen first: every brand is designed around shared kitchen infrastructure, and kitchen placement is driven by order level data. When several brands depend on the same kitchen, the equipment in that kitchen has to keep running.

That makes equipment service a two sided job. When something fails, a technician needs a ticket, the right parts and, often, money to buy something locally. When nothing has failed yet, the same equipment needs planned maintenance on a schedule, with a record of what was checked.

What we built: a ticket and maintenance flow shaped around Curefoods' sites and approvals

The system is organised around Curefoods' own structure. Every ticket and every maintenance job belongs to a site, with its site code, city and region, and to an asset, with its asset code, brand and model, and serial number. Technicians work on the mobile app, with separate lists for open, in progress, Code Red, awaiting cost approval and closed work.

Code Red priority

Alongside low, medium and high, tickets can be marked Code Red, and those tickets get their own list so they are not lost among routine work.

Accept, reject or reassign

A technician decides on each assigned ticket. A rejection needs a reason, and a reassignment records who it went to and why.

Spare parts consumption

Parts used on a job are picked from the parts inventory with quantity and reason, and extra spares not in stock can be added as separate rows.

Cash requests and cost approval

A technician can request money to buy materials, with the bill number, vendor, PO number and a photo of the bill. The ticket then waits in an awaiting cost approval list.

Escalations

Any ticket can be escalated with a reason and a level, from standard handling up to immediate intervention.

Proof of work

Service activity is recorded with before and after photos, video and an uploaded service report before the ticket is closed.

Preventive maintenance on a schedule

The preventive maintenance module lists each planned job by asset and site, with its category, frequency, scheduled date and assigned technician. Jobs move from scheduled to in progress to completed, and anything past its due date appears in an overdue list showing how many days it is late.

Starting a job needs before photos. During the job the technician works through a maintenance checklist in six parts and records the parts used, the issues found, the corrective actions taken and a recommendation for the next visit. Ending the job needs after photos, an overall status, a rating and a signature, and the finished job appears in a closed maintenance report.

Two modules in one week

The service ticket module was built first. The preventive maintenance module followed a week later, using the same site and asset structure so the two sit side by side on the technician's mobile app.

Both were built for Curefoods specifically, around its sites, its assets, a Code Red priority and a cost approval step for local purchases, rather than a standard ticket template.

How it went

  1. Week 1

    Service ticket module built.

  2. Week 2

    Preventive maintenance added.

Visit Curefoods

Stop working around your software. Get one built around you.

Built around how you work. Live within a day. Changes the same day you ask.

Unlimited users, one price for the company.