Powered by STOS, the Smart Terminal Operating System
Warehousing with a stock figure you can defend
Stored cargo gets the same discipline the container yard already has: a known location, a known quantity and a movement record behind every change. When a customer disputes a stock position, the answer comes from the system rather than from a stack of gate passes.
How the module runs
● 5 stages
Receipt
01Put away
02Stored
03Picked
04Issued
05
Why it exists
A stock number is only worth the movement record behind it
Warehouses run on spreadsheets for longer than they should. It works until a quantity is challenged, and then nobody can show when the cargo arrived, where it was put, who moved it or why the figure changed. STOS Warehouse records the movement, not just the balance, so the balance is reconstructable at any date.
What Warehouse covers
Goods receipt and issue posted against the owning party
Stock ageing
So long-dwell cargo surfaces before it becomes a dispute
Cycle counts and adjustments
Each with a reason recorded against it
Bonded carrier movements tracked in and out
Storage charges feeding the same billing run as the terminal
Stock
Where it is and how much
Location mapping is the foundation. Everything else in the module posts against a location and an owning party.
Locations and bins
Bonded and general areas mapped down to the bin, so a put-away instruction points at a place rather than a general area.
Stock on hand
Quantity by party, commodity and location, with the movements that produced it available behind each figure.
Stock ageing
How long cargo has been stored, bucketed, so slow-moving and long-dwell stock is visible early.
Movements
Every change leaves a record
Receipts, issues and adjustments are postings, not edits. The balance moves because something was recorded.
Goods receipt
Cargo received against the owning party and placed into a location, with the reference it arrived on.
Issues and releases
Cargo released against an instruction, checked and posted out of its location.
Cycle counts
Counts raised, differences recorded and adjustments posted with a reason against each.
Control
Charges and oversight on one data set
Warehouse activity feeds the same commercial and reporting layer the rest of the platform uses.
Bonded movements
Bonded carrier movements in and out, kept separate from general stock for customs purposes.
Storage billing
Storage charges calculated from recorded dwell and fed into the terminal billing run, not invoiced separately.
Stock reporting
Position by party, commodity, location and age, over the same data operations works in.
Roles
Who sees what
Access is granted per module and per role, so two people signed into the same platform see different work.
| Role | What the role works with |
|---|---|
| Warehouse operator | Receipts, put away, picking and issues against a location |
| Bond officer | Bonded movements in and out, and the records customs asks for |
| Stock controller | Cycle counts, adjustments and ageing |
| Finance | Storage charges flowing into the billing run |
| Administrator | Location mapping, parties, commodities and role access |
How it fits
The party storing cargo is the party on the invoice
Warehouse runs on the same identity service, the same party master and the same billing layer as STOS core, so storage charges land on the account the terminal already bills rather than on a second set of books.
- Single sign-on with STOS core and every other module
- One party master shared with the terminal and with Accounts
- Storage charges in the same billing run as handling
- Roles granted per module, so access is specific rather than blanket
FAQ
Questions buyers actually ask
They are handled in the same module but kept distinct, because bonded movements carry customs obligations that general warehousing does not. Locations are mapped across both.
By the movement record. Receipts, issues, counts and adjustments are postings with a date, a party and a reason, so the balance at any date can be reconstructed rather than argued over.
No. Storage feeds the same billing run as terminal handling, so a customer receives one invoice from one system.
Yes. Modules are licensed individually, so a terminal that does not run a warehouse does not pay for one.
Ask for a walkthrough. We will show the module running against representative data and talk through how it would map onto your locations and parties.
See Warehouse on your own terminal data
Bring your own customers, tariffs and volumes and we will walk the module end to end on a live system.