SUPPLY CHAIN
From the receiving dock to the workshop.
Stock is not a quantity in a table: it is material stored somewhere, in a given condition, usable or not. The physical layout is described in the application — buildings, storerooms, zones, locations — and every movement refers to it.
Three scales look at the same stock: the centre aggregates the fleet, the site sees its storerooms, the location holds the part. None is a view of another.
- Central viewShortages show at fleet scale, not storeroom scale: the requirements plan aggregates whatever perimeter you give it.
- Local viewA site sees its own stock in full — its storerooms, its locations, its rules — not a share of a total.
- Disconnected autonomyA site cut off from the network keeps issuing, receiving and tracing. It resynchronises on return.
A parcel arrives. It does not go to stock: it first clears technical receipt, and is only put away once what it is has been established.
- QuarantineWhere non-conforming goods go, not a step on the way: what fails the check is held apart.
- StorageA place, not a total: a stored item carries its address and the condition that lets it out.
- WorkshopWhere picking ends and returns begin: what comes back out is not presumed serviceable.
- Goods receiptArrivals are recorded first: quantities delivered, differences against what was expected. Nothing is judged yet.
- Technical receiptRecorded goods then go to inspection. Until an item is signed off, it cannot be fitted.
- ZonesA zone holds one condition: unserviceable, quarantine, a deployment batch. It takes space.
What an order consumes leaves the stock, and what comes back from the workshop is checked by the technical offices. Every part has an address — without one, stock is just a quantity.
- PickingWhat a work order consumes leaves the stock, and stock knows what is left.
- Return to storeWhat comes back from the workshop is not presumed serviceable: it is checked by the technical offices.
- Storeroom and locationA site holds several storerooms, and every item an address. Without it, stock is only a quantity.
WHAT THE MODULE COVERS
Stock described, not inferred.
Technical receipt
Arrival is handled in two steps: goods are recorded, then inspected. Differences between what was expected and what arrived are kept, and anything non-conforming is held rather than entering stock.
DocumentationReceiving worklist
Every arrival awaiting handling sits in one list, with what it came from — a purchase order, a transfer, a repair return — so nothing is processed from memory.
DocumentationStock policies
Thresholds, replenishment, allocation rules. What triggers a purchase requisition is configured per item and per storeroom, not buried in code.
DocumentationShipment preparation
Packing, containers and shipping documents. What leaves the site is prepared and recorded, including the packaging that is itself a repairable item.
DocumentationApproved sources
An item cannot be bought from just anyone. The supplier catalogue, approved sources and traced derogations frame what may be ordered.
DocumentationSupplier portal
Suppliers get their own access: they acknowledge your orders, announce their shipments with their documents and deposit their invoices. Nothing enters without your decision — what they deposit arrives as a proposal, which you accept or refuse.
DocumentationOccupancy
What each location holds, and how much room is left. Occupancy is read on the building plan rather than in a table.
Documentation
NEXT STEPS
Let's see what it looks like on your storerooms.
A 90-minute demo over video: product walkthrough, technical Q&A, review of your constraints. Tell us your context and we will tailor the session to it.
Or write to us directlycontact@envergure.cloud