Skaldify Journal: Why reliable stock starts with a deliberate receiving step

14. September 2026

Good business software earns trust by being clear about what has happened and what has not. That is why the current Nextcloud ERP work begins the supplier purchasing flow with a small but decisive rule: a purchase order is not stock.

The emerging order workflow keeps line data fixed once an order is prepared, records its status in a traceable sequence, and makes partial goods receipt an explicit action. Only that receipt changes the inventory record. A draft and a shipping status do not quietly move numbers in the background.

Small boundaries, reliable records

It sounds modest, but the distinction matters. A purchasing view can show what is planned, what is on its way, and what has actually arrived without blending those states into one optimistic total. That gives later checks, corrections, and everyday decisions a more honest starting point.

The work is being developed and checked in a deliberately local test environment. Automated checks cover the reproducible setup needed for file-based integration work, while the next product steps add the API and interface for supplier orders and goods receipt.

Built for the next careful step

Roles, company data, and document configuration still need their own review, and a client application comes only after the core workflow and permissions have been tested. That sequence is intentional: first make the record dependable, then make it convenient.

For Skaldify, this is a quiet kind of progress. It is not a promise of a finished ERP or a production release. It is a useful foundation for a tool that should explain its state clearly when real work depends on it.