Operations module
STOCK / MODULEStock
One shared, race-safe inventory ledger that Manufacturing and Point of Sale both post into live, with row-locked balance updates that prevent over-issuing.
Receipt to Fulfilment
- 01
Post receipt
The movement posts under a row lock, updating on-hand balance for that item/warehouse/bin.
- 02
Put away
Stock is assigned to a bin within the warehouse's hierarchical structure.
- 03
Reserve
Stock can be reserved against a pending demand without being physically moved yet.
- 04
Issue or transfer
An issue or transfer posts only if the available-stock check clears — no over-issuing.
What it is
The Vercentlabs Stock module is a real-time, multi-location inventory ledger that tracks on-hand quantity, reservation, and valuation per item, warehouse, bin, and batch — one shared ledger that Manufacturing and Point of Sale post real movements into.
Module atlas / operating conditions
Why Stock becomes difficult in fragments
Stockouts and overstock
Without a live, accurate count, ordering decisions are guesses — you either run out or tie up cash in excess inventory.
No multi-warehouse visibility
One location's stock is invisible to another, so transfers and fulfillment decisions happen blind.
Batch/serial traceability gaps
When a defect surfaces, tracing which batch or serial it came from — and where else it went — takes hours instead of minutes.
Unbalanced adjustments
Manual stock corrections happen with no consistent record of why the number changed.
Operating outcomes
What changes when Stock shares one system of record
A number you can trust in real time
Row-locked movement posting means two simultaneous transactions can't both succeed against stock that isn't there.
Visibility across every warehouse and bin
Typed warehouses and a hierarchical bin structure make stock searchable down to its physical location.
Traceability when it matters
Batch and serial tracking connect a unit back to its receipt, and forward to wherever it shipped.
Consistent, costed valuation
Configurable moving-average or FIFO costing keeps the stock value on the books defensible.
Capability architecture
The module, decomposed by operating capability.
5 capability groups organised by the way the product works, not as a flat marketing feature wall.
Real-time ledger & balances
The core of the module — a race-safe, row-locked movement ledger.
- 01Row-locked movement posting enforcing available-stock checks before it allows an issue
Movement types
Every way stock changes, each permission-gated.
- 01Receipt, issue, transfer, adjustment, return, and count movements
- 02Atomic issue+receipt pair posting for transfers
Costing & valuation
How the stock value on the books is calculated.
- 01Configurable moving-average or FIFO costing
Traceability & reorder planning
Following a unit through its life, and knowing when to reorder it.
- 01Batch and serial tracking
- 02Reservations
- 03Reorder rules feeding a low-stock dashboard
Warehouse & bin structure
Where stock physically lives.
- 01Typed warehouses
- 02Hierarchical bin structure
Primary operating sequence
A transaction-level view of how work progresses through Stock.
See it work
Receipt to Fulfilment
The ordered process a real Stock workflow follows inside Vercentlabs.
Trigger
A purchase order receipt, a production output, or a transfer request arrives.
- Post receipt
The movement posts under a row lock, updating on-hand balance for that item/warehouse/bin.
- Put away
Stock is assigned to a bin within the warehouse's hierarchical structure.
- Reserve
Stock can be reserved against a pending demand without being physically moved yet.
- Issue or transfer
An issue or transfer posts only if the available-stock check clears — no over-issuing.
- Value
Moving-average or FIFO costing keeps the valuation current with every movement.
Approvals
- 01Movements are permission-gated by type, but Stock has no approval workflow of its own — thinner governance than Procurement by design.
Automated actions
- 01Transfer completion auto-posts the matching issue/receipt pair
- 02Reorder rules feed a low-stock dashboard
Connected modules in this workflow
Outcome
An accurate, race-safe on-hand balance that Manufacturing and Point of Sale can both post real movements into, live.
Operational proof
Stock, documented as an operating system.
Capability architecture
5 groups
Grouped by how the module is actually structured.
Primary operating sequence
Receipt to Fulfilment
Rendered above as an ordered process rather than a feature collage.
Connected system
3 modules
Adjacent modules are linked through the operating model on this page.
Business outcome
A number you can trust in real time
Row-locked movement posting means two simultaneous transactions can't both succeed against stock that isn't there.
Ready to see Stock running on your own data?
Book a DemoSystem map
Stock does not operate alone.
The handoffs below are part of the operating model, not decorative cross-sells.
Manufacturing posts real, auditable material-issue and finished-goods movements directly into the Stock ledger — a confirmed, wired connection.
Every POS checkout deducts real inventory in the same database transaction as the sale — a confirmed, wired connection.
Sales order lines carry a warehouse reference, but standard order fulfillment does not yet call a stock-movement post — this link is not yet wired end to end.
Output register
What Stock tells operators and managers
On-hand quantity, reserved quantity, valuation, and low-stock count
Audience / Warehouse staff, inventory planners
Rule register
What the module can run on its own
Completing a transfer automatically posts the matching issue and receipt as one pair — never one without the other.
Configured reorder points feed a live low-stock dashboard for planners.
Control register
How Stock stays governed
Module-specific controls shown separately from the platform-wide security architecture.
Every movement type is gated by permission, enforced at the row level.
Movement posting uses idempotency keys to prevent a retried request from double-posting.
Unlike Procurement, Stock does not have its own approval chain today — access control is the primary governance layer.
What to plan before going live.
- 01
Warehouse and bin structures are set up to match your actual physical layout before go-live.
- 02
Opening stock balances are migrated and reconciled against a physical count, not estimated.
- 03
Costing method (moving-average or FIFO) is chosen per item category.
- 04
Stock has no mobile navigation entry today — plan for desktop/browser or handheld-scanner-via-browser workflows.
Buyer questions
Questions teams ask about Stock
Does a Sales order automatically reduce stock?
Not yet for standard order fulfillment — order lines carry a warehouse reference, but no stock-movement call has been found in that path. Manufacturing and Point of Sale are the two flows confirmed to post real stock movements today.
How is stock kept accurate under concurrent activity?
Movement posting is row-locked and enforces an available-stock check before it allows an issue, so two simultaneous transactions can't both succeed against stock that isn't there.
Is Stock accessible on mobile?
No — Stock has zero entries in the mobile navigation today. It's a desktop/browser workflow.