Skip to main content
GullySystem
Hospitality

Product Management for Cloud kitchens

Maintain the item definitions used by sales, purchasing and stock.

Inventory Management

Does this function belong in your operation?

Use when several business processes need the same product or service definitions.

An item, service code or variant is added or changed.

A brand menu holds items, sizes, add-ons and prices per app. A sold out item is paused across every channel together. Photos and descriptions stay with the dish.

Bring the records the workflow depends on.

  • Item codes
  • Units and variants
  • Pricing and tax references

Outputs to check

  • Controlled item and variant catalogue
  • Unit and classification reference
  • Item-change approval history

Follow the product management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Request the item

    Identify its business use and check for an existing equivalent.

  2. 2. Define attributes

    Set units, variants and required classifications.

  3. 3. Review settings

    Check price, tax and stock-related references with the responsible owners.

  4. 4. Approve use

    Release the item to permitted transactions.

  5. 5. Maintain history

    Control changes and retirement without rewriting earlier documents.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Counter or sales staff

Finds the item by whatever they call it, and sees the rate and what is in stock.

Store and purchase

Adds new items with their units, rates and reorder levels before the first delivery arrives.

Owner

Controls who may change a rate. In most shops that is a very short list.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate item discovered

Review linked transactions before merging or retiring a code.

Unit changes after use

Preserve historical quantities and define any conversion for future entries.

Item discontinued

Restrict new use under the agreed rule while retaining old orders and stock history.

Can this work independently?

The catalogue can exist independently, but sales, purchasing and stock must use its identifiers to share records. Prices and taxes may be maintained in separate controlled settings. Adding an item does not create opening stock or confirm that it is available to sell.

Systems and records it connects with

  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Purchase order management: Authorised supplier commitments and open line balances.
  • Barcodes and labels: Item-code mappings and verified printed-label values.

Configure, test and introduce the workflow.

  • We look at your sheet and counter software. You provide an export, and we report on duplicates and gaps.
  • A coding scheme and categories are proposed. You approve them before anything is loaded. Duplicates are merged with your staff. Each decision is logged for later reference.
  • A sample of items is loaded into a test copy. You check units, rates and tax codes. Billing and stores read from the new list. A short session for each team closes the step.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Item codes are unique.
  • Units remain consistent across transactions.
  • Inactive items follow the agreed transaction rule.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should cloud kitchens consider product management?

Use when several business processes need the same product or service definitions. An item, service code or variant is added or changed.

What should we bring to the requirements discussion?

Bring anonymised examples of Item codes; Units and variants; Pricing and tax references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Maintain the item definitions used by sales, purchasing and stock. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An item catalogue does not itself manage stock movements or fulfilment.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Item codes are unique. Use this check when reviewing the first working version.

Talk to us

Discuss product management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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