Skip to main content
GullySystem
Hospitality

Product Management for Cafes and coffee shops

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.

Every espresso drink, cold brew and croissant has a size, price and recipe. A seasonal latte is added and retired by date. Prices change in one place for every till.

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.
Cafes and coffee shops

How the business operates.

A cafe sells a few hundred small tickets a day. Each flat white uses beans, milk, a cup and a lid, and every one of those is bought from a different supplier.

Counter billing and drink menu

Bill dine-in and takeaway tickets with sizes, milk choices, extra shots and add-ons, and send each ticket to the espresso bar screen in order.

Drink recipes and cost per cup

Set grams of beans, millilitres of milk, syrup pumps and cup size for every drink, so the cost of a cortado or an iced mocha is known.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Counter billing. Bill dine-in and takeaway tickets with sizes, milk choices, extra shots and add-ons, and take payment by cash, card or wallet at the till.
  • Bar screen and ticket queue. Send each ticket to the espresso bar and the kitchen pass in the order taken, with hot and iced drinks marked so the bar can plan its pulls.
  • Drink recipes and cost per cup. Set grams of beans, millilitres of milk, syrup pumps and cup size for every drink, so the cost and margin of a cortado or an iced mocha is known.
  • Beans, milk and packaging stock. Count beans by bag, milk by carton and cups by sleeve, with usage taken from drinks sold and a low-stock flag raised before the roaster’s order cut-off.

Operational bottlenecks to check

Drink cost is guessed, not known

A cortado and a large oat latte use different shots, milk and cups, but both sit at one price in the till. Margin by drink is never worked out. The menu drifts with supplier rates.

Pastry waste is written on a slate

Croissants, cookies and sandwiches are ordered by habit and thrown away at closing. Nobody records the count by item, so the next morning’s order repeats the same surplus.

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. Opening

    The opening barista logs the grinder dial-in, counts the float and checks the pastry delivery against the baker’s slip. The shift lead sees stock flags for beans, milk and cups.

  2. 2. Order

    The cashier enters the ticket with size, milk choice and extra shots, for dine-in, takeaway or a pre-order. The ticket appears on the bar screen in the order taken.

  3. 3. Make and serve

    Baristas mark drinks done. Usage of beans, milk, syrup and cups is deducted using each drink’s recipe, and food items are deducted from the pastry case.

  4. 4. Restock

    Items below their reorder level go onto a purchase order for the roaster, dairy or bakery. Deliveries are checked against it and the supplier invoice is kept beside the receipt.

  5. 5. Close

    The cashier closes the drawer by payment type, records pastry leftovers and splits tips by hours worked. Differences are shown before sign-off.

  6. 6. Review

    The owner reads margin by drink, waste by pastry, regulars who have lapsed and each site’s takings, then adjusts the menu or the next supplier order.

Industry reports to connect with

  • Margin by drink, size and milk choice
  • Beans, milk and cups used against bought, by site
  • Pastry delivered, sold and binned, by item and day
  • Loyalty cards redeemed and regulars lapsed for a month

Questions before implementation.

When should cafes and coffee shops 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