Skip to main content
GullySystem
Hospitality

Point of Sale Billing for Cafes and coffee shops

Record counter sales, payments and the resulting stock movements.

Retail and POS

Does this function belong in your operation?

Use when staff complete customer purchases at a physical counter.

A customer completes an in-person purchase.

Takeaway cups, dine-in plates and a pre-order for an office meeting are billed at the counter. Milk swaps and extra shots change the price on the ticket. The barista’s screen shows the same order.

Bring the records the workflow depends on.

  • Item catalogue and prices
  • Payment methods
  • Counter and receipt settings

Outputs to check

  • Counter bill and tender record
  • Shift settlement statement
  • Return and discount exception log

Follow the point of sale billing workflow.

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

  1. 1. Prepare the basket

    Select or scan items and review quantities.

  2. 2. Apply commercial rules

    Check prices, discounts and customer eligibility.

  3. 3. Take payment

    Record the permitted tenders and their actual outcomes.

  4. 4. Issue the bill

    Finalise the sale under the approved numbering and stock rules.

  5. 5. Close the shift

    Compare recorded tender totals with counted or settled amounts and investigate differences.

Who uses the module, and who approves?

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

Counter staff

Selects items, reviews discounts, records the permitted payment method and issues the bill.

Shift in-charge

Closes the shift and counts the drawer. Explains any mismatch.

Owner

Sees today’s sales, by hour and by counter, from wherever they happen to be.

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.

Payment fails after bill preparation

Keep the sale unpaid or void it under the agreed rule before stock is finalised.

Cash drawer differs

Record the counted amount and require a reviewed adjustment.

Return at another counter

Find the original sale and apply the authorised return process without duplicate credit.

Can this work independently?

POS needs item, price and tax settings. It can record permitted tenders independently, but payment terminals or gateways require supported connections and separate settlement checks. Stock, loyalty and customer accounts are optional handoffs; a printed bill does not prove a card payment settled.

Systems and records it connects with

  • Product management: Item identifiers, units and controlled variant definitions.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Barcodes and labels: Item-code mappings and verified printed-label values.
  • Loyalty and offers: Eligible rewards, redemptions and approved reversals.

Configure, test and introduce the workflow.

  • We spend time at your counter and note how bills are made. You get a short written note of the layout we propose. The queue tells the story.
  • Import a checked item list with rates and approved tax settings. On the intended counter hardware, test ordinary sales, discounts, split tenders, failed payments and returns. Review usability and reconcile the resulting totals before release.
  • Who may give a discount and who may take a return is fixed. Each cashier is given a personal login. The counter bills on the system and the day is closed with a cash tally. The owner reads the first closing report with the cashier. Leave room for surprises.

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.

  • Bills total the correct items and prices.
  • Split payments reconcile to the bill.
  • Counter closing highlights differences.
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 point of sale billing?

Use when staff complete customer purchases at a physical counter. A customer completes an in-person purchase.

What should we bring to the requirements discussion?

Bring anonymised examples of Item catalogue and prices; Payment methods; Counter and receipt settings. 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. Record counter sales, payments and the resulting stock movements. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Payment hardware, offline operation and tax requirements need explicit scope confirmation.

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. Bills total the correct items and prices. Use this check when reviewing the first working version.

Talk to us

Discuss point of sale billing 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