Orbit Dine Table Transfers, Ticket Merges & Check Split Operations Runbook

1. Operational Mission & Pre-Flight Verification Gate

During peak dining service in busy restaurants and hotels, guest seating is inherently dynamic. Parties frequently request to move from indoor tables to outdoor patios, adjacent tables combine to accommodate arriving family members, or corporate parties demand divided checks split precisely by seat numbers.

When point-of-sale systems handle table moves and merges through manual order re-entry or uncoordinated ticket voiding, severe operational failures result:

1. Kitchen Ticket Duplication: Staff re-enter dishes on the new table, causing kitchen cooks on multi-station kds routing lines to prepare double orders of entrees.
2. Food Delivery Misdirection: Food runners deliver dishes to the original table location, disturbing newly seated guests while the relocated party waits indefinitely.
3. Financial Discrepancies: Draft bills fail to recalculate taxes, discounts, or service surcharges accurately when combining multi-table tabs.
4. Audit Trail Blind Spots: Dishonest cashiers exploit unmonitored ticket merges to conceal cash payments or apply unauthorized bill cancellations.

Orbit Dine resolves these operational risks through atomic, transactional table mutations:

• Atomic Table Move (POST /tables/transfer): Relocates open items, active kitchen prep lines, captain notes, and running bill totals to an unoccupied target table in a single database transaction.
• Universal KDS & Runner Broadcast: Instantaneous sub-millisecond event dispatch updates all kitchen display units and runner tablets, rerouting dishes to the new table number.
• Master Ticket Consolidation (POST /tables/merge): Combines multiple occupied tables into a unified master check, releasing source furniture back into the Available pool.
• Granular Seat-Level Check Splitting: Enables partial settlement by individual seat numbers or equal split fractions at cashier counter billing.
• Supervisor PIN Security Firewall: Cryptographic signoff prevents cashier theft, cash discrepancies, and unapproved bill modifications.

Pre-Flight Verification Checklist

Before initiating any table transfer, merge, or check split, the floor captain must verify the following baseline prerequisites:

2. Environmental Pre-Conditions & Table Readiness Matrix

The table below outlines operational pre-conditions governing table move and merge actions:

3. Atomic Transaction Pipeline: Transfer & Merge Architecture

The responsive inline diagram below details the database transaction pipeline and event dispatch synchronization that occur during table transfer and merge operations:

4. Software UI Frame: Table Operations Console

The table operations modal interface enables floor supervisors to execute moves and merges with complete visibility into source check details and target table availability:

5. Empirical Telemetry & Boundary Performance Limits

The table transfer and merge engine executes with sub-50ms database commit guarantees and instantaneous event bus synchronization:

6. Granular Procedural Workflows: Transfer, Merge, and Split

Workflow 1: Table Move / Transfer SOP

