What stock is usable now?
Start with on hand minus valid reservations and unusable stock. Reconcile movements and counts before trusting the answer.
Separate current stock, replenishment calculations, source choices and fulfilment, then connect the records so each team knows what to do next.
This guide uses fixed reorder-point and min-max examples. Forecasting, optimization, ERP, purchasing and warehouse execution can remain in specialist systems where they are stronger.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to preview populated sample records. Install your own copy before adding operational inventory data or access rules.
Most replenishment problems become confusing because balance, forecast, decision and execution are treated as one thing.
Start with on hand minus valid reservations and unusable stock. Reconcile movements and counts before trusting the answer.
Use a transparent trigger: fixed reorder point, min-max rule, planning-system recommendation or an explicit exception.
Choose buy, transfer, make, defer, investigate or no action based on source availability, lead time, constraints and authority.
Close only after usable stock is received or the reason for no action is accepted. Partial, late and rejected supply stays visible.
Simple rules can be useful when data and ownership are clear. They should be inspectable, revisable and never misrepresented as an advanced forecast.
Review when the effective stock position reaches the trigger. A common planning concept is demand during lead time plus safety stock, but the approved formula should match your operation.
When the position falls below the minimum, suggest enough to reach the maximum, then round for pack size, order minimum or transport constraint.
Define whether your rule uses on hand, available, open supply, backorders, approved demand or transfers in transit. Inconsistent definitions produce duplicate or late orders.
Show the raw quantity and rounded quantity separately. This lets a reviewer see how supplier packaging or economic constraints changed the action.
A clear boundary avoids duplicated quantities and competing recommendations.
| Layer | Authoritative record | Typical output | Jodoo role |
|---|---|---|---|
| Stock execution | Inventory system or WMS | Posted movements and current balance | Capture or integrate movements; coordinate review |
| Forecast | Planning or forecasting engine | Demand forecast and planning scenario | Import the approved input and retain its source |
| Replenishment decision | Policy and accountable reviewer | Quantity, source and needed-by date | Calculate simple rules or coordinate imported recommendations |
| Purchasing | ERP or procurement system | Approved order and supplier commitment | Create and follow the requisition or reference |
| Receipt and exception | Receiving and quality records | Accepted quantity and unresolved shortage | Coordinate partial, late, rejected and corrective actions |
A small, accountable pilot creates better evidence than turning on automatic ordering across an unreliable catalogue.
Use meaningful demand, known ownership and enough transactions to expose the real exceptions.
Align item codes, units, locations, bins, states and the movement types that change stock.
Agree on the stock position, threshold, target, lead time, safety stock and rounding rule.
Name who can buy, transfer, defer or investigate and what evidence is required.
Run a partial receipt, late supply, rejection, transfer discrepancy, stale demand and retired item before expanding.
The terms overlap in search results, but the buying jobs differ.
Stock control proves the current position. Replenishment decides when, how much and from where to source.
A threshold may use demand and lead-time assumptions, but it does not provide statistical forecast quality or scenario optimization.
An approved recommendation has not increased stock. The purchase, transfer, receipt and exception records must confirm the outcome.
Teams often have stock data in one system and the real decision in spreadsheets, chat or email. Jodoo can make that operating layer structured and changeable.
A business team can build or revise this operating layer in hours without claiming that Jodoo replaces every ERP, WMS or planning algorithm.Add fields and paths for substitute items, internal transfer, partial receipts, quality holds or local approval thresholds.
Link the recommendation to the request, transfer, receipt, count or external document that proves the outcome.
Show work by risk, due date, next action and unresolved condition—not only an aggregate stock chart.
It begins with a reliable stock position, applies a policy or planning input, reviews quantity and source, creates a purchase or transfer action, confirms receipt and resolves shortages or rejections.
A common starting concept is expected demand during lead time plus safety stock. Your approved formula must define demand source, lead time, service objective, units and review frequency.
A reorder point defines when review begins. A min-max policy also defines the target level used to calculate how much to replenish.
Usually open supply belongs in the effective position, but only if it is current, approved and expected in time. Late or disputed supply may need separate treatment.
Use it when seasonality, promotions, intermittent demand, service-level optimization or multi-location planning require statistical methods beyond transparent fixed rules.
Open the populated records, replace the sample assumptions with your policy and test exceptions before increasing automation.
Open the working example