Specialized POS · step-by-step handbooks
Seven operational desks extend the existing foundations. Each requires its matching optional block, parent modules, selected counter workflow and Operations access. Boarding House belongs to Real Estate.
Water and Retail include the existing sales register separately. The other five desks provide operational front desks; new payment engines remain pending. Business source setup, billing and original order/job completion use a separate authorized Business portal login.
POS sign in · Business sign in · Download complete handbook collection
Updated 22 October 2026. Use browser Print / Save PDF for a printable copy. New workflow screenshots remain pending; the matching industry guides provide diagrams and numbered Step by Step views.
Water refilling POS
Optional block: water-custody · Workflow: water-desk
Step by step
- Administrator: select the compatible retail foundation, its parent modules and the optional water-custody block. Select Water refilling POS · sales & custody in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes. Sales also requires Retail checkout access and its existing foundation prerequisites.
- Open /pos-login, choose Water refilling POS · sales & custody in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (Container movements). Use Record bottle exchange to create a record, or open History & next action on an existing one.
- Select the existing active customer and a consistent station-owned container type.
- Record issued bottles or physically received empties, with a custody note. Returns cannot exceed the outstanding quantity.
- Review customer/type balances and history. Record opposite movements to correct custody; original movements stay visible.
- Use Sales, payment & receipt for the existing Retail register: open your own cash session, review products and record actual manual tenders. Container custody is separate from that sale; a custody entry does not charge or refund a deposit.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Water demo: 3 container issue/return movements. Review outstanding balances by customer and container type; the examples leave station-owned bottles outstanding.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Container quantities only. Customer-owned bottles, refundable deposit accounting, rider deliveries and cash handover are not handled here. This desk includes the existing Retail financial checkout separately; custody/packing and checkout are not one atomic transaction.
Salon front desk
Optional block: salon-appointments · Workflow: salon-desk
Step by step
- Administrator: select the compatible professional-services foundation, its parent modules and the optional salon-appointments block. Select Salon front desk · appointments in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
- Open /pos-login, choose Salon front desk · appointments in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All appointments, Booked, Arrivals, In service, Completed). Use Book appointment to create a record, or open History & next action on an existing one.
- Select the client and active staff member. Enter the service, chair and total occupied time including processing/buffer time.
- Create the booking. Active appointments cannot overlap for the same staff member or chair; adjacent time windows are allowed.
- Record arrival, start service and completion. Use cancelled or no-show only from the permitted stages; retain evidence in history.
- Record cancellation or no-show only when offered. Keep service billing in the separately authorised Business portal. Completing an appointment does not complete or invoice a service engagement.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Salon demo: 4 appointments in Booked, Arrivals, In service and Completed. Choose a record and inspect History & next action before progressing it.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Scheduling and operational progress only. Staff qualification rules, multiple processing phases, visit checkout, deposits, rebooking and stylist commissions are not implemented. This operational desk has no new payment engine.
Laundry front desk
Optional block: laundry-custody · Workflow: laundry-desk
Step by step
- Administrator: select the compatible professional-services foundation, its parent modules and the optional laundry-custody block. Select Laundry front desk · intake & collection in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
- Open /pos-login, choose Laundry front desk · intake & collection in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All tickets, Intake, Processing, QC, Ready to collect, Released). Use Receive laundry to create a record, or open History & next action on an existing one.
- Select the client, kg or piece basis, gross quantity, tare, bag count and promised time. Pieces must be whole and have zero tare.
- Keep the generated bag codes with each bag. Progress sorting, washing, drying, packing, QC and ready with evidence; return to sorting for rework.
- At release scan/type every expected bag code exactly once and record the verified recipient and handover evidence. Verify payment separately in the billing workflow.
- Keep promised time and net quantity visible. Use History & next action to review the last evidence; use permitted rework transitions when needed. Check payment separately in commercial billing; this desk does not enforce payment before release.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Laundry demo: 4 tickets in Received, Washing, Ready and Released, each with two generated bag codes. Open the Ready ticket to practice checking every expected bag before release.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Operational ticket and bag custody only. No price/rush rules, payment enforcement, garment photos, bag splitting, representative registry or scale integration. This operational desk has no new payment engine.
Food pickup counter
Optional block: food-pickup · Workflow: food-desk
Step by step
- Administrator: select the compatible food-hospitality foundation, its parent modules and the optional food-pickup block. Select Food front desk · takeaway pickup in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
- Open /pos-login, choose Food front desk · takeaway pickup in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All pickups, Waiting for pickup, Collected). Use Prepare pickup ticket to create a record, or open History & next action on an existing one.
- Create the takeaway order in the existing food workspace. Open a pickup ticket linked to that order and enter the pickup name.
- Prepare the order in the existing kitchen workflow. A pickup ticket never changes the kitchen order or posts a bill.
- Once the kitchen order is ready or served, verify the recipient and record collected with evidence. Only one pickup ticket can refer to an order.
- If collection is blocked, an authorised kitchen operator must progress the original order to Ready in the Business portal. Refresh the desk before recording collection. Pickup does not collect money or change the kitchen order.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Food demo: 3 pickup tickets linked to 3 synthetic takeaway orders. Two are waiting, one is collected; kitchen sources include New and Ready. A New kitchen order cannot be collected.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Takeaway handover only. Restaurant billing, modifiers, table/seat splits, recipes, ingredient deduction and food cash shifts remain separate work. This operational desk has no new payment engine.
Auto repair reception
Optional block: auto-intake · Workflow: auto-desk
Step by step
- Administrator: select the compatible trades foundation, its parent modules and the optional auto-intake block. Select Auto repair front desk · intake & release in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
- Open /pos-login, choose Auto repair front desk · intake & release in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All vehicles, Arrivals, Inspection, Authorised, Work in progress, QC, Released). Use Check in vehicle to create a record, or open History & next action on an existing one.
- Create the authoritative trade job first. Attach the vehicle identifier, odometer and intake condition/keys evidence.
- Progress to inspection. An owner or manager records actual customer work-authorization evidence; changed estimated amounts require fresh authorization through inspection.
- Record work and QC. Release requires the authoritative job already completed and recipient/QC evidence. Quote approval and payment remain in their existing workflows.
- Only an owner or manager can record work authorization. Staff must obtain that review. If the agreed job estimate changes, return to Inspection and obtain fresh actual authorization. Complete the original job before release; no automatic parts issue or payment occurs.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Auto demo: 2 fictional vehicle intakes linked to existing open jobs: Received and Authorised. Seeded authorization evidence is synthetic, not customer consent.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Vehicle intake and work/release controls only. No item-level authorization, bay planning, warranty engine, automatic parts issues or payment-release enforcement. This operational desk has no new payment engine.
Retail store POS
Optional block: retail-handover · Workflow: retail-desk
Step by step
- Administrator: select the compatible retail foundation, its parent modules and the optional retail-handover block. Select Retail store POS · sales & packing in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes. Sales also requires Retail checkout access and its existing foundation prerequisites.
- Open /pos-login, choose Retail store POS · sales & packing in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All handovers, Picking, Packed, Handed over). Use Create pick/pack sheet to create a record, or open History & next action on an existing one.
- Select an existing confirmed or completed sales order. Create one pick/pack sheet with the picking instructions.
- Verify the contents and record packed. Fulfill stock through the existing sales workflow; this sheet never deducts stock.
- After the authoritative sales order is completed, verify the recipient and record handover evidence. Payment and deposit application remain in the existing order/checkout workflows.
- Complete stock fulfillment through the authoritative sales order before release. Sales, payment & receipt opens the existing Retail register; it does not retrieve a handover as a cart or automatically apply its deposit. Avoid entering a second sale for an existing completed order.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Retail demo: 3 handovers linked to existing sales orders, including Picking and Released examples. Inspect the original order before changing handover status.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Operational pick/pack evidence only. No per-line scan verification, order checkout retrieval, automatic deposit application or courier integration. This desk includes the existing Retail financial checkout separately; custody/packing and checkout are not one atomic transaction.
Services & contracting desk
Optional block: service-visits · Workflow: services-desk
Step by step
- Administrator: select the compatible trades or professional-services foundation, its parent modules and the optional service-visits block. Select Services front desk · site dispatch in counter workflow setup. Keep existing counters and assign Operations View for reading or Edit for operational changes.
- Open /pos-login, choose Services front desk · site dispatch in Workflow, then sign in with the account for this business. Business administration uses a separate login; a copied desk URL cannot change your signed workflow. On a phone use the same online browser route; use your device keyboard for form entry.
- Choose the appropriate queue (All visits, Scheduled, Dispatched, On site, Completed). Use Schedule site visit to create a record, or open History & next action on an existing one.
- Select an open job or service engagement, active staff member, site and visit window. The corresponding parent module must be selected.
- Schedule the visit; active visits cannot overlap for the same staff member. Record dispatch and arrival with evidence.
- Complete the visit with actual site evidence. Complete/review the authoritative job or engagement and issue eligible billing separately.
- A visit completion does not complete the parent job or engagement. Record delivery checks and approved work in the Business portal, then use eligible commercial billing separately. Scheduling cannot overlap for the same staff member.
- Before changing desks or sales tabs, save the form or deliberately discard it. Switching is blocked while saving. If a record changed, refresh and review its latest version before retrying.
Demo practice
Services demo: 3 site visits linked to an existing open job: Scheduled, Dispatched and Completed. Schedules are fixed examples from the seed date; check the actual date before demonstrating dispatch.
Use the matching package account supplied privately by your administrator. Demo evidence is synthetic. Reruns preserve used records and dates.
Current limits
Site-visit scheduling and evidence only. No travel optimization, variations, retention/progress billing, native reception checkout or automatic parent completion. This operational desk has no new payment engine.
When a step is blocked
- Missing desk: check foundation blocks, selected workflow and staff access.
- Source not ready: complete its original kitchen, sales or job action and refresh.
- Approval needed: use an eligible owner or manager.
- Record changed: refresh and review history before retrying.
- No connection: these browser desks require the ERP server. An unsaved form is not a completed transaction.