Orbit Commerce Vendor Purchase Orders & Docked Goods Receiving Inspections

1. Operational Mission & Pre-Flight Verification Gate

Commercial retail and wholesale distribution operations depend upon absolute physical and financial integrity at the goods intake dock. When dock receiving relies upon manual paper tallies, unchecked delivery notes, or delayed data entry, businesses suffer catastrophic inventory leakage:

1. Undetected Short Shipments: Suppliers deliver fewer cases than billed, leaving retailers paying for phantom inventory that never entered the storage zone.
2. Distorted Inventory Valuation: Accepting stock at updated prices without atomic moving average adjustments corrupts Gross Margin reporting and Gross Margin Return on Investment analytics.
3. Unrecorded In-Transit Liabilities: Delayed entry of delivery notes creates multi-day blind spots where physical stock is sold at cash registers before the corresponding Accounts Payable liability is recognized in the general ledger.
4. Damaged Lot Contamination: Broken, expired, or compromised goods enter forward pick locations without batch segregation, resulting in customer returns and damaged retail reputation.

The Orbit Commerce Docked Receiving Inspector eliminates these failure modes by providing an interactive master-detail intake console. Every delivery is checked against authorized purchase orders line by line, validating item barcodes, ordered quantities, unit cost agreements, and batch expiry dates before physical stock moves to retail shelves.

Pre-Flight Verification Gate

Before unlatching freight delivery bays or breaking pallet security seals, the receiving lead must complete this verification gate:

2. Environmental Pre-Conditions & Station Readiness Matrix

The receiving dock terminal operates as a high-density inspection portal. Ensure the operational environment satisfies these baseline parameters prior to processing freight:

Codebase Anchors & Grounded Architecture

The procurement and docked receiving engine is implemented across the modular backend application server and dynamic client view engine:

• Client Receiving View Engine: Docked receiving inspector and purchase order lifecycle console (purchase-orders-view.tsx at apps/commerce/src/components/pos/purchase-orders-view.tsx), handling optical wedge barcode ingress, DataGrid item reconciliation, and Goods Receipt triggers.
• Backend Procurement Service: Purchase orders and intake pipeline (purchase-orders.service.ts at apps/api/src/modules/commerce/services/purchase-orders.service.ts), providing createPurchaseOrder, issuePurchaseOrder, cancelPurchaseOrder, and receiveGoods.
• Relational Persistence Schema: Master order header, line manifests, and intake receipts (purchase_orders, purchase_order_items, and goods_receipts tables) enforced with row-level tenant isolation boundaries in the relational persistence kernel.

3. Docked Receiving Inspector User Interface

The Docked Receiving Inspector provides real-time visibility into the complete delivery manifest, displaying ordered quantities, received quantities, variance deltas, unit costs, and lot numbers.

4. End-to-End Docked Receiving Procedural Workflow

Receiving operations follow a strict chronological sequence governed by deterministic state gates. Frontline operators must execute each step in order without skipping physical or digital verifications.

Phase 1: Intake & PO Attachment

1. Trigger Condition: Freight truck docks at bay; driver hands physical delivery paperwork to intake clerk.
2. Operator Action: Enter purchase order reference into search box (e.g., PO-2026-00481) or scan barcode on supplier delivery paperwork.
3. Terminal System Response: Inspector retrieves target order; verifies order status is ISSUED; verifies tenant boundary; preloads item manifest into virtual DataGrid.
4. Verification State: Header displays green active order banner with supplier name, delivery destination, and expected line count.

Phase 2: Dock Physical Verification & Wedge Ingress

1. Trigger Condition: Pallets are unladen from truck; boxes staged for inspection.
2. Operator Action: Scan each outer carton EAN-13 or GS1-128 shipping barcode using hand scanner.
3. Terminal System Response: Within 2.4ms, scanner wedge matches item identifier; increments received count; triggers green highlight flash on active row; scrolls row into view; updates remaining required tally.
4. Verification State: Scanned count tallies match physical box count on dock floor.

Phase 3: Variance Logging & Dispute Generation

1. Trigger Condition: Delivered quantity is short, items arrive damaged, or supplier invoice rate deviates from purchase order agreed cost.
2. Operator Action: Select variance reason from dropdown (SHORT_DELIVERY, DAMAGED_IN_TRANSIT, SUPPLIER_PRICE_SURCHARGE); enter physical delivered count.
3. Terminal System Response: System calculates dollar delta; prepares vendor credit claim memo; flags line for manager sign-off.
4. Verification State: Variance summary card displays explicit line debit amounts and tags order for AP reconciliation.

Phase 4: Atomic Valuation Recalculation & General Ledger Posting

1. Trigger Condition: All physical lines verified; receiving supervisor clicks Post Goods Receipt.
2. Operator Action: Confirm receipt dialog; enter supplier delivery note number; press Enter.
3. Terminal System Response: Database transaction updates inventory counts; recalculates Weighted Average Cost; creates stock movement ledger entries with reason PURCHASE_RECEIPT; posts operational general ledger entry COMMERCE_GOODS_RECEIPT_POSTED.
4. Verification State: Success confirmation dialog displays Goods Receipt Number (e.g., GRN-2026-00319) and General Ledger Journal Reference.

5. Mathematical Weighted Average Cost (WAC) Formulation

Accurate inventory accounting requires continuous recalculation of inventory asset valuation whenever new inventory is acquired at differing unit purchase prices. Orbit Commerce implements the continuous Perpetual Weighted Average Cost model.

Mathematical Formulation

When receiving new stock units at a specified purchase cost while holding existing warehouse units evaluated at current moving average cost, the updated Weighted Average Cost is derived as:

New WAC = ((Existing Units * Existing Cost) + (Received Units * Invoice Cost)) / (Existing Units + Received Units)

