Skip to content

Platform

Order Lifecycle

Placed → Vetted → Loaded → In transit → Arrived → Paid → Fiscalizing → Completed — one canonical state machine from state_machine.go.

Order Lifecycle

Built for supplier-led logistics networks

Roles

6 connected

System of record

One shared truth

Live updates

Boards stay in sync

Surfaces

Portal · Mobile · Desktop

Capabilities

Plan, dispatch, and settle on one picture

Smart dispatch & load match

Match orders to trucks from forecasted demand, capacity, and warehouse constraints — with human override on every assignment.

Read more

Live fleet & on-time delivery

See planned vs actual routes across the network. Spot deviations before retailers call and keep every role on one ETA.

Read more

Payment & gate confidence

Reconcile COD, gate seals, and capacity utilization so treasury and payload teams close the day without spreadsheet fire drills.

Read more

KEY DIFFERENTIATORS

Why leaders choose Pegasus order lifecycle

No soft complete

ADR-009: no ARRIVED → COMPLETED without fiscalizing.

Sentinel errors

zone_miss, geofence_violation, inventory_exhausted, credit_limit_breached — actionable, not generic 500s.

Cross-role parity

Portal and mobile read the same labels for the same order ID.

BUSINESS VALUE

Examples of business value on the Pegasus platform

Maintained accurate, real-time inventory visibility across supplier and warehouse nodes.

60%

Reduction in stock-outs

Dispatch and fleet coordination on one order truth — fewer manual handoffs.

+53%

On-time delivery

Supplier, warehouse, factory, driver, retailer, and gate on one shared order record.

6

Roles connected

Boards and maps stay aligned automatically — no manual refresh.

<2s

Live updates

CORE CAPABILITIES

What this solution enables

ENTERPRISE VALUE

Driving real network value

Regional supplier network

Pegasus gave us one dispatch board and one payment truth — we stopped reconciling three spreadsheets every morning.

Operations leadSupplier control plane

Multi-site warehouse

Gate seal to retailer tracking stayed on the same order ID. Drivers and warehouse admins finally saw the same state.

Warehouse adminDispatch & fleet

Retailer chain

Shop-closed respond and pay-at-delivery work the same on desktop and mobile — no duplicate workflows to maintain.

Retail opsLast-mile delivery

HOW IT WORKS

From signal to settled outcome

  1. 01

    Placed & vetted

    Retailer checkout creates PENDING; supplier approves or rejects before dispatch.

  2. 02

    Loaded & sealed

    Warehouse assigns trucks (LOADED); payload seals before IN_TRANSIT.

  3. 03

    In transit & arrived

    Driver telemetry feeds maps; geofence gates ARRIVED and payment entry.

  4. 04

    Paid & completed

    AWAITING_PAYMENT / PENDING_CASH_COLLECTION / DELIVERED_ON_CREDIT → FISCALIZING → COMPLETED.

why it matters

Status accuracy is trust

Operators lose trust when AI or automation cannot explain why an order cannot complete. The lifecycle is the contract between field teams and finance.

From firefighting to structure

Exceptions like SHOP_CLOSED_PENDING are first-class states, not chat threads.

Money follows state

Ledger and OFD movements attach to fiscalizing — not to informal “marked delivered” clicks.

EDGE CASES

Exception paths that stay consistent

SHOP_CLOSED_PENDING

Driver can leave without fake delivery; later reopen to payment or cancel paths.

FISCAL_FAILED

Retry FISCALIZING or force COMPLETED only through audited paths.

CANCEL_REQUESTED mid-route

Must resolve to CANCELLED or resume LOADED/IN_TRANSIT/ARRIVED.

zone_miss

Checkout and dispatch reject destinations outside topology service areas.

AI & DATA

Intelligence on a consistent data plane

Layer

Reliable change events

Every confirmed update notifies the right apps in the same step — screens never diverge from the order truth.

Layer

Live coordination

Dispatch boards, fleet maps, and retailer tracking stay aligned automatically — no manual refresh.

Layer

AI with proven fallback

Smart assist for dispatch and recommendations always falls back to proven planning rules — never blocks the floor if models are slow.

Specs

Technical details

pegasus.spec
Source of truth
order/state_machine.go
Money unit
Integer minor units
Fiscal
ADR-009 hard-gate
Safe retries
Required on critical save actions

use cases

Related use cases on the Pegasus platform

Discover our platform

Live demo with a Pegasus expert

Get a personalized walkthrough with a Pegasus specialist and see how to run dispatch, fleet tracking, and payments across your network.

Request demo

Discover the platform

Take a tour

See how Pegasus unifies planning, dispatch, and execution through one control plane for every role in your network.

Take platform tour