Phase 4.5 · Supplies Needed live

Store requested.
District delivered.

A focused supply workflow for the operational gap between “we need it” and “it arrived”—with store boundaries, district visibility, exact quantities, and delivery evidence.

Open supply inbox ↗Read the guide

Accountable fulfillment

One small workflow. No missing handoff.

The feature is additive: assets, work orders, inventory, offline sync, and predictive analytics remain unchanged.

Store scoped

A store sees only the requests in its assigned operating scope.

District routed

The store’s district is derived on the server and cannot be spoofed by a request.

Quantity exact

Partial deliveries track each line; final delivery closes every remaining quantity.

Audit complete

Create, edit, delivery, and cancellation events remain append-only and time-stamped.

Lifecycle

Request → partial → delivered.

Every state change runs in one database transaction. Duplicate delivery attempts return a conflict instead of rewriting history.

RequestStore · items · quantity

RouteDerived district · scoped inbox

DeliverPartial or complete quantities

ProveActor · time · immutable log

Release captures

Store, district, desktop, field.

Four responsive views captured from the working Phase 4.5 preview.

**District inbox on desktop**Queue, route, status, and delivery metrics in one view.

**Partial-delivery detail**Requested, delivered, and remaining quantities beside an immutable timeline.

**Mobile store view**The same request workflow adapted to a 390-pixel field viewport.

**Public Phase 4.5 release**Release context, lifecycle, API, and operating guide in the public project site.

API v1 included

Automate request intake, delivery updates, and CSV reporting.

Open developer portal →