UXA Flow: Distribution Operations
A working operations platform connecting purchasing, warehouse inventory, customer orders, partial shipments, and stock imports. A real Yodexa product, presented here with synthetic business data.
The project today.
- The working demo is integrated into this website. Each visitor gets a separate synthetic dataset, retained for up to 30 minutes while the server stays running. The source application includes a persistent SQLite database and a separate import worker.
- Harbor Distribution, its people, suppliers, customers, and records are synthetic. UXA Flow is a real Yodexa product. This public preview uses a synthetic distribution company.
- Selectable demo roles let you explore the workflows. This demonstration contains no client data. A client deployment needs its own authentication, hosting, monitoring, and operational review. No production capacity or business savings are claimed.
26 checks passed
Domain, HTTP, and website demo verification
Node.js 24.11.1 on Windows, 6 October 2026; fresh SQLite databases. Test report retained with the source.1 of 2 reserved
Two simultaneous orders each requesting 70 of 100 units
Two worker threads with independent database connections, released at a shared barrier. Exactly one confirmation succeeded; 70 reserved, 30 available.Recovery verified
Interrupted import resumed without repeating its receipt
A worker process exited after claiming a persisted job. A fresh connection recovered its expired lease and applied the row once.The starting point.
A distributor needs one dependable view of goods on hand, stock promised to customers, and goods moving between warehouses. Receiving, reserving, shipping, and cancelling all change the same balances. The application must keep those changes coherent when operations overlap or fail.
Inside the application.
The thinking behind the outcome.
- Orders, purchases, and transfers share the inventory ledger. Reservation, shipment, and receipt commands update their records and movements in one database transaction.
- Operation identifiers store the accepted result with a payload fingerprint. Repeating an accepted command returns its result; changing the input under that identifier is rejected.
- Stock files enter a persisted queue. A separate worker validates the complete file, applies accepted rows together, and recovers expired processing leases after interruption.
- The dashboard links shortages, incomplete shipments, transfers, and failed imports to actionable records. Product details expose the movements behind each balance.
Our role
- Business workflow and relational data modelling
- Transactional inventory and order engine
- Operations interface with record details, filters, and CSV export
- Durable import worker, failure recovery, and verification
What came to life.
- Seven connected views: overview, orders, inventory, purchasing, transfers, imports, and activity.
- Order creation, full-order reservation, partial shipments, and cancellation of the unshipped remainder.
- Supplier purchases with partial receipts, warehouse dispatches with partial destination receipts, and persistent stock data.
- Validated stock receipt imports, automatic retry of temporary processing failures, and actionable row errors.
- Manager, Sales, Warehouse, and Auditor demo roles, stock export, reconciliation checks, source code, and run documentation.