B-01OBSERVED
PER-CLIENT INVENTORY BOOK
On hand, available, reserved and held for each client, with holds, adjustments and ownership transfers.
/DIGIWAREHOUSE
RECEIVE. HOLD. SHIP. PROVE IT.
With each client seeing only its own. DigiWarehouse takes a pallet from advance notice to carrier handoff as one chain of recorded facts, and every receipt, putaway, count, pick and load names a person or a device.
/WHAT IT COVERS
FOUR THINGS IT COVERS.
Four nouns, each with the state it has earned. The screens a person uses are designed; the records behind them are observed.
B-02OBSERVED
DIRECTED WORK AND HANDHELDS
Tasks for putaway, pick, replenish, count, pack and load, confirmed by scan on a handheld that works offline.
B-03OBSERVED
LABELS AND DOCUMENTS
Labels, carrier documents and shipment notices, with print outcomes recorded as separate facts.
B-04OBSERVED
APPROVALS BEFORE RISKY CHANGES
A write-off or an ownership transfer waits for a person to approve the exact payload.
/DIGIWAREHOUSE
WHAT DIGIWAREHOUSE DOES.
Six verbs, in the order a pallet meets them. Each carries the state of the claim underneath it.
- 01
RECEIVES
A receipt is observed at the door, lands restricted, and is matched to the order before it counts.
OBSERVED - 02
HOLDS
Each client's book: on hand, available, reserved and held, with holds, adjustments and ownership transfers.
OBSERVED - 03
DIRECTS
Tasks for putaway, pick, replenish, count, pack and load, confirmed by a scan on a handheld that works offline.
OBSERVED - 04
SHIPS
Closing a load hands the stock to the carrier and fulfils the order, as a consequence that carries a name.
OBSERVED - 05
SHARES
A client with a login sees its own orders, stock and documents. Client Link carries documents to systems that have no login.
DESIGNED - 06
PROVES
Every step names a person or a device, and a client can ask what was approved and by whom.
OBSERVED
A task assigned to a handheld is a plan. A task confirmed by a scan, at a place, by a person, is a fact. Confirmed is the difference between work that was assigned and work that was done.
/AREAS
EIGHTEEN JOBS IN SIX GROUPS.
Each area is a job a person does, with the board they land on. The area list is ours until the ERP landing publishes its own.
/CATALOGUE
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| ITEMS AND BARCODES | Item identity and packaging, with each client's own item codes and barcodes. | products.TypeIndexOBSERVED |
| TAGS AND SERIAL REGISTRY | Pallets, license plates, RFID tags and unit serials, unique across the operator. | identifiers.OpenBindingsOBSERVED |
| SERIAL NUMBER RANGES | Prefixes, range grants and leases for issuing serials. | None yet.PLANNED |
/ORDERS AND INBOUND
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| ORDERS, ASNS AND APPOINTMENTS | Orders, advance ship notices, purchase orders, transfers, returns and dock appointments as one record kind. | orders.CommitmentViewOBSERVED |
| RECEIVING | A receipt is observed, matched to an order with tolerance, then released into stock. | None yet.PLANNED |
| CHARGES | A charge recorded against an order. Rate cards and billing runs are planned. | None yet.PLANNED |
/INVENTORY AND LOCATIONS
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| INVENTORY AND AVAILABILITY | A per-client book: on hand, available, reserved and held, with holds, adjustments and ownership transfers. | inventory.AvailabilityOBSERVED |
| WAREHOUSE MAP AND RULES | Facility layout, places with capacity, and the hard rules a task must satisfy. | None yet.PLANNED |
| STOCK BY LOCATION | What is in each place, and every move between places. | locations.ContentsOBSERVED |
| COUNTS AND EXCEPTIONS | Counts, variances, shorts and inspections, with an exception queue. | capture.ExceptionQueueOBSERVED |
/WORK AND SHIPPING
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| WORK AND TASKS | Directed tasks for putaway, pick, replenish, count, pack, load and cross-dock. | work.TaskBoardOBSERVED |
| RELEASE, REPLENISHMENT AND CAPACITY | A release queue, replenishment planning and advisory capacity windows. | None yet.PLANNED |
| LOADING AND SHIPPING | Loads of sealed containers; closing a load hands stock to the carrier and fulfils the order. | None yet.PLANNED |
/FLOOR AND QUALITY
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| HANDHELDS AND OFFLINE WORK | Device sessions, task claims and offline leases for the floor. | capture.SessionBoardOBSERVED |
| SENSORS, SCALES AND COLD CHAIN | Scale and dimension readings, RFID reads and excursions that restrict stock. | capture.RegionBoardOBSERVED |
/DOCUMENTS AND APPROVALS
| AREA | WHAT A PERSON DOES | HOME BOARD |
|---|---|---|
| LABELS AND PRINTING | Label and document print jobs where printed, failed and unknown are different facts. | documents.PrinterQueueOBSERVED |
| DOCUMENTS | Stored documents, carrier labels and shipment notices, each owned by one client. | documents.DocumentIndexOBSERVED |
| APPROVALS INBOX | Requests drafted by agents or rules, approved by a person against the exact payload. | approvals.PendingApprovalsOBSERVED |
/WORKFLOWS
YOUR WAY OF WORKING IS A RULE.
Special labelling, serial control and the move, count and inspect tasks are kinds and rules the warehouse publishes, not code someone writes for one client. Authoring entirely new workflows is planned; today our engineers compose them with you.
OBSERVEDPLANNED
/THE FLOOR
THE FLOOR KEEPS SCANNING.
Handhelds hold a lease on their work, so a scan in a dead zone is queued as an intent and judged when the link returns. If a lease is revoked, what was admitted before the cut-off stands; what came after is refused and shown to the supervisor.
- 01
THE INSTRUCTION
A card says what to move, from where, to where and how many. One primary action per screen.
DESIGNED - 02
SCAN THE LOCATION
The operator scans the source. A wrong place is refused on the spot, not discovered later.
DESIGNED - 03
SCAN THE ITEM OR PLATE
The scan identifies the item or the pallet. Another client's pallet is refused without saying whose it is.
DESIGNED - 04
QUANTITY BY SCAN
Quantity is scanned, or typed where the user's setting allows it.
DESIGNED - 05
SCAN THE TARGET
Scanning the target completes the task and posts the move.
DESIGNED - 06
REPORT AN ISSUE
Preset reasons replace a notes screen, and each writes a short, a conflict or a hold.
DESIGNED
| STATE | WHAT THE OPERATOR SEES | WHAT THE RECORD DOES |
|---|---|---|
| QUEUED | A badge on the action, and a sync count that falls to nothing on its own. | The intent waits under the lease and is judged in order when the link returns.OBSERVEDDESIGNED |
| CONFLICT | The app asks the operator to choose another source or short the line. | A conflict is raised for a person to resolve, and the record keeps both sides.OBSERVEDDESIGNED |
| REFUSED | A plain refusal: the lease was revoked before the action was admitted. | The action is refused and logged for the supervisor, never silently dropped.OBSERVEDDESIGNED |
HANDHELD · MY WORKSAMPLE
PUT AWAY TO RACK A-01
CONNECTIONON LEASE
QUEUED0
PRINTERREADY
FIG · THE HANDHELD'S HOME, WITH ITS STATUS STRIP
/THE CLIENT VIEW
THE CLIENT SEES THE SAME FACT.
A cargo owner signs in and reads its own orders, stock and documents from the warehouse's record, with an as-of time on every board. Another client's pallet, scan or price never appears, and a refused lookup does not say whose it was.
/CLIENT VIEW · DESIGNEDits own owner only
/OPERATOR VIEW · OBSERVEDall owners, names the client
/RECORD · OBSERVEDone ledger, owner in the key
- /CLIENT VIEW · DESIGNEDits own owner only
- /OPERATOR VIEW · OBSERVEDall owners, names the client
- /RECORD · OBSERVEDone ledger, owner in the key
DESIGNED
A cargo owner with a login sees a live view of its own orders, stock and documents, and nothing of another client's.
OBSERVED
A scan of another client's pallet is refused without saying whose it is.
evidence · repo-path · wms/packages/wms-identity/README.mdOBSERVED
An operator may hold every client as owner and names the client it acts for; the record shows both.
evidence · repo-path · wms/packages/wms-identity/README.md/DIGIMESH
IT NEVER WORKS ALONE.
A warehouse is one party in a chain. Through Digimesh, DigiWarehouse shares the same facts with the client that owns the stock and the carrier that collects it, each under separate permissions.
/CLIENT LINK
KEEP YOUR ERP. FIX THE HANDOFF.
Orders, receipts, shipment advices and inventory snapshots move over EDI or REST with acknowledgments and one shared exception queue. Each inbound document is kept as evidence beside the order it opened.
DESIGNED
/CLIENT SYSTEMS · DESIGNEDERP, OMS or API
/CLIENT LINK · DESIGNEDdocuments with evidence
/DIGIWAREHOUSE · OBSERVEDthe same recorded facts
- /CLIENT SYSTEMS · DESIGNEDERP, OMS or API
- /CLIENT LINK · DESIGNEDdocuments with evidence
- /DIGIWAREHOUSE · OBSERVEDthe same recorded facts
DO WE HAVE TO RIP OUT OUR CURRENT WMS?
Not for the first session. We start with one client's order feed and one inventory export, so you see that client's record without touching the system your floor runs on. Running a facility on DigiWarehouse is a later, separate decision.
DESIGNED
/PERSONAS
BUILT FOR THE WAY YOUR TEAM WORKS.
Eight roles, each with its own scope and the board it lands on. Every scene runs on named operations, and every one carries its state.
R-01OBSERVED
3PL OPERATIONS MANAGER
SCOPE · ALL CLIENTS
A write-off request waits in the approvals inbox with its exact payload. The manager approves it, and the record shows who approved what.
RUNS ON
approvals.PendingApprovals
approvals.Approve
locations.PublishRuleSet
R-02OBSERVED
SHIFT LEAD
SCOPE · ONE FACILITY
Tasks are planned, assigned and confirmed by scan, so a temp starts on the next instruction instead of the shift lead's memory. Rules are published once and checked before any task starts.
RUNS ON
work.TaskBoard
work.Assign
work.Revalidate
capture.SessionBoard
R-03OBSERVED
FLOOR OPERATOR
SCOPE · ONE DEVICE SESSION
The handheld loses the network in a dead zone. Scans queue as intents under a lease and are judged when the link returns.
RUNS ON
capture.Login
capture.ClaimTask
capture.RecordScan
R-04OBSERVED
INVENTORY CONTROLLER
SCOPE · ALL CLIENTS
A count disagrees with the ledger. The variance lands on the exception queue, and a policy can post the correction as a recorded adjustment.
RUNS ON
capture.ExceptionQueue
capture.RecordCount
inventory.Adjust
R-05DESIGNED
CLIENT USER
SCOPE · ONE CARGO OWNER
The client signs in and sees its own orders, stock and documents, dated, with nothing of any other client.
RUNS ON
orders.CommitmentView
inventory.Availability
documents.DocumentIndex
R-06OBSERVED
CLIENT SERVICE
SCOPE · ALL CLIENTS, ON BEHALF OF ONE
A client calls about a late order. Client service opens the order for that client, names the client it acts for, and the record shows both.
RUNS ON
orders.Open
orders.Amend
orders.BookAppointment
R-07OBSERVED
QUALITY AND COLD CHAIN
SCOPE · ONE FACILITY
A temperature excursion in a cold room restricts the stock in it by policy. Quality inspects, then releases the hold or keeps it.
RUNS ON
capture.RegionBoard
capture.AcceptExcursion
inventory.Restrict
inventory.Release
R-08PLANNED
FINANCE
SCOPE · ALL CLIENTS
Finance reads the charges recorded against orders. A charges board and rate cards are planned, and not built.
RUNS ON
orders.RaiseClaim
/NOT BUILT YET
WHAT IS NOT BUILT YET.
DigiWarehouse is in build. These are the gaps we know about, each stated as it is.
PLANNED
Home boards for six product areas that have none today: serial ranges, dock, charges, layout, release queue and loads.
PLANNED
A per-person task view, so a handheld shows the operator's own task first.
PLANNED
Rate cards, billing runs and invoices for a 3PL's clients, derived from recorded activity.
PLANNED
A path for a customer's own people to author a workflow. Today our engineers compose one with you from the task kinds and rules the engine already has.
— NOT CLAIMED
A full item master with names, descriptions, dimensions and weights. Products holds item identity and packaging only.
— NOT CLAIMED
Lot-level genealogy, or compliance with any traceability rule.
/SESSION
PLAN A WAREHOUSE SESSION.
One client's order feed. One inventory export. We load both and open that client's view beside yours, so you see what the client would.