Open purchase orders
Ordered quantities and expected receipt dates.
01 — Inventory Movement Agent
Turn excess inventory into liquidity and an actionable decision
Keeper links every SKU's movement to forecast demand, open purchase orders, branches, shelf life and margin. It then compares transfer, purchase-hold, return, liquidation and wait-and-hold options, and shows the SAR impact of each choice before you approve.
The agent runs on top of your existing ERP and WMS, and does not duplicate the inventory reports they already produce. Illustrative example of what the dashboard below can show.
Keeper Command CenterIllustrative example of Keeper output
Inventory value11.0MSAR
Dead stock640K5.8% of value
Transfer opportunities31across branches
Portfolio classificationby value
Internal transfer opportunity.
Move 12 SKUs to three branches before any discount.
The agent's jobs
Your inventory's full health — not just a dead-stock report.
Every job has a clear deliverable, and the final decision stays with your team.
1
Spot the excess trend before it forms
Monitors slowing demand, rising cover, incoming additional purchases and shifting seasonality, and identifies the last suitable moment to intervene.
Delivers: an early warning by SKU and the value at risk of going dead
2
Classify the portfolio dynamically
Classifies each SKU by its own movement and seasons, shows the reason for the classification and its confidence range, and distinguishes temporary excess from genuinely dead stock.
Delivers: portfolio classification with the reason for each category
3
Optimize redistribution
Compares forecast demand with transfer cost, sell-through probability, and the impact of transfer on service level, and determines where, when and how much quantity to move.
Delivers: transfer opportunities ready to approve
4
Compare processing alternatives
Ranks transfer, purchase-hold, return, bundling, discounting and waiting by their impact on liquidity, margin and service level.
Delivers: a processing plan ranked by financial impact
01 — Data
What data does Keeper need?
Keeper gathers the operational signals that actually affect the decision, while preserving the source and timestamp of each piece of information — it does not replace your system of record.
Reservations and confirmed orders
Quantities already allocated to customers or projects.
Minimum order quantity and supplier pack sizes
The constraints that determine whether purchase-hold is possible or how to adjust it.
Transfer cost and margin
To determine the impact of each option on liquidity and profitability.
Return and discount policy and target service level
The boundaries the company sets for each processing option.
Outcomes of past processing decisions
To improve the accuracy of future comparisons between alternatives.
On top of your current systems
What does Keeper add on top of your existing systems?
Your current systems keep records and transactions, and may offer advanced reports and analytics. Keeper does not replace or duplicate these capabilities; it links context across systems, gets ahead of exceptions, compares processing options, and ranks the decision by its financial and operational impact.
| Area | Current systems | What Keeper adds |
|---|---|---|
| Balance, movement and age | The system of record for data and transactions | Gathers context from multiple systems and sources |
| Slow and dead classification | Reports and analytics per system settings | Dynamic interpretation of reason, impact and confidence range |
| Transfers between locations | Creates and executes the transfer transaction | Determines where, when and how much to move, and compares transfer with alternatives |
| Excess processing | Supports transactions and reports | Compares alternatives and ranks them by impact |
| Follow-up | Saves the transaction | Measures the outcome and preserves the decision context |
Keeper starts with a read-only connection by default. Draft creation or transaction writing can be enabled through specific integrations, permissions, and approval workflows agreed with the company, and Keeper never executes any action outside the delegated and recorded boundaries.
02 — How it works
From data to an actionable decision.
Every recommendation follows a clear sequence your team can review: context, analysis, verification, then a proposed action with its reason and impact.
Full classification
Sorts the entire catalog into active, slow, dead, and at risk of write-off.
Measure the impact
Calculates the frozen value, holding cost and risk.
Compare alternatives
Transfer, purchase-hold, return, bundling, discount, or wait.
Processing plan
Ranks actions by their impact on liquidity, margin and service level.
03 — Output
This is what your team actually sees.
Instead of a long report or a chart with no decision, Keeper shows the priority, the number, the reason and the next step on a single screen. Illustrative example of the output below.
Keeper recommendation
Inventory portfolio — this week
Active inventorySAR 7.8M
Slow-movingSAR 2.4M
DeadSAR 640K
At risk of write-offSAR 180K
Why?
SAR 180K can be transferred to three branches with demand, while SAR 220K needs a processing plan within 45 days.
SAR 180K can be transferred to three branches with demand, while SAR 220K needs a processing plan within 45 days.
Every step stays linked to its source, timestamp and responsible user.
04 — Proof
Accuracy is shown, not asked for on blind trust.
Results are measured against your past and current data, and you see what worked, what needs improvement, and the confidence range of every recommendation.
Performance metrics (illustrative example)
Value of dead stock
SAR 640KInternal transfer opportunities
31 opportunitiesAnnual holding cost
SAR 164KSKUs recommended for purchase-hold
48 SKUs"The goal is not to label a SKU 'dead'; the goal is to choose the action that releases the most liquidity with the least impact on service level."
Keeper design principle
05 — Governance
Clear intelligence, control stays in your hands.
Keeper starts with a read-only connection by default, and additional permissions can be enabled within approval workflows the company defines. Every action waits for the authorized user's approval before sending or writing to the system.
By category
Slow and dead thresholds differ by SKU nature.
Seasonality impact
A seasonal SKU is never classified as dead before its season is understood.
Full history
The decision relies on movements and batches, not balance alone.
Human approval
Processing and transfer plans require the authorized manager's approval.
06 — Other capabilities
A team of agents working as one chain.
Each agent is independent in its task, but shares context and decisions with the rest of the team so departments don't work in silos.
Before you ask
The questions we hear most.
How does the agent tell a seasonal SKU apart from a genuinely dead one?
It compares each SKU's movement against its own historical pattern and seasons, not a single rule applied to the whole catalog, and shows the reason for the classification and its confidence range with every recommendation.
Does the agent execute discounts or liquidation without approval?
No. The agent presents processing options ranked by financial and operational impact, and approval of any action stays with the authorized user within your agreed approval workflows.
Our stock is spread across several branches and warehouses — does the agent distinguish between them?
Yes. It compares availability across branches, and the first recommendation is usually an internal transfer rather than a new purchase, because it is the fastest and least costly option.