1. Trigger: Guest requests relocation to a different table (e.g. Moving from Table T-06 to Table T-14).
2. Identification: Floor captain locates Table T-06 on the live floor map, verifying the active order badge (Order #1042).
3. Modal Launch: Captain taps Move on the table card, opening the transfer dialog.
4. Target Selection: The system queries unoccupied active tables (!t.isOccupied && t.isActive). Captain selects Table T-14 from the dropdown.
5. Supervisor Signoff: Captain enters authorized 4-digit PIN.
6. Execution: System dispatches POST /tables/transfer with:

   {
     "sourceTableId": "tbl_06_mainhall",
     "targetTableId": "tbl_14_mainhall"
   }
   

7. Confirmation: Table T-06 reverts to Available (emerald beacon). Table T-14 illuminates with the amber pulsing beacon, carrying Order #1042 and running total Rs. 4,850.00. Kitchen display screens update instantly.

Workflow 2: Multi-Table Merge SOP

1. Trigger: Two adjacent dining groups unite into a single party (e.g., Table T-08 combining with Table T-09).
2. Identification: Captain verifies both tables have active occupied orders.
3. Modal Launch: Captain taps Merge on Table T-08.
4. Target Master Selection: Captain selects Table T-09 as the target master table.
5. Supervisor Authorization: Floor supervisor authorizes the merge.
6. Execution: System dispatches POST /tables/merge with:

   {
     "sourceTableId": "tbl_08_mainhall",
     "targetTableId": "tbl_09_mainhall"
   }
   

7. System Resolution: Line items from Table T-08 transfer to Table T-09's ticket. Table T-08 order closes with status MERGED. Table T-08 reverts to Available. The combined ticket displays on Table T-09 with consolidated running balance.

Workflow 3: Seat-Level Split Check SOP

1. Trigger: Guests at a 4-top table request individual checks divided by seat numbers.
2. Access: Cashier or captain opens the active order on cashier counter billing.
3. Seat Assignment: Operator assigns each line item to its corresponding seat index:
   • Seat 1: 1x Chicken Karahi (Rs. 1,850.00) + 2x Naan (Rs. 120.00)
   • Seat 2: 1x Mutton Handi (Rs. 2,400.00) + 1x Fresh Lime (Rs. 180.00)
   • Seat 3 & 4: 2x Zinger Burgers (Rs. 1,400.00) + 2x Mint Margaritas (Rs. 500.00)
4. Child Check Generation: System generates 3 distinct sub-checks, apportioning subtotal, taxes, and service charges accurately.
5. Independent Settlement: Each sub-check tenders independently via Cash, Digital QR, or Credit Card, closing the master table once all child checks reach financial clearance.

7. Supervisor Authorization & Fraud Prevention Guardrails

Table transfers and merges represent high-risk operational moments vulnerable to cashier fraud. Orbit Dine implements strict anti-leakage guardrails:

Anti-Fraud Controls Matrix

• Closed Ticket Transfer Prohibition: Completed or paid orders cannot be transferred. Once settled, tickets lock permanently against floor movements.
• Void Prevention via Merge: System prohibits merging a table with unpaid food items into an already-paid ticket, preventing staff from disguising uncollected cash tabs.
• Audit Ledger Logging: Every transfer and merge writes an immutable record to the audit ledger:
  • Timestamp of operation (T-00:00 ISO format).
  • Source and destination table numbers.
  • Authorizing Supervisor ID and Terminal ID.
  • Snapshot of transferred line items and currency values.

8. Failure Modes & Operational Resilience

The table below outlines common operational failures during table transfers and merges, their root causes, and standard recovery procedures:

9. Advanced Production Tuning & Check Partitioning Directives

Maximum Child Split Ceilings

To prevent checkout gridlock during peak dinner rushes:

• Maximum Split Partitions: A single dining check may be divided into a maximum of 12 child checks. Larger banquet splits require supervisor override.
• Minimum Transaction Limit: Split checks cannot create child tickets below Rs. 100.00 currency units, preventing excessive micro-card transaction merchant fees.

10. Operational Inquiries & High-Intent Technical FAQs

Can items be transferred individually between tables rather than moving the whole check?

Yes. In addition to full table moves, the system supports Line Item Transfer. Supervisors select specific dishes on the check (e.g., "Transfer 1x Mint Margarita from Table 04 to Table 08"), moving only selected lines while leaving the remainder of the order active on the original table.

Does transferring a table change the assigned waiter captain?

By default, the order retains its original waiter captain to ensure tip tracking and service accountability. However, if the table moves into a different physical dining hall with dedicated captain zoning, the supervisor can elect to re-assign the order to the local section captain.

How does the customer-facing display reflect table transfers?

When a customer-facing display is paired with a specific table (e.g. tablet standee), executing a transfer immediately refreshes the display to reflect the updated table token and welcome message, preventing guest confusion.

What happens if a table transfer is attempted while a course is being fired?

The system permits the transfer; the course fire event carries the updated table destination directly to kitchen display screens, ensuring that kitchen cooks plate and tray the order for the new table location.

11. Structured Schema Metadata

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "TechArticle",
      "headline": "Orbit Dine Table Transfers, Ticket Merges & Check Split Operations Runbook",
      "description": "A comprehensive operational runbook detailing table transfer protocols, multi-ticket merge pipelines, seat-level check splitting SOPs, and supervisor authorization guardrails.",
      "proficiencyLevel": "Advanced",
      "articleSection": "Floor Management & Table Operations",
      "inLanguage": "en-US",
      "publisher": {
        "@type": "Organization",
        "name": "FrontOrbit Core Engineering",
        "url": "https://frontorbit.com"
      }
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://frontorbit.com"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Documentation",
          "item": "https://frontorbit.com/docs"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Orbit Dine",
          "item": "https://frontorbit.com/docs/dine"
        },
        {
          "@type": "ListItem",
          "position": 4,
          "name": "Table Transfers, Merges & Splits",
          "item": "https://frontorbit.com/docs/dine/table-transfers-merges-and-splits"
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What system pre-conditions must be satisfied before executing a table transfer?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The source table must have an active order with non-zero lines, and the destination table must be active (t.isActive) and unoccupied (!t.isOccupied)."
          }
        },
        {
          "@type": "Question",
          "name": "How does Orbit Dine synchronize kitchen display rails when a table is transferred mid-service?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The endpoint POST /tables/transfer updates the order table reference in an atomic database transaction and broadcasts an update over the sub-millisecond event bus to all KDS screens without resetting cooking timers."
          }
        },
        {
          "@type": "Question",
          "name": "What occurs to open items, service charges, and taxes during a table merge?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "All items transfer onto the target master check, the source order closes as merged, the source table becomes Available, and taxes, service charges, and discounts recalculate dynamically."
          }
        },
        {
          "@type": "Question",
          "name": "Why are table transfers and merges protected by Supervisor PIN authorization?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Supervisor PINs prevent unauthorized discounts, cashier theft, and inventory leakage, recording an immutable cryptographic audit trail of all table modifications."
          }
        }
      ]
    }
  ]
}