Sales · live · metalzone.curiopal.com/api
Sales orders
asking…
Total Sales Orders
—
asking…
Total Order Value
—
asking…
To Be Delivered
—
asking…
On-Time Delivery
—
no promised or requested delivery date in the schema: sales_order carries neither, so nothing can be on time or late
Avg. Fulfillment Time
—
both events of an imported order carry the sheet’s date, so no elapsed time can be computed
OrderOrder dateCustomerSpecificationQuantityTheoreticalValueStatusDelivery
asking metalzone.curiopal.com/api for the orders…
Quantity is the sheet's tonnes in kilograms; theoretical is the catalog's kg/piece × the sheet's pieces, and the two disagree on most rows: both are shown, neither is repaired (principle 3). Every order is dispatched: a booked sale is goods that left, and nothing in the sheet says an invoice was exported. Delivery progress is 100 % once the ledger holds a DISPATCHED event and NONE otherwise: dispatched is the last state the ledger knows, and there is no proof of delivery. Open a row for the lines, the dispatch and the ledger.
Order Fulfillment
orders by status, in the schema's words
no order on the ledger
order_status is confirmed, picking, packing, ready, dispatched and invoiced. The board's In Production, In Transit, Partially Delivered, Delivered and Cancelled are defined in neither the schema nor the workbook, so no row is drawn under them.
Delivery Performance
the board draws an on-time gauge and an on time / delayed split
Nothing to show yet
on time against what? sales_order has no requested and no promised delivery date, and a dispatch has no proof of delivery. Nothing in v01 can say a delivery was late.
Upcoming Deliveries
the next seven days
Nothing to show yet
no future delivery exists to list: every imported order is already dispatched, and no order carries a delivery date to look forward to.
Quick Actions
every action the board offers, none of them live in the demonstrator