> For the complete documentation index, see [llms.txt](https://dukarun.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dukarun.gitbook.io/docs/daily-operations/serving-before-payment.md).

# Serve items before collecting payment

## Why this matters

A customer may order another round before paying. Tables keeps served items on the same receipt so payment can settle what was actually served.

## Before you start

Your plan must include **Tables**, and the business setting must be enabled. Work in the intended counter and cashier session. There are eleven temporary receipt slots. They belong to the local device workspace, user, counter and session; they are not shared physical-table assignments or bookings.

## Steps

1. Open **Sell** and choose a temporary receipt slot.
2. Add and check the items, quantities and prices.
3. Choose **Serve** to record the items as served.
4. Return to the same receipt to add and serve further items.
5. If needed, print a **Service note · Unpaid**. It includes served items, not unsent drafts.
6. Collect payment when the customer is ready. Print the paid receipt after settlement.

## What changes in Dukarun

Serving records the batch's stock consumption and costs. Collecting payment settles the same receipt without consuming stock again. Ordinary customer-credit sales use the standard sale workflow; do not assume every ordinary-sale payment option applies to Tables.

Supported offline service stays on the device for replay after reconnection. Another device cannot see unsynced local work. Keep the device available and review held work before closing. When resolving a receipt, record the reason and whether the stock was returned or consumed.

## Related guides

* [Send a sale to a cashier](https://dukarun.gitbook.io/docs/daily-operations/sending-a-sale-to-a-cashier.md)
* [Close the day](https://dukarun.gitbook.io/docs/daily-operations/closing-and-whatsapp-summary.md)
