Real-time stock status
Red, amber and green per SKU and store, from the latest ERP import, with days of coverage.
Stock
Stock, lots and expiry dates under control in every store
See the red, amber and green before the write-off
Real-time stock status per SKU and store, stock-out management, lot and expiry-date tracking, and transfers to the store that will sell a lot in time.
Who uses it
- Supply chain director
- Store manager
- Quality and compliance
What is inside
Stock-out management
Current and predicted stock-outs, lost-sales estimate, root cause: late supplier, wrong forecast, missing transfer.
Batch and expiry tracking
Stock by lot with expiry date, alerts before a lot becomes unsellable, sell-through by lot.
Transfers
Proposed transfers from stores with excess to stores with demand, created as transfer orders in the ERP.
Transit stock
Goods in transit between the central warehouse and stores are tracked and deducted from the need.
Alerts and rules
Your own rules: coverage below X days, lot expiring in Y weeks, overstock above Z, sent by email or in IRISYS.
The module, screen by screen
01
Stock status and projection
Real-time stock status per SKU and store, with a twelve-month projection of stock levels from the forecast and the planned orders.
Red, amber and green by coverage
Twelve-month stock projection
Filters by city, brand, store, category and ABC class
02
Inventory levels and health
Total SKUs, units, value, critical and warning counts, plus stock by lifecycle and by ABC class. The charts show where value is sitting and how healthy it is.
Stock by lifecycle: growth, mature, end of life
Stock by ABC class
Export to Excel
03
Stock-out management
Current and critical stock-outs, lost revenue estimate and the monthly trend, with root causes: late supplier, missing forecast, missing transfer.
Lost revenue estimated per stock-out
Root cause per SKU
Trend by month and by store
04
Inter-store transfer suggestions
Before ordering more, IRISYS finds references overstocked in one door and short in another of the same city or retailer, and proposes the transfer with the quantity, the expected extra sales and the priority.
Same city and same retailer eligibility checks
Excess and deficit quantities from days of stock
Potential extra sales and priority per suggestion
05
Transfer history and tracking
Every transfer keeps its TO number, proposed, shipped and delivered dates, and status. In transit, delivered, rejected and claims are counted so nothing is lost between two doors.
TO number generated on approval
Proposed, shipped and delivered dates per transfer
In-transit, delivered, rejected and claim counters
06
Batch and expiry tracking
Stock by lot with expiry dates, near-expiry counts and value at risk, with batch upload from Excel for networks whose ERP does not manage lots.
Lots with expiry date per store
Near-expiry and expired counters
Batch upload from Excel
Key benefits
Stock-outs seen before they happen
Projected stock-outs per SKU and store from the forecast and the open orders.
Expiry loss cut
Lots are tracked with their dates; alerts fire weeks before a lot becomes unsellable.
Transfers instead of write-offs
Excess in one store is moved to the store that will sell it in time.
Store-level visibility
Every manager sees the status of their own store; the network sees the whole picture.
Stock value under control
Coverage in days and value by lifecycle and ABC class, per store.
Traceability for pharma
Lot and expiry per pharmacy, from receipt to sale.
What it changes
-30 to -50 %
overstock and expiry loss
31 days
of stock on the pilot, target 30
Per lot
traceability for skincare and pharma
How it works
Stock by warehouse, transit and lot is imported several times a day.
Status and coverage are recomputed per SKU and store.
Alerts and transfer proposals reach the planner before the loss.
Connected to your ERP
Stock from your ERP, lots from the ERP or a file
Stock by warehouse and transit stock are imported every four hours. Lot numbers and expiry dates come from the ERP when it manages them, or from a CSV / SFTP file or the REST API when it does not.
Implementation
Implementation
The same plan on every project. Your team spends a few hours a week; IRISYS does the rest.
- Week 1
Connect and check
ERP connector or CSV / SFTP export. Item master, stock by warehouse, sales history, open purchase orders. Data quality report.
- Week 2
Calibrate
Models trained on 12 to 24 months of history. Accuracy reviewed by category with the planner. Rules set: safety stock, service-level targets, case packs.
- Week 3
Run in parallel
IRISYS proposals compared every morning with the current process. Differences explained; rules and events added.
- Week 4
Go live
Proposals validated in IRISYS and created in the ERP. Thresholds opened category by category. On-site or remote training.
Questions about this module
Lot tracking uses the lot data your ERP already holds. Without lots, IRISYS still manages status, coverage and stock-outs.
Every four hours by default; hourly for statuses. Intraday POS feeds are possible.
Yes. The Manager role sees its stores only; planners and executives see the network.
Yes. Alert rules on coverage, expiry window, overstock and stock-outs are defined per category and sent in IRISYS or by email.
Yes. Central warehouse, regional warehouses, transit warehouses and stores are all locations with their own stock and rules.
Find the lots that will expire before they sell.
Send us a stock export with lot dates. We show you the value at risk per store and the transfers that would save it.