Orbit Commerce Inter-Store Stock Transfers & In-Transit Custody Tracking

1. Enterprise Governance Hierarchy & Organizational Logistics Scoping

Multi-unit retail enterprises operating across metropolitan areas, shopping malls, and regional fulfillment hubs depend on continuous inventory rebalancing. When satellite retail branches deplete fast-moving stock keeping units while suburban central warehouses hold surplus pallets, inefficient transfer workflows create devastating commercial bottlenecks:

1. Phantom Stock Double-Counting: If transferred stock is deducted from the source warehouse but not tracked in transit, operations teams either double-count floating units or report false stock-outs.
2. Untracked Carrier Shrinkage: When boxes disappear off delivery trucks, uncoupled systems trigger finger-pointing between warehouse loaders, 3rd-party logistics drivers, and store receiving clerks.
3. Unilateral Unauthorized Transfers: Store managers moving merchandise between sibling stores without head office approval distort regional P&L attribution and tax jurisdiction reporting.
4. Unrecorded Receipt Discrepancies: Receiving clerks quietly adjusting counts without mandatory discrepancy reason codes mask recurring supplier packaging faults or driver pilferage.

Orbit Commerce enforces a deterministic four-tier organizational hierarchy. Transfer authorizations follow strict top-down governance rules, ensuring complete chain-of-custody tracking from requisition creation through dispatch, road transit, and final dock acceptance.

2. Role-Based Access Control (RBAC) & Entitlement Matrix

Transfer actions are gated by explicit role capabilities. The system blocks unauthorized privilege escalation across all inventory transfer endpoints:

Codebase Anchors & Grounded Architecture

The inter-branch requisition and transfer infrastructure is implemented across the modular backend application server and dynamic client view engine:

• Client Stock Transfer & Receiving View: Central transfer and goods receipt console (receiving-view.tsx at apps/commerce/src/components/pos/receiving-view.tsx), handling carton scanning, variance logging, and transit manifest confirmations.
• Backend Requisition Logistics Service: Inter-store movement and custody pipeline (requisitions.service.ts at apps/api/src/modules/commerce/services/requisitions.service.ts), executing create, approve, dispatch, receive, and completeTransfer.
• Relational Persistence Schema: The stock_requisitions table, stock_requisition_items, and immutable ledger rows in stock_movements, enforced with strict multi-branch tenant isolation rules in the relational persistence kernel.

3. Stock Transfer Console User Interface

The Stock Transfer Console provides central logistics teams with real-time visibility into active inter-branch transfers, vehicle tracking, carrier bills of lading, and dock verification tallies.

4. Requisition Lifecycle & Movement Ledger State Machine

Inter-branch stock requisitions advance through five deterministic states. Inventory ledger movements are created during the dispatch and receiving stages, guaranteeing that floating stock is never unaccounted for.

Phase 1: Requisition Creation & Line Validation

1. Trigger Condition: Store supervisor identifies low-stock warning on critical inventory items.
2. Operator Action: Navigate to Inter-Store Transfers; select destination store and source warehouse; add items and requested quantities; submit requisition.
3. Terminal System Response: Validates that source and destination location identifiers differ; pre-verifies all item records exist and are marked active; generates StockRequisition record in REQUESTED status; emits audit log COMMERCE_REQUISITION_CREATED.
4. Verification State: Requisition appears in central supply chain dispatch queue.

Phase 2: Central Approval & Allocation

1. Trigger Condition: Supply chain controller inspects pending store requests.
2. Operator Action: Review requested quantities against warehouse availability; adjust allocations if warehouse is constrained; click Approve Requisition.
3. Terminal System Response: Verifies requisition status is REQUESTED; transitions status to APPROVED; locks line allocations; emits audit log COMMERCE_REQUISITION_APPROVED.
4. Verification State: Warehouse picking team receives authorized picking ticket.

Phase 3: Physical Dispatch & Stock Movement Ledger Deduction

1. Trigger Condition: Warehouse pickers stage packed boxes on the outbound shipping dock.
2. Operator Action: Enter carrier identifier (e.g., driver name, license plate, bill of lading number); confirm dispatched counts; click Dispatch Freight.
3. Terminal System Response:
   • Executes atomic balance validation: checks that source warehouse balance $\ge$ dispatch quantity for every line. If short, throws immediate exception.
   • Creates negative inventory movement in stock_movements with reason COMMERCE_TRANSFER_DISPATCH.
   • Stamps dispatchedQty and dispatchedAt timestamps on requisition lines.
   • Transitions requisition status to DISPATCHED; emits audit log COMMERCE_REQUISITION_DISPATCHED.
4. Verification State: Outbound manifest prints with carrier signature line; warehouse stock ledger is immediately relieved.

Phase 4: Receiving Dock Inspection & Variance Reconciliation

1. Trigger Condition: Delivery van arrives at receiving store; driver presents freight cartons.
2. Operator Action: Scan each carton barcode; enter received quantities; if any count deviates from dispatched total, select mandatory discrepancy reason (TRANSIT_DAMAGE, SHORT_DELIVERY, WRONG_ITEM_SHIPPED); confirm receipt.
3. Terminal System Response:
   • Validates all submitted line items belong to the active requisition.
   • Creates positive inventory movement in stock_movements with reason COMMERCE_TRANSFER_RECEIVE for actual received units.
   • Calculates line variance: Variance = Received Quantity - Dispatched Quantity.
   • Stays within transaction: updates requisition status to COMPLETED; stores variance details in stock_requisition_items; emits audit log COMMERCE_REQUISITION_RECEIVED.
4. Verification State: Shelf stock is instantly available for point-of-sale checkout at receiving store.

5. In-Transit Custody & Mandatory Discrepancy Reason Taxonomy

When physical inventory moves over public roads, damage or loss must be classified immediately to prevent financial write-off ambiguity.

Mandatory Discrepancy Reason Taxonomy

Orbit Commerce enforces an auditable classification taxonomy:

1. TRANSIT_DAMAGE: Goods physically crushed, punctured, or spoiled during vehicular transit. Requires carrier co-signature and photographs attached to inspection note.
2. CARRIER_SHORTAGE: Box or unit count is missing upon delivery seal opening. Triggers formal freight carrier shortage claim.
3. PACKING_ERROR_DEFICIT: Warehouse shipping box was unsealed but contained fewer units than stamped on packing manifest. Debited to Central Warehouse Picking Shift.
4. OVER_SHIPMENT: Driver delivered excess cartons not listed on requisition. Units staged in quarantine for head office re-assignment.
5. WRONG_SKU_DELIVERED: Carton contained a different product variant than ordered. Treated as zero intake for ordered SKU plus un-manifested quarantine intake.

Discrepancy Calculation & Ledger Impact

Consider SKU-OIL-2041 (Virgin Coconut Oil 500ml):

• Dispatched from Central Warehouse: 80 units
• Physically received at Store #04: 76 units
• Variance: -4 units
• Recorded Reason: TRANSIT_DAMAGE

Source Warehouse Stock Movement:
- Date: 2026-10-08 14:15
- Action: COMMERCE_TRANSFER_DISPATCH
- Location: WH-Central
- Quantity: -80 units

Destination Store Stock Movement:
- Date: 2026-10-08 16:30
- Action: COMMERCE_TRANSFER_RECEIVE
- Location: Mall-Branch-04
- Quantity: +76 units

Requisition Item Audit Record:
- Item: SKU-OIL-2041
- Dispatched: 80
- Received: 76
- Variance: -4
- Reason: TRANSIT_DAMAGE
- Dispute Account: 5020 Inventory Shrinkage (Sub-ledger: Carrier Swift Freight)

The 4 lost bottles are not phantom inventory. They are permanently recorded in the variance register, allowing corporate finance to deduct the cost from the logistics carrier monthly settlement.

Commercial Settlement & Carrier Dispute Sub-Ledger Integration

When variance is recorded under TRANSIT_DAMAGE or CARRIER_SHORTAGE, the accounting kernel segregates the disputed valuation from standard store shrinkage:

1. Shortage Segregation: Rather than burdening the receiving store's local profit and loss statement with transit losses, the system routes the loss to a dedicated balance sheet clearing account: Carrier Claims Receivable (Account 1190).
2. Monthly Carrier Reconciliation: At month-end, the corporate supply chain auditor generates the consolidated Carrier Discrepancy Statement. This document aggregates all transfer lines with negative variances, listing dispatch timestamps, driver sign-off tokens, bill of lading references, and pre-calculated wholesale cost totals.
3. Automated Freight Invoice Offsetting: When the logistics carrier submits their monthly freight invoice for inter-branch hauling services, the accounts payable team applies an automatic debit memo against the freight bill, recovering 100% of the lost merchandise valuation before issuing wire disbursement.

Predictive Stock Rebalancing & Buffer Replenishment

Inter-branch transfers are orchestrated not only by manual store requests but also through automated replenishment calculations:

• Velocity Rebalancing: The central inventory engine monitors stock consumption velocities across all retail branches. If Branch A has a 45-day supply of an item while Branch B has a 4-day supply, the system drafts an automated rebalancing requisition.
• Minimum Safety Thresholds: Each product variant maintains location-specific minimum safety stock levels and reorder points. When shelf counts cross below the safety buffer, the platform alerts regional logistics coordinators with suggested transfer manifests, preventing localized stock-outs while avoiding redundant central supplier purchases.

6. Immutable Audit Trail & Chain-of-Custody Logging

Every inter-branch requisition lifecycle event is immutably recorded in the central audit registry with microsecond precision, actor identification, and payload delta capture.

Event Specification

Audit ID: AUD-REQ-2026-00842-DISPATCH
Timestamp: 2026-10-08T14:15:32.418Z
Actor ID: usr-wh-lead-042 (Farhan Qureshi)
Action: COMMERCE_REQUISITION_DISPATCHED
Entity: StockRequisition
Entity ID: req-2026-00842
Before State: { status: "APPROVED", dispatchedAt: null }
After State: {
  requisitionNumber: "RQ-2026-00842",
  status: "DISPATCHED",
  carrierReference: "Swift Freight Van #402 (Lic: KHI-8921)",
  dispatchedLinesCount: 5,
  totalUnitsDispatched: 450
}

This immutable log cannot be altered or truncated, providing non-repudiable forensic evidence for internal loss-prevention audits and statutory insurance claims.

7. Deviation Handling & Exception Protocols

Logistics teams must follow standardized remediation protocols when transfer operations encounter anomalies:

8. High-Frequency Triage & Operational FAQs

What happens if an entire truckload is lost or stolen in transit?

The regional supply chain controller marks the requisition as LOST_IN_TRANSIT, writing down the inventory to the carrier insurance clearing sub-ledger. The destination branch receives zero units, ensuring its inventory records remain accurate. A corporate loss investigation voucher is created, debiting Carrier Insurance Claims Receivable (Account 1190) and crediting In-Transit Inventory (Account 1250).

Can an approved requisition be cancelled after the picking process has started?

Yes, an approved requisition can be cancelled provided it has not yet advanced to the DISPATCHED status. When a requisition is cancelled in the APPROVED state, no stock movements have occurred in the inventory ledger. The warehouse pickers return the picked items to primary pallet racking, and the requisition is archived with status CANCELLED. Once dispatched, however, the shipment cannot be cancelled; it must be received and processed through a reverse return transfer.

Does transferring stock between branches trigger sales tax or VAT liabilities?

Inter-branch transfers within the same registered legal entity are non-taxable internal inventory movements. Because ownership of the goods remains with the corporate parent, no commercial sale occurs, and no output tax is calculated. However, transfer documents maintain cost valuations to comply with inter-state transport checkpoint regulations and excise transport permits.

9. Related Operations & Lateral Internal Links

Maintain end-to-end operational mastery across inventory auditing, logistics, and store operations:

• Master warehouse auditing workflows: Physical Stock Take Broadsheet & FEFO Reconciliation.
• Explore dock vendor receiving: Vendor Purchase Orders & Docked Goods Receiving Inspections.
• Examine double-entry general ledger posting: Enterprise Double-Entry General Ledger & Real-Time Financial Statements.
• Review omnichannel inventory synchronization: Headless Omnichannel E-Commerce & Atomic Inventory Depletion.
• Hospitality terminal operations: Orbit Dine POS Terminal Operations.