Stock integrity
Negative-balance protection, paired transfers, exact missing/owed reduction and a verified movement trail.
CASE STUDY / 03
ONE Warehouse
STOCK · PRODUCTION · LABELS
IN USE · SKLAVOUNOS MEAT
This presentation uses the ONE identity. The documented functions are used at Sklavounos Meat. Portfolio naming does not change the architecture or installed applications.
What is in stock, where it is and what needs to happen next. Warehouse organizes stock movements, transfers, shortages, production and controlled label printing.
CURRENT STATEProduction core · Inventory v1 live as a read-only projection in One
00 / AT A GLANCE
The project at a glance.
PROBLEM
A final balance is not enough; every change needs a location, direction, reason, pending state and auditable trail.SOLUTION
An autonomous system that organizes stock, transfers, purchasing, special workflows and controlled printing into distinct operational areas.IN USE BY
Warehouse operations covering stock, transfers, shortages, purchasing, production and labels.OPERATES ACROSS
A Postgres-backed web service and an internal Windows print agent; One receives bounded read-only projections only.MY ROLE
Product design and UX, backend, data flows, labels/printing and deployment.STATUS
The core service is in production. Inventory v1 is live as a controlled read-only projection in One. Newer SSO and label/print changes require separate, current release evidence.01 / THE NEED
Inventory must explain every change.
A real warehouse needs more than a final number. It needs location, movement direction, reason, pending state, receipt, shortage and an auditable record of who did what.
- CENTRAL and WORKSHOP need clear balances and linked transfer movements.
- Shortages, pending quantities and partial receipts must remain visible until closed.
- Labels and print jobs must stay bound to the exact approved data and layout version.
02 / IN PRACTICE
Critical workflows remain visible.
The team checks stock at each location, records each movement and tracks outstanding work until it is closed. Warehouse remains the source of this information.
- Every stock change is tied to a location, direction, reason and movement history.
- Transfers between CENTRAL and WORKSHOP, shortages, pending quantities and partial receipts remain visible until they are closed.
- Labels are printed at the approved station, using the data and layout of the approved version.
03 / PUBLIC-SAFE DEMO
The operational model becomes visible.
Three static renders based on the Stock, Movements and Label Center surfaces show how locations, pending quantities, the audit trail and station-scoped printing connect — using synthetic data only.
Tap to view full image
Tap to view full image
Tap to view full image
The structure comes from the current Warehouse source interfaces, while every product, SKU, quantity, user and reference is fictional. No production database was captured, and the Label Center visual is not evidence of a production release.
04 / THE FLOW
From movement to an evidence trail.
The system organizes distinct operational areas without conflating product stock, freezer balances, consumables and controlled printing.
- 01
STOCK
Locations and movements
Balances, IN/OUT, paired transfers, overdraw protection and movement history. - 02
SUPPLY
Purchasing and receiving
Purchase suggestions, pack rounding, partial receiving and idempotent repeat handling. - 03
SPECIAL FLOWS
Shortages, freezer, consumables
Separate workflows and ledgers for operations that should not be compressed into one table. - 04
LABELS
Queue and HPRT agent
Station-scoped jobs, terminal states and version-bound payloads for controlled physical printing.
The public visual is a synthetic functional map. It uses no real products, quantities, suppliers, lots or production labels.
05 / EVIDENCE
Critical flows have been characterized and tested.
The case study is grounded in real code, tests, restore evidence and guarded release handoffs without exposing operational data.
Purchasing and receiving
Stable purchase suggestions, pack rounding, capped receiving and safe retries without duplicate movements.
Read-only integration
The production-active aggregate bridge to One is GET-only, bounded and exposes no rows, suppliers or credentials.
Controlled label evolution
Label design and print changes proceed only through immutable drafts, separate activation, audit reasons and snapshot-bound print jobs.
06 / SCALE & EVIDENCE
Controlled scale with an evidence trail.
These figures come from the exact restore and controlled activation of the Warehouse read-only projection in One.
- Tables / restored rows
- 20 / 52,425Exact isolated restore of the documented production snapshot.
- SELECT grants
- 7The production-read role has exactly seven explicit grants, all read-only.
- Read-only cadence
- 5 minThe controlled cache projection refreshes every five minutes.
- Current results
- 6 / 6Two observed cron runs produced six current results in one attempt with no error.
LAST VERIFIED2 August 2026
07 / TODAY
Live core. Controlled read-only projection in One.
The core Warehouse service is in production. Inventory v1 is live as a controlled read-only projection in One. Newer SSO and label/print changes are presented only when separate, current release evidence exists.
CURRENT FOCUS
- 01Physical printer acceptance for every new agent and layout release.
- 02Current release evidence for SSO and every new inventory projection.
- 03Controlled rollout of Label Designer and the compatible HPRT Agent.
- 04An append-only freezer ledger and stricter print-job leases.
08 / CONTACT
Does an operational workflow need a clearer system?
Describe the current process, the tools you use and the point where time, information or control is being lost. The first conversation clarifies the need and the boundaries of a solution.