Skip to main content

​
Where Product Inventory Lives

Product inventory is reviewed from two places. The Inventory module shows the operating view across products and locations. The product detail page shows the product-specific view for one SKU, including thresholds, location balances, transactions, serials, bins, and related setup.
Inventory Overview page with KPI cards, balances table, location filter, available quantities, allocated quantities, on purchase order quantities, values, and alerts

​
Understand the Core Quantities

  • On hand: the physical quantity at a location.
  • Allocated: stock reserved for open orders or work that has not been fulfilled yet.
  • Available: stock that can still be promised. This is usually on hand minus allocated.
  • On PO: quantity expected from open purchase orders that has not been received yet.
  • Reorder point: the threshold that helps purchasing know when to buy more.
  • Value: inventory value based on stock quantity and cost history.
Use available stock for promises On-hand stock may already be committed to another order. Use Available when deciding whether a product can be sold, picked, packed, or promised to a customer.

​
Use The Product Inventory Tab For One SKU

The product detail Inventory tab is the best place to answer questions about one product. It has its own location filter, so support can review all locations or one location without changing the global header location used elsewhere in Arcus.
Product Inventory tab with all-locations scope, stock cards, run rates, Inventory by Location table, value column, and Recost action
  • All locations: use this to understand product-level availability, allocations, value, and demand pressure.
  • One location: use this when a warehouse, bin, pick, receive, or count question is location-specific.
  • Independent location scope: the product tab filter is separate from the global header location, so you can audit one product without changing the rest of the app.
  • Inventory by Location: compare on hand, allocated, available, on PO, reorder point, average value, and total value by location.
  • Run rates: compare recent daily demand over 30, 90, 180, and 365 days.
  • Transactions: audit the movements that changed this product, with filters for type, status, and location.
  • Active FIFO layers: review the remaining cost layers available for future outbound movement.
  • FBA breakdown: review marketplace fulfillment stock context when FBA quantities exist for the product.
Location scope changes the answer A product can be healthy in the all-location rollup and still be short in the warehouse that is trying to fulfill the order.

​
Read Supply And Demand On The Product

The product Inventory tab includes a product-specific Supply and Demand panel. Use it when a support case or planner asks whether the SKU is actually at risk, not just whether it has low stock today.
  • Available: current available quantity in the selected scope.
  • Current demand: open demand that still needs supply.
  • Blended daily demand: recent demand rate used for projection math.
  • Lead time: the buying or planning lead time used for the projection.
  • Days until stockout: the estimated time before available stock is exhausted.
  • Reorder quantity and reorder date: suggested buying guidance based on demand and thresholds.
  • Stockout risk: the risk label for the current projection. If Arcus says there is not enough data, treat the label as unknown instead of safe. The chart can show supply, demand, and reorder point over the selected horizon. If the panel shows a warning, retry state, or unknown-data message, document that context before escalating or changing reorder setup.
Do not treat a projection as a promise Supply and demand guidance depends on available stock, allocations, open purchase orders, demand history, lead time, and the selected location scope. Confirm the underlying orders, POs, and transactions before promising a date to a customer.

​
How Inventory Changes

Inventory should move through the workflow that matches the real-world event. That keeps stock, cost, purchasing, fulfillment, and accounting aligned.
  • Receive Inventory: add standalone stock when it is not tied to a purchase order.
  • Receive a PO: add stock from a purchase order and keep GRNI and vendor billing aligned.
  • Inventory Adjustment: correct a counted quantity, damage, loss, or setup issue with a reason.
  • Warehouse Transfer: move stock from one location to another without pretending it appeared or disappeared.
  • Fulfillment: consumes stock when orders are packed, shipped, or marked fulfilled.
  • Return processing: can bring stock back, send it to inspection, or dispose of it depending on disposition.
Inventory Transactions page showing movement history with type, product, location, quantity, balance before, balance after, source, and unit cost

​
Receiving and Cost Basis