Concrete Operational Valuation Example

Consider retail stock keeping unit SKU-OIL-1001 (Organic Olive Oil 1L):

• Existing stock balance on floor: 200 units
• Existing recorded unit cost: $16.00
• Total existing inventory valuation: $3,200.00
• Incoming received quantity: 100 units
• Incoming supplier invoice cost: $18.50
• Value of incoming shipment: $1,850.00

Recalculating moving average unit cost upon accepting delivery:

New WAC = ((200 * $16.00) + (100 * $18.50)) / (200 + 100)
        = ($3,200.00 + $1,850.00) / 300
        = $5,050.00 / 300
        = $16.8333

The database engine rounds unit costs to four decimal places ($16.8333), while updating total stock balance to 300 units and total inventory asset balance to $5,050.00. Subsequent retail sales instantly deduct Cost of Goods Sold at $16.8333 per bottle, guaranteeing matching accuracy between revenue and cost.

6. General Ledger Posting & 3-Way Match Integration

Goods intake represents a fundamental shift in the enterprise balance sheet. Rather than waiting for monthly vendor statements, Orbit Commerce executes real-time perpetual posting upon dock acceptance.

3-Way Match Validation Matrix

The 3-way matching engine compares three distinct source documents before clearing vendor disbursements:

1. Purchase Order (PO): Internal commercial authorization establishing agreed quantities, delivery dates, and negotiated contractual prices.
2. Goods Receipt Note (GRN): Receiving dock physical confirmation establishing actual verified units received in merchantable condition.
3. Vendor Commercial Invoice (Bill): Supplier legal claim for payment requesting monetary disbursement for goods supplied.

       [Purchase Order]  <====== Contractual Agreed Rate ======>  [Vendor Invoice]
              ||                                                         ||
     Authorized Quantities                                       Billed Quantities
              ||                                                         ||
              \/                                                         \/
     [Goods Receipt Note]  <==== Verified Received Quantity =====>  [3-Way Match Kernel]

Double-Entry General Ledger Journal Entry

Accepting a goods receipt note generates an atomic operational journal entry. Holding accounts segregate physical goods acceptance from vendor invoice processing:

Voucher Reference: JV-GRN-2026-00319
Event Action: COMMERCE_GOODS_RECEIPT_POSTED
Description: Dock Goods Receipt PO-2026-00481 Al-Madina Wholesale Distribution

Account Code | Account Name                          | Debit (Dr) | Credit (Cr)
-------------|---------------------------------------|------------|------------
1200         | Merchandise Inventory                 | $4,722.00  | -
2010         | Goods Received Not Invoiced (GRNI)     | -          | $4,722.00
-------------------------------------------------------------------------------
TOTALS       | Balanced Operational Journal Entry    | $4,722.00  | $4,722.00

When the vendor commercial invoice arrives in the accounts payable inbox, the finance team matches the bill against GRN-2026-00319:

Voucher Reference: JV-AP-2026-00892
Description: Vendor Bill Matched to GRN-2026-00319 Al-Madina Wholesale

Account Code | Account Name                          | Debit (Dr) | Credit (Cr)
-------------|---------------------------------------|------------|------------
2010         | Goods Received Not Invoiced (GRNI)     | $4,722.00  | -
2020         | Input VAT Recoverable (15%)           | $708.30   | -
2000         | Accounts Payable Trade                 | -          | $5,430.30
-------------------------------------------------------------------------------
TOTALS       | Balanced Commercial Settlement Entry  | $5,430.30  | $5,430.30

This two-stage accounting model prevents inventory distortion: inventory is immediately capitalized when delivered, while trade liabilities are precisely cleared without unbilled accrual drift.

7. Deviation Handling & Exception Protocols

Receiving docks encounter delivery discrepancies daily. Operators must follow these standardized protocols rather than improvising on the floor:

8. High-Frequency Triage & Operational FAQs

What happens if a delivery contains perishable stock with an expiry date under 60 days?

Perishable stock with remaining shelf life below the minimum contractual acceptance threshold must be rejected immediately at the receiving dock. Dock operators must inspect manufacturer expiration stamps before scanning cases into inventory. If the expiry date violates supplier vendor terms (typically minimum 180 days for ambient groceries or 45 days for dairy), the operator selects Reject Due To Short Expiry in the receiving inspector, stages the cartons on the outbound return pallet, and refuses carrier sign-off.

Can a single purchase order be received across multiple split deliveries on different days?

Yes, Orbit Commerce natively supports split multi-delivery purchase order fulfillment across multiple distinct goods receipt notes. When a supplier delivers 60 cases of an authorized 100-case order, the inspector records 60 received units and transitions the purchase order status to PARTIALLY_RECEIVED. The remaining 40 units remain open on the order manifest. When the secondary freight truck arrives, the intake clerk references the same purchase order number, inspects the remaining balance, and completes the order with a secondary independent goods receipt note.

How does the system handle foreign currency purchase orders subject to exchange rate fluctuation?

Foreign currency purchase orders record both transaction currency amounts and base currency equivalents locked at the transaction exchange rate. When dock intake completes, inventory asset values are capitalized in the tenant base functional currency using the exchange rate effective on the goods receipt date. Any variance between purchase order issuance exchange rates and invoice booking exchange rates is automatically routed to Realized Foreign Exchange Gain/Loss (Account 5810).

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.
• Configure barcode hardware peripherals: EAN-13 Scale Barcodes & Scanner Wedge Processing.
• Audit enterprise ledger integrations: Enterprise Double-Entry General Ledger & Real-Time Financial Statements.
• Govern multi-branch distribution: Inter-Store Stock Transfers & In-Transit Custody Tracking.
• Hospital and front-of-house hospitality terminals: Orbit Dine POS Terminal Operations.