creekpos · Classic Desktop
Share restaurant items and payments · Classic Desktop
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Cashier / manager
Required tools
Tables and split payments. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Named fractional guest shares are supported by the cloud-connected till and online table bill. Classic Desktop has its existing bill splitting and partial-payment controls; do not assume the new browser guest plan editor is a native screen. Online prepaid QR credits currently require their existing settlement/release path rather than silently assigning them to named shares.
Steps
- Open the held order from Tables and choose the native split/payment action.
- Use Split by items for whole or decimal quantities. Review how the original discount is allocated between the resulting held orders.
- For shared money, use Pay a part with equal parts or typed amounts. For 100.00 split three ways, review 33.34, 33.33 and 33.33.
- Verify recorded parts before taking the closing payment. Named guest fractions are an Online/cloud-till feature, not a native Desktop dialog.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Named fractional guest shares are supported by the cloud-connected till and online table bill. Classic Desktop has its existing bill splitting and partial-payment controls; do not assume the new browser guest plan editor is a native screen. Online prepaid QR credits currently require their existing settlement/release path rather than silently assigning them to named shares.