Receiving creates stock and cost history. If stock is from a purchase order, receive it from the PO workflow. Use standalone receiving only when the stock truly is not tied to PO receiving.
Receive Inventory page with standalone receiving form, product, location, quantity, unit cost, reason, and PO guidance banner
Positive cost matters Receiving stock with a real unit cost gives FIFO layers and inventory value something reliable to work from. If the cost is wrong, fix the receiving source before relying on margin, COGS, or valuation.

​
Adjustments and Corrections

Use adjustments for counted corrections, damaged stock, lost stock, setup cleanup, or other inventory corrections. The adjustment reason and notes should explain why the quantity changed.
Inventory Adjustments page with product, location, counted quantity, unit cost, reason, notes, warning controls, and recent adjustments
Do not use adjustments to bypass a workflow If stock changed because of a purchase order, transfer, fulfillment, or return, use that workflow instead of manually adjusting the balance. Manual adjustments are for corrections, not shortcuts.

​
FIFO Cost History

Arcus uses FIFO cost behavior for inventory valuation. Receiving creates cost layers. Fulfillment and other outbound movements consume the oldest eligible cost layers first. That gives accounting a traceable cost basis for inventory value and cost of goods sold.
FIFO Layer Detail modal showing a consumed cost layer, layer date, quantity used, balance before and after, unit cost, layer cost, and warning
Cost warnings deserve review If Arcus shows a cost mismatch or negative value warning, review receiving, adjustments, and cost history before posting more corrections.

​
Fix Negative Product Value Safely

A negative value warning means the balance value for a product or location needs review. Use the product Inventory tab to decide whether the source workflow is wrong or whether the balance row should be recomputed from the FIFO ledger.
  1. Open the product detail page.
  2. Open Inventory.
  3. Check whether the warning is on all locations or one location.
  4. Review recent receives, adjustments, fulfillment, returns, and manufacturing consumption.
  5. Open FIFO layer detail for outbound transactions when cost consumption looks suspicious.
  6. Correct bad source records when the receipt, adjustment, or purchase cost is wrong.
  7. Use Recost only when the ledger is right but the balance row is stale.
Recost does not make bad source costs good Recost refreshes the balance value from FIFO history. If the receipt or adjustment entered the wrong cost, fix that source workflow first.

​
Planning Reorders

Inventory settings and demand signals feed purchasing work. Reorder points, safety stock, open purchase orders, and demand pressure help operators decide what to buy and when.
Supply and Demand page with stockout signals, available quantity, safety stock, reorder point, on purchase order, suggested reorder quantity, and status
Use the product tab first when the question is about one SKU. Use the Inventory module when you need to compare many products, many locations, or all low-stock work at once.

​
Common Blocks

  • Available is lower than expected: stock may be allocated to open orders.
  • On PO does not match expectation: review open purchase orders and what has already been received.
  • Supply and Demand says not enough data: review transactions, recent demand, open POs, and lead time before treating the product as low risk.
  • Wrong warehouse appears on the product tab: check the product Inventory tab location dropdown. It is intentionally separate from the global header location.
  • Value looks wrong: review recent receiving, adjustments, and FIFO layer detail before posting a shortcut correction.
  • Recost is missing: the row may not have negative value, or your role may not allow inventory adjustments.
  • Adjustment is blocked: the counted quantity, unit cost, reason, or permission may be missing.
  • Receiving is blocked: product, location, quantity, unit cost, or PO guidance may need review.
  • Product cannot be fulfilled: stock, serials, bins, kit components, payment holds, or approval holds may be blocking fulfillment.

Inventory Overview

Monitor stock health, location balances, low-stock alerts, and inventory value warnings.

Inventory Transactions

Audit stock movement history, movement types, supply and demand rows, and FIFO layer detail.

Receive Inventory

Receive standalone stock, choose the right PO receiving path, and protect FIFO cost basis.

Inventory Adjustments

Correct counted stock, choose adjustment reasons, handle unit cost, and review negative-stock warnings.

Supply & Demand

Review stockout pressure, demand signals, reorder timing, safety stock, and suggested reorder quantity.

Product Setup

Create physical products, services, and product records.

Product Types and Costing

Understand product type conversion rules, FIFO layers, product value, and Recost repair behavior.