Inventory

Stock control that stays honest about the shelf

Multi-warehouse quantities that move when work moves — because receipts, issues and transfers are recorded by the same actions that do the work.

Ten tools · Multi-warehouse · Lot traceability and cycle counting

Illustrative product view with sample data. Request a live walkthrough.

Before Caspian ERP

The system says twelve; the shelf says three

Stock records go wrong in one of two ways: nobody records the movement, or somebody records it twice. Both end the same way.

Stock is updated after the fact

Material is taken for a job and written down later, if at all. By the time anyone reconciles, the trail is a week cold.

Counting means stopping

A full stocktake needs the warehouse shut and everyone counting. So it happens once a year, and the rest of the year is guesswork.

Critical spares are found missing at the worst moment

The part is on the system and not on the shelf, and you discover it with a machine already down.

What it does

Stock that reflects what the operation actually did

Every quantity change is a movement with a reason, a person and a time behind it.

Multi-warehouse stock

Real quantities per location, not one blended organization-wide number.

  • Warehouses, yards and site stores as separate locations
  • Stock levels held per item per warehouse
  • Minimum levels and reorder visibility per location
  • One catalogue shared with procurement and manufacturing

Movements and adjustments with a reason

Every change is a record — receipts, issues, transfers and corrections.

  • Movements created by receipts, issues and transfers
  • Adjustments require a reason, so shrinkage is visible
  • Full history per item and per location
  • Attributable: who moved it, and when

Lot traceability

Batch and lot tracking for the items where provenance matters.

  • Inventory lots with batch references and dates
  • Trace a lot from receipt through to where it was consumed
  • Expiry-sensitive stock managed rather than assumed
  • The evidence a client audit asks for

Transfer orders between locations

Moving stock between sites is a controlled transaction, not a phone call.

  • Raise a transfer, dispatch it, receive it at the far end
  • In-transit stock visible rather than missing
  • Discrepancies captured at receipt
  • The paperwork the receiving site actually needs

Cycle counting instead of an annual shutdown

Count a slice of the warehouse continuously and keep accuracy high all year.

  • Cycle count plans defining what gets counted and how often
  • Counting sessions performed on a phone in the aisle
  • Variances recorded and turned into adjustments with a reason
  • Accuracy trends rather than one annual verdict

Demand forecasts

Forward view of what will be needed, so reordering is planned rather than reactive.

  • Forecasts held per item and location
  • Compared against current stock and open orders
  • Critical spares identified before they are urgent
  • Feeds purchasing decisions in Procurement

How an item moves through the system

From a purchase order to consumption — every step a recorded movement.

Purchase order
Goods receipt
Warehouse stock
Transfer
Issued to work order
Cycle counted
Every tool in the module

Ten tools for physical stock

Everything from the catalogue record to the count in the aisle.

Inventory Items

The stock-keeping view of the shared item catalogue — units, categories, minimums and identifiers.

Warehouses

The locations you hold stock in: main stores, site containers, yards and workshops.

Warehouse Stock

Quantity on hand per item per location, with minimum levels and reorder visibility.

Stock Movements

The full movement history — every receipt, issue and transfer, attributed and time-stamped.

Stock Adjustments

Corrections with a mandatory reason, so variance is explained rather than absorbed.

Inventory Lots

Batch and lot records for traceable items, from receipt through to consumption.

Transfer Orders

Controlled movement between warehouses, with dispatch, in-transit visibility and receipt.

Cycle Count Plans

What gets counted, how often, and by whom — continuous accuracy instead of an annual shutdown.

Cycle Count Sessions

The count itself, performed in the aisle on a phone, with variances captured as they are found.

Demand Forecasts

Expected consumption per item and location, compared against stock on hand and orders in flight.

Connected, not bolted on

Stock is a shared record, not an island

The item you buy, store, consume and invoice against is one record.

Receipts create stock

A goods receipt in Procurement is the movement that puts the item on the shelf. There is no second entry to forget.

See Procurement

Spares issued to work orders

Parts consumed on a maintenance job are issued from stock, so the work order carries its real material cost.

See Maintenance

Components for production

A bill of materials consumes the same stock records, so production plans meet the actual shelf rather than a hoped-for one.

See Manufacturing

Who lives in it

For the people who own the shelf

The warehouse, the planner and the person who has to answer for the variance.

Storekeeper

Receives, issues and transfers stock from a phone in the aisle, and runs cycle counts without shutting the store.

Materials planner

Works from forecasts, minimum levels and open orders instead of walking the racks to see what is short.

Finance controller

Gets stock movements and adjustments with reasons attached, which is the difference between a valuation and a guess.

Yours to shape

Configure inventory to your physical reality

One organization has a single store; another has eleven sites and a yard. Both are normal.

  • Create as many warehouses, stores and yards as you actually have
  • Set minimum levels and reorder points per item per location
  • Decide which items are lot-tracked and which are not
  • Define cycle count plans by category, value or movement frequency
  • Require a reason code on every adjustment, and restrict who may make one

See what an administrator controls

Inventory · Settings
SettingValue
Warehouses6 active
Lot trackingBy category
Adjustment reasonMandatory
Cycle countWeekly, A-items
Negative stockBlocked

Inventory questions we get asked

Can we run several warehouses and site stores?
Yes. Stock is held per item per location, so a main store, a yard and a container on site are separate records with their own minimum levels — not one blended number.
Do we have to stop work to count?
No, that is the point of cycle counting. You define plans for what gets counted and how often, and counts are performed in the aisle on a phone while the warehouse keeps operating.
How does stock stay accurate?
Because the actions that do the work are the actions that move the stock. A goods receipt in Procurement, an issue to a maintenance work order and a transfer between sites each create a movement, so accuracy does not depend on someone remembering to update a second system.
Can we trace a batch back to its supplier?
For lot-tracked items, yes. Inventory lots record the batch from receipt onwards, so you can trace where a given lot went and which order it arrived on.
Does inventory value flow into finance?
Movements and adjustments are recorded with reasons and attribution, which is what a valuation needs. Finance works from the same item catalogue, so codes agree across the two.

Browse every module