Wrong Branch Gets the Online Order: Routing Rules

Calendar icon
November 16, 2026
November 17, 2026

Multi location online ordering assigns web orders to a closed or unsuitable branch when storefronts rely on stale branch selectors, overlapping distance circles, or un-synced POS stock statuses. To fix this, test branch zones, stock availability and trading hours before payment authorization, enforce street-aligned polygons, and route tickets via an OMS with real-time branch health into POS.

Designed for restaurant owners, multi-branch operations leads, and IT managers across Riyadh, Jeddah, and Dammam, this routing QA manual keeps owned web tickets isolated from consumer food-delivery apps.

The problem — web orders assigned to a closed or unsuitable branch

Multi-branch polygon & live kitchen status verification — Riyadh Operations

Consumer food-delivery apps run proprietary marketplace dispatch algorithms tied directly to rider telemetry and tablet acknowledgments. When chains expand Direct Web Ordering for multi-branch restaurants on standalone storefront software, however, weak routing rules frequently assign carts to whichever store the user browsed first, to an adjacent store separated by a major Riyadh highway, or to a branch whose kitchen already closed for the night.

Fixing branch misassignment requires clear separation across the two operational layers behind checkout:

  • Point of Sale (POS): Executes local sales accounting, generates ZATCA Phase 2 e-invoices, prints Kitchen Display System (KDS) tickets, and toggles branch item 86 stockouts—it executes only whatever tickets reach that specific branch endpoint.
  • Order Management System (OMS): Sits upstream across all Saudi restaurant branches to evaluate pin-to-polygon ownership, real-time trading hours and pre-close cutoffs, POS 86 stock availability, and API event status codes before accepting buyer tenders.

How to diagnose the failure and capture evidence

Before redrawing maps or altering shift schedules, audit the past 14 days of misrouted direct web tickets using four operational evidence sources:

  • Cancelled After-Hours & Shift-Gap Tickets: Pull branch void reports for web orders accepted right before closing time, during mid-day prayer pauses, or on temporary maintenance closures.
  • Cross-Corridor 3PL Delivery Outliers: Sort courier bookings by driving distance to detect overlapping distance radii sending orders across highways instead of assigning the nearest reachable store.
  • Stale 86 Item Voids in Branch POS: Check branch POS refunds caused by unavailable menu items that were marked 86 on dine-in kiosks hours earlier yet remained active on web menus.
  • Unacknowledged Webhook Queues: Inspect OMS API event status logs for tickets queued while a branch POS terminal lost internet connectivity and missed pre-checkout health suppression.

To review storefront setup fundamentals alongside unit contribution math, consult our existing restaurant online ordering guide and the Direct Online Ordering vs Delivery Apps cost guide.

Step-by-step solution — test branch zones, stock availability and trading hours

Apply this five-step routing discipline across your multi location online ordering Saudi Arabia stack so every cart resolves cleanly before card authorization:

  • Eliminate Overlapping Distance Circles with Street-Aligned Polygons: Map non-overlapping polygons bounded by real highways, bridges, and industrial zones in Riyadh, Jeddah, and Dammam so one pin always resolves to one priority kitchen.
  • Enforce Real-Time Trading Hours & Pre-Close Cutoff Buffers: Sync branch schedules with KSA time (UTC+3) and apply a 15-to-30-minute last-order cutoff ahead of closing or prayer breaks so late orders shift to scheduled pickup or an open 24h branch.
  • Re-Validate Pin-to-Branch Selection When Saved Addresses Load: Do not trust cached browser branch cookies from deep links or prior sessions; trigger dynamic branch assignment immediately when the guest picks or edits a delivery pin.
  • Bind Cart Menu Items to Live Per-Branch 86 Stock Sync: Require sub-minute inventory webhook sync between branch POS and storefront OMS so out-of-stock dishes cannot pass into checkout.
  • Deploy Health-Aware Multi-Branch Routing via Managed OMS: Route storefront sessions through a unified Direct Web Ordering service that verifies POS heartbeat health, branch availability, and polygon ownership prior to payment.

