Skip to main content
GullySystem
Hospitality

Multi-Outlet Stock for Cafes and coffee shops

Keep outlet stock separate while supporting controlled transfers.

Retail and POS

Does this function belong in your operation?

Use when physical stock is held across several selling outlets.

Goods move between outlets or staff need another outlet's availability.

A second cafe borrows a sack of beans from the first, and the transfer is recorded on both sides. Every shop sees its own stock. Pastry waste is compared outlet by outlet.

Bring the records the workflow depends on.

  • Outlet and item list
  • Stock by location
  • Transfer approval rules

Outputs to check

  • Outlet availability view
  • Transfer dispatch and receipt record
  • Combined stock reconciliation

Follow the multi-outlet stock workflow.

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

  1. 1. Check outlet balances

    Use current item quantities by location.

  2. 2. Request the transfer

    Identify the receiving need and dispatching outlet.

  3. 3. Approve and dispatch

    Record actual quantities leaving the source.

  4. 4. Acknowledge receipt

    Count the goods at the destination and record differences.

  5. 5. Reconcile availability

    Close the transfer only after both sides agree the movement.

Who uses the module, and who approves?

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

Outlet manager

Runs their own shop, asks for transfers and answers for their own count.

Counter staff

Checks the other shop before making a promise to a customer standing in front of them.

Owner

Compares the shops. The same items in the same month with different results are now a reason to look into it.

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.

Receiving outlet counts short

Record the difference and keep it unresolved until both custodians agree.

Goods sent to wrong outlet

Create a traceable redirection rather than silently changing the destination.

Concurrent sales consume stock

Recheck availability before confirming the transfer or customer promise.

Can this work independently?

This requires item identifiers and balances for each outlet. A standalone transfer register can coordinate moves, but actual stock records must acknowledge both dispatch and receipt. POS and warehouse links update movements; viewing another outlet's stock does not reserve it.

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.
  • Warehouse management: Storage locations, picking instructions and count results.
  • Transport documents: Consignment details and authorised movement-document references.

Configure, test and introduce the workflow.

  • We list your shops, stores and who runs them. You provide current stock and rate lists. A diagram of how stock should move comes back.
  • Balances are loaded outlet by outlet. A manager signs off on each list. Request, dispatch and receipt are tried between a pair of shops. Notes from staff reshape the screens.
  • Local rates and offers are entered where they differ. You review them against shelf prices. Remaining shops join in turn. Owners see combined and separate figures together.

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.

  • Transfers debit and credit the correct outlets.
  • Unreceived goods remain in transit.
  • Outlet totals reconcile with the combined stock view.
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 multi-outlet stock?

Use when physical stock is held across several selling outlets. Goods move between outlets or staff need another outlet's availability.

What should we bring to the requirements discussion?

Bring anonymised examples of Outlet and item list; Stock by location; Transfer approval rules. 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. Keep outlet stock separate while supporting controlled transfers. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Recorded stock is not a reservation or promise of availability without the relevant workflow.

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. Transfers debit and credit the correct outlets. Use this check when reviewing the first working version.

Talk to us

Discuss multi-outlet stock 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