Skip to main content
GullySystem
Hospitality

Business solutions for Cloud kitchens

Explore software for work such as “Menu and dish catalogue management”. Review each business function below, including when it fits and what to check before implementation.

Cloud kitchens

How the business operates.

A cloud kitchen has no dining room. It has a pass, a row of stations and three or four delivery brands that all draw on the same walk-in fridge.

Channel order intake

Bring orders from each delivery app and the brand’s own web link into one queue, tagged by brand, channel and promised pickup time.

Brand menus and item pauses

Keep a menu for each virtual brand over the same recipes, and pause an item across every brand when its ingredient runs out.

Station tickets and prep lists

Send each order to the grill, fryer, wok or cold pass as separate tickets, and build the morning prep list from expected orders.

Packing and rider handover

Mark an order packed, sealed and labelled, then confirm the rider’s pickup time so waits at the hatch can be read by channel.

Shared walk-in stock by brand

Deduct ingredients from the shared fridge as dishes are cooked, and read consumption brand by brand against what was bought.

Brand profit and app payouts

Set commission, packaging and promotion cost against each brand, and match every payout statement to its orders and deductions.

Recipe cards and portion costs

Write each dish as a recipe with grams per ingredient and a packaging line. Cost per portion moves when a supplier price changes. Two brands share one card.

Wastage and spoilage log

Record trim, burnt batches, expired sauce and dropped orders with the reason and the cook on shift. Stock falls by the same amount. Waste can be read brand by brand.

Complaints and refund claims

Log a missing item, a spilled bag or a late arrival against the order, with the customer’s photo. Claims to the app start from that entry. Refunds follow to the payout.

Hygiene and temperature logs

Staff tick opening and closing checks, and key in walk-in and freezer readings where no sensor is fitted. Missed entries show on the manager’s list. Audit sheets print by date.

The records that hold the operation together.

  • Channel order intake. Bring orders from each delivery app and the brand’s own link into one queue, tagged by brand, channel and promised pickup time, with accept and reject rules.
  • Brand menus and item pauses. Keep a separate menu for each virtual brand over shared recipes, and pause an item on every brand at once when its ingredient runs out.
  • Station tickets and kitchen screens. Split each order into tickets for grill, fryer, wok and cold pass, and show the pass which parts of a combo are still open.
  • Prep lists and batch cooking. Build the morning prep list from expected orders, record gravies and marinades made in batches, and note the discard time of each batch.
  • Recipes and portion cost. Set grams of protein, rice, sauce and garnish per dish, and read the plate cost for each brand’s version of a shared item.
  • Shared walk-in and dry stock. Receive goods from vendors, deduct ingredients as dishes are cooked, and read consumption brand by brand against what was bought.
  • Packing and packaging stock. Mark orders sealed and labelled, and track boxes, bags, cutlery and sachets per brand so packaging cost enters each order.
  • Rider handover and wait times. Record rider arrival and pickup, read waits at the hatch by app, and flag orders likely to be marked late before they leave.

Operational bottlenecks to check

Each app is a separate tablet

Orders, menu edits and item pauses are handled app by app. A dish sold out on one brand stays live on another, and the kitchen cooks an order it cannot finish.

Every brand draws on one walk-in

Chicken, rice and sauces are shared across menus, yet stock is counted once a week. Nobody knows which brand consumed the chicken thighs or the marinated wings.

Brand margin is hidden by commission

A virtual brand shows strong sales on its app, but after commission, packaging, promotions and refunds the figure is unclear. Which brand earns money stays a guess.

Rider waits cause cold boxes

Packing is not timed against rider arrival. Food sits at the hatch, riders wait and the app marks the order late. Complaints and refunds follow.

Payout statements cannot be matched

Deductions for cancellations, ad spend and disputed refunds arrive as a lump, and checking them against orders takes a day of spreadsheet work each cycle.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Menu and brand setup

    Each virtual brand gets its menu, prices and packaging. Recipes are shared. Item availability is controlled once and pushed to each channel as far as its access allows.

  2. 2. Order intake

    Orders from each delivery app and any direct link enter one queue, tagged by brand and channel with a promised pickup time. The manager accepts or rejects against kitchen load.

  3. 3. Cook

    Each order splits into tickets for the grill, fryer, wok and cold pass. Cooks mark their part done, and the pass sees when every part of a combo is ready.

  4. 4. Pack and hand over

    The packer seals the box and adds the label. Then the order is marked packed. The rider’s arrival and pickup time are recorded so waits at the hatch are measured.

  5. 5. Stock and prep

    Cooked dishes deduct their recipes from the shared walk-in. Tomorrow’s prep list is built from expected orders and what the fridge already holds.

  6. 6. Settle

    Each app’s payout statement is matched to its orders, commission, refunds and penalties. The owner reads profit by brand after all deductions.

Roles and responsibility boundaries.

For owners

See profit by brand after commission, consumption against purchases, refund rates by app and payout shortfalls, without opening three dashboards.

For kitchen managers

Accept orders against load. Pause items. Read the prep list and watch rider waits at the hatch.

For line cooks

See tickets for your own station, mark parts done and flag an ingredient running short before the next batch.

For packers and runners

Check each box against its ticket. Seal it. Hand it to the right rider.

For store keepers

Receive vendor deliveries, count the walk-in and record wastage of batches that passed their discard time.

Reports your managers need.

  • Orders by brand, channel and hour
  • Ingredient use by brand against purchases
  • Plate cost and margin after commission by dish
  • Rider waits at the hatch by app
  • Refunds and complaints by dish and cook
  • Payout statements matched to orders and deductions
  • Batch discards for marinades and gravies

Connections to scope

  • Delivery app order feeds
  • Kitchen printer and screens
  • SMS and messaging
  • Email
  • Payment gateway
  • Accounting export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Brand menus and recipes

Each virtual brand’s menu, prices, packaging and shared recipes go in first, the way your kitchen builds them today.

Station layout

Grill, fryer, wok, cold pass and packing bays are named as your kitchen runs them, with screens or printers at each.

Channel routes

Which delivery apps feed orders directly and which need manual entry is confirmed app by app during implementation.

Commission and fee rules

Each app’s commission, ad fees and penalty rules are entered so brand profit shows after every deduction.

Opening stock and vendors

Vendor lists, rates and opening walk-in counts come across from your sheet or register.

Hosted by GullySystem

Hosting stays with us, which keeps the pass, the stores and the owner on one set of records, and our staff make menu and commission edits when asked.

Limitations to settle before implementation

  • A restaurant that mostly serves guests at tables will find Restaurant Management System closer.
  • A kitchen cooking for events, buffets and bulk contracts will find Catering Management Software closer.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Menu and dish catalogue management
  • Rating recovery, with a plan for complaints
  • Separate identity for each brand from the same kitchen
  • Corporate lunch accounts with a fixed quote sheet
  • Pricing that accounts for commission and packaging
  • Packaging that arrives intact
  • A list of customers who have agreed to be contacted
  • Search listing for the area the kitchen can actually serve
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements