The till is the POS in Business Made's Operations area. A tab is an ordinary order (sf_order) with channel: "pos", so reports, Orders and refunds see it like any web order. The floor is made of service points (service_point): tables, seats, bays, rooms. Arrivals wait in the check-in queue, which is a workflow: each guest waiting is a task on reservation-checkin-pipeline. Lines sent to be made become tickets on prep-pipeline, one per station. Both pipelines are created the first time they are needed.
This page is the order of work for one service day. The screens are described elsewhere; link to them rather than repeat them:
- what staff press, screen by screen: Take orders and payments at the till and Floor and check-in (Business Made docs);
- the same jobs on the phone: Point of sale and checkout, Take payment, Tabs, floor and reservations, Service day playbook;
- the records underneath: Locations and service points, Check-in workflow, Menu and stock, Printing.
Bookings made ahead are a different job: see Booking type and availability and Bookable chairs, rooms or tables. A phone order paid later by invoice is Phone order for a customer.
The AI's tools
The AI Agent and AI Employees have bm_* tools for this work (src/ai/skills/business-made.skill.ts). They call the same server code as the screens. Everything else is a call_appengine to the route the screen uses.
| Job | Tool | Route |
|---|---|---|
| Open a tab | bm_open_tab | POST storefront/pos/tab |
| Read tabs | bm_list_open_tabs, bm_list_closed_tabs, bm_get_tab | GET storefront/pos/tabs, …/pos/tabs/closed, GET storefront/order/<sk> |
| Add lines | bm_add_items_to_tab | POST storefront/order/<sk>/items |
| Send to stations | bm_fire_to_kitchen | POST storefront/order/<sk>/fire |
| Split | bm_split_tab | POST storefront/pos/tab/<sk>/split |
| Take a payment | bm_settle_tab | POST storefront/pos/tab/<sk>/settle |
| Refund a payment | bm_refund_tab_payment | POST storefront/pos/tab/<sk>/refund |
| Print the check / receipt | bm_print_check, bm_print_receipt | POST …/print-check, POST …/print-receipt |
| Table on a tab | bm_assign_service_point_to_tab, bm_release_service_point_from_tab | POST …/assign-service-point, POST …/release-service-point |
| Table status | bm_set_service_point_status, bm_clear_service_point | POST storefront/service-point/<id>/status, POST checkin/service-point/<id>/clear |
| Queue | bm_walk_in, bm_check_in_reservation, bm_assign_queue_task_to_sp, bm_notify_queue_task, bm_mark_queue_task_no_show, bm_remove_from_queue | POST checkin/walk-in, …/from-reservation/<id>, …/<taskId>/assign, /notify, /no-show, /leave |
| Queue reads | bm_get_queue, bm_get_queue_summary, bm_get_queue_position, bm_list_available_service_points, bm_get_upcoming_reservations | GET checkin/queue, …/queue/summary, …/queue/position/<taskId>, …/service-point/available, …/upcoming |
| Counts | bm_counts | none: always use it for "how many open tabs / in the queue / bookings today" |
These have no tool, so use call_appengine: close a tab, void a tab or a line, the money breakdown, discounts, the tab's customer, the receipt and check as data, sending a receipt, the books check, and retrying accounting or stock.
Three tool descriptions don't match what the server does (tested):
bm_open_tabsays aservicePointId"does NOT occupy". It does: the table goes tooccupiedwith this tab on it. Sendoccupy: falseto attach only.bm_set_service_point_statussays it clears the occupant when leaving occupied. It doesn't:currentTabId, the party size and a seated booking stay. Usebm_clear_service_pointto empty a table.bm_refund_tab_paymentsaysamountdefaults to the whole payment. Withoutamountthe refund is refused (step 10). Always send it.
Ask first
- Which location? Every tab, table and queue belongs to one business location, by its
name(main-store), not its title. See Business locations, hours and sales tax. - The party: a name, and an email or phone if they want to be told when their table is ready. How many people. Any booking.
- What they ordered: each product's SKU (exactly as on the product), quantity, choices, seat and notes, and which station makes it.
- How they pay: cash (and how much was handed over), check (its number), house account, a gift card's code and PIN, the customer's store credit or points, or card. Any tip.
- For a refund or void: which tab, which payment, how much, and for cash, whether the cash has already been handed back.
Steps
1. Operations › POS: before service
Check that the till can work at this location. Nothing here changes anything.
| Check | Call | What it says |
|---|---|---|
| The location's tax | the location's taxRate / taxName | Every tab is taxed at its location's rate when lines change and at payment (Business locations, hours and sales tax). |
| May this operator use the till? | GET storefront/pos/readiness?businessLocationId=<name> (&permissionScope=alcohol for one kind of product) | { allowed, effect, blocking, warnings, reasons }. A person with no employee record answers allowed: true, staff: false (tested). Requirements on the pos gate are set in Training and readiness. |
| Card terminal | GET storefront/pos/card-terminal?location=<name> | state: ready, none, hub-offline or terminal-offline. With none: "No card terminal is connected at this location. Connect one in Operations › Devices to take card payments." (tested). |
| Printer and drawer | the location's data.pos | receiptPrinter, checkPrinter, cashDrawer ({ hubName, endpointName }), printReceiptOnSettle, openDrawerOnCashTender (both on unless false). With no config, the first active printer device at the location is used (Printing). |
| What's off the menu | the 86 list and day-parts | Menu and stock |
| Who is expected | bm_get_upcoming_reservations (GET checkin/upcoming?businessLocationId=&windowHours=12) | Bookings not yet checked in, with minutesUntil, isLate, isImminent. |
| Free tables | bm_list_available_service_points | Points with status available. The whole floor, any status: GET checkin/service-point?businessLocationId=. |
Hands on: the location name.
Check: open Operations › POS (/operations/pos) with that location picked in the top bar.
2. Operations › Check-in: the waiting queue and seating
A walk-in: bm_walk_in, POST checkin/walk-in:
{ "businessLocationId": "main-store",
"customer": { "name": "Ana Diaz", "email": "[email protected]", "phone": "+12145550100" },
"partySize": 3, "preferences": { "window": true }, "notes": "birthday", "quotedWaitMinutes": 15 }customer needs a name, email or phone; with none: "customer is required (name/email/phone)" (tested). With an email or phone, the guest is found or created as a customer (source walk-in), with no welcome email (tested). A walk-in also gets its own reservation record (source: "walk-in", pending), and the queue entry is a task at stage 0 (Waiting).
A booking arriving: bm_check_in_reservation, POST checkin/from-reservation/<reservation id> ({ partySize?, notes? }). It is refused for a booking that is cancelled, no_show or used (tested: "Reservation is used — cannot check in"), and with "Already in the check-in queue" while one entry is still waiting.
Reading the queue: bm_get_queue returns the waiting tasks, oldest first, each with an enrich block: waitedMs, isOverdue, queuePosition, displayName. bm_get_queue_summary gives { inQueue, avgCurrentWaitMs, longestCurrent }. bm_get_queue_position gives one guest's position, totalInQueue and a saying such as "less than a minute" (tested). What already left the queue: GET checkin/queue/history?businessLocationId=&sinceMs=86400000.
Holding a table for a booking: POST storefront/service-point/<table>/status with { "status": "reserved", "reservationId": "<booking>" }. The hold runs to heldUntil: the booking's start plus its booking type's Check-in by minutes, else 15 (tested). Check-in then seats only that party there. A table already occupied, or held for another booking, is refused.
Seating: bm_assign_queue_task_to_sp, POST checkin/<taskId>/assign { servicePointId } (the point's name or id). The table goes to occupied with the booking and party size on it, the queue entry to Assigned (done), and the booking to used (tested). It is refused for a table that is occupied or held for another booking, and for a section ("That is a section — pick a table in it"). A dirty or blocked table is not refused (tested: a party was seated at a dirty table), so check the status first.
Stop: seating a guest who gave an email or phone sends them reservation-ready (email, subject "We're ready for you") and reservation-ready-sms at once (tested on a @test.local address). bm_notify_queue_task sends them again. Say who will be told, and send a notify only when asked.
When a guest goes:
| Tool | Route | What it does |
|---|---|---|
bm_remove_from_queue | POST checkin/<taskId>/leave { reason } | The entry is cancelled with "Guest left: pending (tested). |
bm_mark_queue_task_no_show | POST checkin/<taskId>/no-show | The entry is cancelled as no-show and the booking marked no_show. A table held for that booking is released to available. It also takes a booking id that was never queued. |
Hands on: the table's name, and the guest seated there.
Check: Operations › Check-in (/operations/check-in, ?openId=<taskId> for one entry) and Operations › Floor (/operations/floor?point=<table sk>).
3. Operations › POS: open the tab
bm_open_tab, POST storefront/pos/tab:
| Field | What it does |
|---|---|
businessLocationId | The location name. Sets the tax rate and the business day. |
servicePointId | Opens the tab at a table (name or id). The tab is named after the table and the table goes to occupied with this tab on it (tested). occupy: false attaches only. A party already seated there by check-in becomes the tab's customer, with their booking's notes (tested). |
alias | A name ("Smith party"). Without one and without a table: Walk-up #<n>, counted per location per business day. |
partySize, customer | Optional. customer is { sk, name, email, phone }. |
requestId | 8 to 100 characters, one per new-tab action. Sending it again returns the same tab instead of a second one (tested). Always send one. |
The tab starts new, with a 9-character number (E0A5URDDK) that the receipt, refunds and Books use, and tabDay, the business day in the location's time zone.
To put a known customer on later: POST storefront/pos/tab/<sk>/customer { customerId } (or null to clear). The tab is re-priced for their groups (Price lists and customer-group pricing).
Hands on: the tab's sk and number.
Check: Operations › Tabs (/operations/tabs) shows it; the POS opens it at /operations/pos?tab=<sk>.
4. Operations › POS: ring it up
bm_add_items_to_tab, POST storefront/order/<sk>/items:
{ "items": [
{ "sku": "BURGER", "quantity": 2, "options": [{ "name": "prepStation", "value": "grill" }],
"seat": "1", "course": "mains", "specialInstructions": "no onions" },
{ "sku": "COKE", "quantity": 1, "options": [{ "name": "prepStation", "value": "bar" }] }
] }| Rule | What happens |
|---|---|
| Price and tax | From the product (and its chosen options and volume tiers), never from the request unless you send unitPrice on purpose. Tax is the location's rate on taxable lines. Tested: 2 × $12 + $3 at 8.25% gave subtotal 27, tax 2.23, total 29.23. |
| The SKU | Found without regard to case, and a variation's own SKU sells that variation. Unknown: 404 "Product not found: |
| The station | Where a line is made is its prepStation option, and only that. The screens copy it from the product's prepStation attribute; the API and bm_add_items_to_tab don't, so send it yourself. A line without one goes on a shared ticket with no station (tested). |
| A fee or deposit with no product | { "itemType": "fee", "name": "Room deposit", "unitPrice": 50 }. Never taxed, never sent to a station (tested). |
| A gift card sold at the till | Its line is priced at the chosen amount, untaxed, never sent to a station. The card is issued when the tab is paid (Gift cards). |
| Changing a line | "updates": [{ "id": "<line id>", "quantity": 3 }], { "id", "delta": 1 }, { "id", "remove": true } or { "id", "specialInstructions" }. A line already sent is refused (tested: "… has already been sent to the station and can't be changed or removed …"). |
| Restricted products | A product with restriction.ageRestricted (scope alcohol, etc.) is checked against the operator's readiness. A refusal is 423 readiness_block; an override goes in the body as override (Training and readiness). |
| After a payment | Refused: "This tab has a recorded payment. Use a new tab for additional items." (tested). |
Discounts (only before any payment):
| Call | Body | Notes |
|---|---|---|
POST storefront/pos/tab/<sk>/discount-code | { code } | Checked like checkout (Discount codes). Refused: 400 DISCOUNT_CODE_REFUSED with the reason (tested: "… Discount code not found"). One code per tab. Remove: …/discount-code/remove. |
POST storefront/pos/tab/<sk>/manual-discount | { type: "percent" | "fixed", value, reason }, or { remove: true } | A reason is required (tested: "Say why the discount is given …"). Applied after codes and promotions. Tested: 10% off 27 gave discount 2.70, tax 2.00, total 26.30. |
Hands on: each line's id.
Check: bm_get_tab: the lines, subtotal, tax, total and balanceDue.
5. Operations › Prep line: send to the stations
bm_fire_to_kitchen, POST storefront/order/<sk>/fire { itemIds, course?, seat?, specialInstructions? }. The lines are grouped by station: one ticket per station on prep-pipeline, titled <tab> · <station> (tested: a grill ticket, and one with no station for the line without one). Each sent line carries its ticket's taskId; that is what "sent" means. Sending them again: "All requested items are already fired" (tested). Nothing is sent by adding lines; only this call sends.
A ticket moves Received → Prepping → Ready → Delivered. Stations see them on Operations › Prep line (/operations/prep-line?station=grill) and move them there. bm_get_tab shows each line's ticket under task (stageName, status). To mark one finished: POST workflow/task/<taskId>/complete (tested). Tickets have no one assigned, so moving them notifies nobody (tested: no messages).
A line sent by mistake: POST storefront/pos/tab/<sk>/lines/<lineId>/void { reason }. The line comes off and is kept under voidedLines, the tab is re-priced, and its ticket is cancelled or the line taken off it (tested). It is refused once the tab has taken a payment; refund instead.
Check: the ticket on Prep line, and the line's task on the tab.
6. Operations › POS: the check, and splitting
The money, as the till shows it: GET storefront/pos/tab/<sk>/breakdown?tipPercent=18&split=2 (read only). It returns subtotal, discount, tax, total, paid, balanceDue, tipOptions (15, 18, 20, 25 % of the subtotal before tax), tip, dueNow, and splitOptions for 2 to 5 ways. Tested on 29.23: 18% tip 4.86, split in two 14.62 + 14.61.
The check before paying: GET …/check-payload returns the printed lines as data (header from the location, *** CHECK ***, lines, totals; tested). bm_print_check (POST …/print-check) sends it to the location's check printer, else its receipt printer. With none: { ok: false, error: "no printer found — configure location.data.pos.receiptPrinter or attach a printer device to the hub" } (tested).
Splitting (bm_split_tab, POST …/split), only before any payment:
| Body | Result |
|---|---|
{ itemIds, alias?, sourceAlias? } | Those lines move to a new tab (alias, default "sourceAlias if given (split by seat). Both stay on the same table. Sent lines keep their tickets (tested). |
{ parts: 3, alias? } | The lines are spread over 3 tabs by value, a line of several split into units if needed. With fewer items than parts: 400 SPLIT_TOO_FEW_ITEMS, "… take 3 payments of an equal part of the balance on this tab instead." (tested). |
After a payment: "Split the tab before recording payment; a paid sale snapshot cannot be redistributed" (tested). To share one bill after that, take several payments on it (step 7).
7. Operations › POS: take the payment
bm_settle_tab, POST storefront/pos/tab/<sk>/settle { amount, method, gateway?, ref?, tip?, tendered? }. Each call records one payment; take as many as the bill needs. The server re-prices the tab first, so the total is always its own.
| Tender | How | Notes |
|---|---|---|
| Cash | { amount, method: "cash", tendered? } | Cash may be more than is due: the payment is what was due and the rest is change. Tested: 30 on 25.98 recorded 25.98 with tendered: 30, change: 4.02. tendered on a part payment works out change for that share (tested: 2 paid from 5, change 3). |
| Check, other, house account | { amount, method: "check", ref: "1001" } (other, house) | No more than is due. Tested: "Payment of 40.00 exceeds the 29.23 due … overpayment is only accepted on cash tenders". |
| Gift card | First POST storefront/giftcards/redeem { code, pin?, amount, orderNumber: <tab number>, idempotencyKey, context: { channel: "pos" } }. Then settle with method: "gift_card", gateway: "giftcard", ref: <its transactionId>. | Without the redemption: "Redeem the gift card first …" (tested). A card holding less pays what it holds. See Gift cards. |
| Store credit or points | First POST finance/customer-wallets/spend, then settle with method: "store_credit" or "reward_points", gateway: "wallet", ref: <its transactionNumber> | Without it: "Use the store credit or points first …" (tested). See Store credit and reward points. A tab whose lines are all bought with points: POST …/redeem-points { operationKey }. |
| Card | Only on the location's card terminal: POST …/terminal-charge { amount, tip?, chargeKey }, which waits up to 2 minutes for the customer. Declined: 402 CARD_DECLINED. No terminal: 409 NO_CARD_TERMINAL. Without a terminal, the POS screen can take the card in a Stripe form if Stripe is connected (Take payments on the site). | A card can't be written down by hand. Tested: method: "card" gave 400 CARD_ON_TERMINAL, and gateway: "terminal" "A card terminal payment is recorded only from the terminal's own approval." |
Stop: taking a payment records money and posts it to Books, and a card or gift card tender really takes it. Say the tab, the amount, the tender and the tip, and wait for yes. A card on the terminal is the cashier's to run with the customer; the AI never starts one.
What a payment does (storefront.pos.service.ts settlePosTabNow, tested where marked):
- It is an
sf_transactionand a line in the tab'spayments, with who took it. The tab becomespaid-partialorpaid(tested). - When the tab is paid in full, its table goes to
dirty(tested). Gift cards sold on it are issued and the customer's points earned. A code's use is counted. - Books: once paid in full, one sale entry: sales revenue and sales tax payable credited, each tender's account debited (tested: 4000 credit 24.00, 2100 credit 1.98, 1000 Cash debit 25.98). A tab paid in parts waits for its last payment and then books once. Tips go to a liability, not revenue. Gift cards sold go to gift card liability.
GET storefront/order/<number>/booksshows whether every payment is in Books (tested:inBooks: true). - Stock: once paid in full, tracked products leave the tab's location's stock. A stock problem never fails the payment; it shows in the answer's
stock.status: "needs_attention"with the reason (Stock: adjust, count, receive and transfer). - Devices: the receipt prints on the location's receipt printer, and a cash payment opens the drawer, if those are set up (step 1). Neither ever fails the payment.
If accounting or stock needs attention: fix the cause, then POST …/retry-accounting or POST …/retry-stock.
Hands on: each payment's transactionId.
Check: bm_get_tab: status, amountPaid, balanceDue: 0, and the payments.
8. The receipt
| Call | What it does |
|---|---|
GET …/receipt-payload?copy=customer (or merchant) | The receipt as lines, for a client with its own printer. Tested: header, lines, tax, total, CASH 30.00, Change 4.02. |
bm_print_receipt (POST …/print-receipt?copy=) | Prints it again on the location's printer. Same "no printer found" answer when there is none. |
POST …/send-receipt { email? , phone?, mode? } | Emails (pos-receipt, subject "Receipt #pos-receipt-sms) it. Falls back to the tab's own email or phone; with neither: "No recipient — pass to, email, or phone, or save a contact on the tab first." (tested). |
Stop before sending a receipt: it reaches the guest. Use the address they gave.
9. Operations › Tabs: close the tab and reset the table
POST storefront/pos/tab/<sk>/close { markDirty? }. The tab becomes completed and leaves the open list. It is refused while money is owed (tested: "This tab still owes 29.23. Take the payment, or void the tab if the guest walked out.") and while a sent line's ticket is still open ("… still open at the station … Close the tab once the ticket is done.").
The table: if another check from the same table is still open (a split by seat), the table passes to it (tested). Otherwise its occupant is cleared and an occupied table goes to dirty (markDirty: false for available).
When the table is ready again: bm_clear_service_point (POST checkin/service-point/<table>/clear { finalStatus: "available" }). It empties the party, the booking and any hold (tested).
Other moves:
| Need | Call |
|---|---|
| Move a tab to another table | bm_assign_service_point_to_tab { servicePointId, occupy: true }. Refused across locations. It does not check the table: an occupied one or one held for another booking is taken (tested). |
| Take a tab off its table | bm_release_service_point_from_tab { markDirty? }. The tab stays open; the table goes to dirty or available (tested). |
| Block, close or mark a table dirty | bm_set_service_point_status { status, reason }: available, occupied, reserved, dirty, blocked, closed. Only the status changes (see the warning above). |
Check: Operations › Tabs with ?view=closed lists the tab as Completed; Operations › Floor shows the table's state.
10. Refunds and voids
| Situation | Call | What happens |
|---|---|---|
| Nothing paid: walk-out or opened by mistake | POST …/void { reason } | The tab is cancelled, its tickets cancelled, its table freed (tested). |
| Part paid, guest walks out | POST …/void { reason, moneyReturned: true } | Without moneyReturned: 409 "2.00 was collected on this tab. Voiding hands it back …" (tested). With it: the money is recorded as handed back (card tenders refunded through the provider), and the sale, tax and what was owed come back out of Books (tested). |
| Paid in full | bm_refund_tab_payment (POST …/refund) { transactionId, amount, reason, operationKey, cashReturned? }, once per payment | Voiding is refused for a paid tab. The refund goes back to where the payment came from: cash recorded as handed back, a gift card or wallet back onto its balance, Stripe through Stripe. A card taken on the terminal can't be refunded yet. |
Refund rules (services/pos-refund.service.ts, tested):
operationKey(8 to 100 letters, digits,_,-) is required, and the same key retried is the same refund.amountis required, up to what is left on that payment: "Refund must be greater than zero and no more than the remaining 25.98".- Cash needs
cashReturned: trueonce the cash is back with the guest: "Cash refund: send cashReturned: true once the cash has been handed back to the guest". - A full refund turns the tab
refunded, and Books gets the mirror of the sale (tested: 4000 debit 24.00, 2100 debit 1.98, Cash credit 25.98). Tips are not refunded. A refunded tab takes no more payments. - A refund doesn't put stock back. Count it back in by hand (Stock).
The same refund from Orders works for a till sale: Refund, cancel or return an order.
Stop: a void or refund gives money back and changes the books, and voiding a tab that has the customer's email sends them order-cancellation. Say the tab, each payment, the amount and where it goes, and for cash, ask whether it has been handed back. Wait for yes.
11. End of day
- What is still owed:
bm_list_open_tabsgivessummary.owing,summary.owedandpaidAwaitingClose;GET storefront/pos/tabs?businessLocationId=&unpaid=truelists only tabs still owing. Each needs a payment, a void or a word with the manager. - Paid but not closed: close them (step 9).
- The day's tabs:
GET storefront/pos/tabs/closed?businessLocationId=(pages withp,ps,q,mode=location|card|name). - Books: each tab's
posAccounting.statusshould becomplete;GET storefront/order/<number>/booksper tab;retry-accountingorretry-stockwhere one needs attention. The day's figures are in Financial reports.
There is no register shift or cash-up to close (see What it can't do yet).
Every message, and when
| Moment | Template | To |
|---|---|---|
| A queued guest is seated | reservation-ready (email), reservation-ready-sms | the guest's email and phone, if given |
| Notify on a queue entry | the same two | the same |
| Send receipt | pos-receipt / pos-receipt-sms | the address given, else the tab's |
| A gift card sold on the tab is paid for | the gift card emails | its recipient (Gift cards) |
| A tab is voided | order-cancellation | the tab's email, which is set when the tab was opened with a customer (code: storefront.order.service.ts orderCancel). A tab with no email sends nothing (tested). |
Opening, ringing up, sending to stations, paying, closing and refunding send nothing to the guest (tested on tabs with no customer email).
When it's done
Tell the person: the tab (name, number, table), what was on it, the total with tax, each payment (tender, amount, tip, change), whether it is closed, and the table's state. For a refund or void: what went back, to which payment, and that Books was reversed. For the floor: who was seated where, who is still waiting and for how long, and who was told their table is ready. Open the tab at /operations/pos?tab=<sk>.
What it can't do yet
- No register shifts or cash-up. There is no opening float, cash count, drawer session, X or Z report, or "close the day". The drawer only opens on a cash payment, through the printer. Check the day with step 11 and Financial reports.
- A line's SKU is kept as typed. Lines are found without regard to case, but the SKU is saved as sent, and stock looks it up exactly. Tested: a line added as
skilltest-pos-burgerfor productSKILLTEST-POS-BURGERpaid fine, but stock answered "Cannot identify one product for skilltest-pos-burger; check its SKU" (storefront.pos.service.ts2059). Send the product's own SKU. - The API doesn't route lines to stations by itself. Only the screens copy the product's
prepStation. Send it on each line (step 4). - Refund needs
amount, though the route's description andbm_refund_tab_paymentsay it is optional (services/pos-refund.service.ts51–52). - Card payments taken on the terminal can't be refunded from Appmint yet: "Refunds back to the card through the terminal are not available yet".
- A table hold doesn't end by itself.
heldUntilis only a note: nothing releases the table when it passes, or when the party is seated at a different table (tested: the held table stayedreservedfor a booking alreadyused). Only a no-show releases it. Clear it by hand. - Seating and moving tabs don't check every status. Check-in seats a party at a
dirtytable (tested) or ablockedone (code:checkin.service.tsassign), and moving a tab takes an occupied or held table (tested). - A walk-in who leaves the queue keeps a
pendingbooking (tested). - Two closed walk-in tabs can't both be deleted. Every tab with no customer is named "Walk-in", and Trash refuses a second record of the same name: "A trash with name "Walk-in" already exists." (tested;
history.service.ts312). Tabs are rarely deleted; void them instead.
Don'ts
- Don't take a payment, refund or void without the person's yes for that tab and amount.
- Don't record a card by hand, or start a terminal charge; the cashier runs the card with the customer.
- Don't send
cashReturned: trueormoneyReturned: trueuntil the cash is really back with the guest. - Don't settle a gift card, store credit or points tender without redeeming or spending it first.
- Don't add lines to a tab that has a payment; open a new tab.
- Don't trust
bm_set_service_point_statusto empty a table; usebm_clear_service_point. - Don't send a receipt or a "table ready" notify without saying who it reaches.
- Don't open a tab without a
requestId; a retry would open a second one.