Orders · ERP
An order drags on. In which state?
The ERP keeps only today's status.
In progress yesterday, Delivered today. Nothing on the wait in between.
Fictional orders · synthetic data
The problem
The status has no history.
- Tonight's export replaces yesterday's.
- The time spent in a state is lost.
- The ERP cannot be changed.
Nothing is changed
lumnik compares each night with the previous one.
- Each order is followed by its number.
- Each status change enters a journal, dated.
- Nothing is written to the ERP.
What had to be written
key: order_id
dormancy:
after: 25mOne order followed, one alert if it stops moving.
The whole scenario fits in 3 declaration files, 73 lines.
The journal
7 moves, each with its waiting time.
- C-01: entered, then in progress, then delivered.
- C-02: cancelled.
- Each line gives the time spent in the state left.
Real values, replay of 28 October 2026.
The orders that stand still
4 orders did not move. They alert.
- C-06, C-08, C-09, C-11.
- One alert per stall, not at every tick.
The business decides
EN ATT means in progress. It is not a move.
- The business declares EN ATT as an alias.
- C-08 and C-09 are renamed.
- Their clock and their alert stay.
Try it
The scenario replays end to end.
Three nights, a declaration, the journal: each step is published with its output.