Multi-Branch Routing Method

Geographic Accuracy

Hours & Stock Awareness

Operational Risk

Manual Guest Branch Dropdown

Guests routinely click nearest familiar name regardless of zone

Often displays static hours disconnected from branch pauses

High misrouted ticket & manual refund rate

Static Circular Radius Routing

Overlapping circles cross highways and U-turns

Slow manual 86 stock updates per location

Delayed 3PL handoffs & cold food handovers

Dynamic OMS Polygon + Live POS Health

Pin resolves deterministically to accessible branch polygon

Real-time cutoff buffers, 86 stock, and POS heartbeat

Zero misassigned orders entering closed kitchens

wrong-branch routing QA cases

Run these five QA test cases across staging before launching multi-branch direct web ordering:

QA Case

Failure Condition to Reproduce

Required OMS Routing Rule

API Event Status

Workflow Owner

QA-01: Overlapping Radius vs Street Polygon

Pin sits 2.5 km straight-line from Branch A across a major highway barrier

OMS evaluates street-aligned polygons (not radius) and routes to accessible Branch B

branch_match_source: "POLYGON" (200)

Operations Lead / OMS Vendor

QA-02: Prayer Pause or Cutoff Buffer

Buyer checks out 10 minutes before closing or during an active branch pause window

OMS enforces closing buffer, switches to scheduled slot or adjacent open kitchen

BRANCH_CUTOFF_BUFFER_TRIGGERED (422)

Branch Supervisor / IT Lead

QA-03: Branch Item Stockout (86 Sync)

Branch A marks a combo 86 on POS while bordering Branch B retains active inventory

Catalog updates per branch quickly; cart warns or blocks Branch A pre-payment

SKU_OUT_OF_STOCK_AT_BRANCH (409)

POS Integrator / Kitchen Lead

QA-04: POS Heartbeat Offline

Storefront authorizes Apple Pay while target branch POS webhook endpoint fails

OMS detects stale heartbeat and blocks instant delivery for the offline branch

POS_HEARTBEAT_UNREACHABLE (503)

IT Manager / OMS Support

QA-05: Deep-Link / Saved Address Override

Guest loads an Al Khobar URL and picks a saved Riyadh work pin at checkout

OMS re-evaluates pin against target polygon dynamically rather than keeping stale branch ID

REVALIDATED_BRANCH_ID (200)

Storefront Product / QA Lead

Saudi restaurant operations scenario

HYPOTHETICAL ILLUSTRATIVE SCENARIO (Not Documented Case Study Data):

Suppose a hypothetical 9-branch fried chicken group runs Riyadh, Jeddah, and Dammam stores with differing late-night closing times and overlapping 6 km delivery circles. Late at night, paid web orders routinely land on kitchens closing within 10 minutes or on stores across a congested ring road while an open 24-hour branch sits nearby.

Operations teams carve clean, non-overlapping polygons aligned to road arteries, apply 20-minute pre-close cutoff buffers, wire live POS 86 stock sync, and route checkouts through an OMS designed for LYNNC restaurant operations. Late orders either reroute cleanly to the open 24-hour kitchen within coverage or block instant delivery before tender capture.

What to validate in a vendor demo

During an integration vendor demo wrong-branch routing QA cases session, test edge-case state transitions live on staging:

  • Emergency Store Pause Speed: Ask the operator to click "Pause Online Orders" for one Riyadh store and verify the web cart blocks new orders for that zone within seconds.
  • Cross-Branch Saved Address Switching: Select a previously saved Jeddah address while viewing a Riyadh deep link and confirm OMS updates pricing, inventory, and branch ID dynamically.
  • Branch-Specific 86 Menu Sync: Mark one modifier or combo out of stock at a single POS branch and verify adjacent stores stay active and purchasable.
  • Real-Time API Event Status & Failover Logs: Inspect OMS telemetry showing polygon match decisions, cutoff blocks, and POS heartbeat health checks.
  • Factual Multi-Location Branch Pages: Publish verifiable store addresses, hours, and service zones aligned with Google's AI optimization guidance, focusing on factual clarity rather than guaranteed search indexing or sales claims.

