Skip to main content
GullySystem
Hospitality

Business solutions for Cafes and coffee shops

Explore software for work such as “Weekday work-from-cafe crowd”. Review each business function below, including when it fits and what to check before implementation.

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.

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 before the roaster’s cut-off time.

Pastry case and closing waste

Record the baker’s delivery, what sold and what was binned at closing, so the next order is set against real leftovers by item.

Loyalty card and regulars

Tie a phone number to each regular, count drinks toward a free one and see who has not visited in a month.

Shift cash-up and tip pool

Close each drawer by payment type, compare it with the till, and divide card tips across staff by hours worked on that shift.

Roaster and supplier orders

Raise a purchase order to the roaster, dairy and bakery, check each delivery against it, and keep the invoice beside what arrived.

Opening and closing checklist

Grinder calibration, milk fridge temperature, float count and till reconciliation are ticked off by the opener and the closer. Missed items are shown to the manager. The café lead reviews it each shift.

Allergen and menu notes

Every drink, sandwich and pastry carries its allergens, milk options and syrup ingredients. Counter staff see them when ordering. A seasonal item is added once and shows everywhere.

Roaster and wholesale accounts

Offices and neighbouring shops that buy bags of beans or catering trays are held as accounts, with their standing orders and invoices. Deliveries are planned around the morning rush.

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.
  • Pastry case and closing waste. Record the baker’s delivery, items sold and items binned at closing, so tomorrow’s order is set against real leftovers by croissant, cookie and sandwich.
  • Loyalty card and regulars. Tie a phone number to each regular, count drinks toward a free one, apply offers at the counter and list regulars who have not visited in a month.
  • Grinder and machine log. Log grinder dial-in, group head cleaning and descaling dates for each espresso machine, with the next service due shown to the shift lead.
  • Shift cash-up and tip pool. Close each drawer by payment type, compare it with the till, and divide card tips across the shift by hours each barista worked.

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.

Milk, beans and cups run out mid-service

Dairy, oat milk, house beans and takeaway lids are checked by eye. A shift lead finds the oat drink empty during the lunch rush, and the roaster needs a day to deliver.

Loyalty stamps live on paper cards

Ten-drink cards are lost, stamped twice or never redeemed. The owner cannot identify lapsed regulars or count the complimentary drinks served last month.

Cash-up and tips are settled by memory

Drawer shortfalls, card tips and the staff pool are divided at closing from a scribbled sheet. A barista who disagrees with the share has nothing to check against.

Follow the work across teams.

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

  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.

Roles and responsibility boundaries.

For owners

See margin by drink, pastry waste, takings by site, tips paid out and supplier spend, without waiting for a Sunday stock count.

For baristas

Read tickets on the bar screen, log the grinder dial-in and mark drinks done. Report low oat milk early.

For cashiers

Take orders and payments, apply a loyalty reward, and close the drawer by cash, card and wallet with a clear difference at the end.

For shift leads

Check pastry deliveries and count the case at closing. Raise supplier orders. Approve swaps on the rota.

Reports your managers need.

  • 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
  • Drawer difference and tip pool by shift
  • Roaster, dairy and bakery orders against deliveries
  • Machine descaling and grinder service dates due

Connections to scope

  • Card terminal
  • Digital wallets
  • SMS and messaging
  • Email
  • Kitchen printer
  • 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.

Your drink menu and sizes

Espresso drinks, filter coffee, teas, cold drinks, milk choices and extra shots go in first, priced the way your counter sells them.

Recipes and supplier rates

Bean grams, milk volumes and cup sizes are entered for each drink, with the roaster’s and dairy’s current rates so cost per cup is true.

Tip and rota rules

How tips are pooled, how swaps are approved and which hours count follow what your team already agrees.

Regulars and opening stock

Customer phone numbers, loyalty counts and opening stock of beans and packaging come across from your notebook or sheet.

Receipts and messages

Receipt layout, tax settings per country and loyalty messages by SMS or messaging app are set during implementation.

Hosted by GullySystem

Every site reads one menu and one stock list because the records live on a server that GullySystem runs for all of you. Menu and recipe edits come from GullySystem staff.

Limitations to settle before implementation

  • A mobile coffee cart with one grinder and a tap-to-pay reader can run on a card terminal and a notebook.
  • Full-service restaurants with table service and a large kitchen will find Restaurant Management System closer, and bakeries that mainly sell by weight will find Bakery Management System 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.

  • Weekday work-from-cafe crowd
  • Weekend brunch
  • Birthday and small group bookings
  • Coffee subscriptions and takeaway packs
  • Delivery through Swiggy and Zomato
  • Specialty coffee and single-origin brews
  • Catering for offices nearby
  • Loyalty and repeat-visit programmes
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