KPIs and implementation acceptance tests

Enforce explicit KPI, SLA, and workflow ownership across branch leadership and IT prior to enabling multi-location web ordering:

QA Gate & Acceptance Test

Workflow Owner

Target SLA

Staging Verification Test

Exclusive Non-Overlapping Street Polygons

Operations Lead / OMS Vendor

0 ambiguous overlaps

Confirm bordering Riyadh, Jeddah, and Dammam branches resolve each pin deterministically

Trading Hours & Pre-Close Cutoff Buffer

Branch Manager / Ops Lead

Cutoff enforced pre-pay

Attempt checkout within 15 minutes of close or prayer pause and verify clean block/reschedule

Branch POS 86 Stockout Propagation

Kitchen Lead / POS Integrator

< 30s item sync

Mark item 86 in Branch A POS and verify storefront availability updates immediately

POS Heartbeat & Failover Suppression

IT Manager / OMS Support

< 60s offline detection

Pause staging branch POS connector and confirm OMS halts delivery tenders for that unit

Frequently Asked Questions

Why do restaurants face web orders assigned to a closed or unsuitable branch?

Multi-location storefronts route tickets incorrectly when guest sessions lock onto an outdated manual branch choice or evaluate straight-line distance circles rather than live street polygons. Without continuous synchronization between POS stock flags, local Saudi trading hours, and branch connector health, websites accept orders that a closed or stocked-out kitchen cannot fulfill.

How can an operator test branch zones, stock availability and trading hours?

Reproduce five controlled staging tests: place boundary orders across highway-split polygons, check out inside a 15-minute pre-close buffer, mark an item unavailable in one branch POS only, disconnect a branch POS heartbeat, and load deep-linked URLs alongside saved addresses from another city. Every failure case must intercept payment prior to authorization.

What should a Saudi restaurant verify during a software demo?

Ask engineers to pause a single branch kitchen live on staging and demonstrate what an active cart buyer sees seconds later on mobile Safari. Inspect how the Order Management System (OMS) validates hours, 86 item stock, and polygon borders before injecting settled tickets into the correct branch Point of Sale (POS) while logging transparent API event status traces.

Which operational metric proves this issue is fixed?

Tracking Wrong-Branch Order Rate, Post-Pay Branch Reassignment Count, and Cancelled-Due-to-Closed-Kitchen Tickets down toward zero across branch POS logs proves routing accuracy. Confirm simultaneous drops in manual dispatcher reroutes and 3PL cross-district delivery distances.

Decision Summary: Send Orders to the Right Branch

Preventing wrong-branch fulfillment eliminates emergency refunds and cold food deliveries. Combine exclusive street polygons, pre-close trading buffers, branch-level 86 stock sync, and POS heartbeat monitoring inside your OMS before accepting payment.

Discuss Multi-Branch Routing with LYNNC

LYNNC Restaurant Solutions

Make your restaurant operations simpler

Explore LYNNC solutions for orders, digital menus and integrations. Choose what fits your operation, or ask us for a tailored demonstration.

Restaurant Order ManagementBring orders from different channels into one clearer workflow.Explore solution →Digital MenusKeep menu items, availability and pricing easier to update.Explore solution →System IntegrationsConnect LYNNC to supported POS systems and delivery channels.Explore solution →
Want to see which solution works for you?Request a demo →
Quotation mark icon
LYNNC is your trusted partner in optimizing restaurant operations, improving efficiency, and delivering outstanding customer experiences. Let us help you achieve your business goals.