LineNow supports Forecast & Reorder and configured replenishment that can stage items in a cart. The operator reviews the buying plan and sends the purchase order. Customer-order-driven dropshipping is a separate workflow whose routing and dispatch settings must be validated during setup.
The useful evaluation is the complete path from alert to receipt: why the item needs attention, how the quantity was calculated, what is already incoming, and who approves the purchase.
What the alert shows
The Forecast & Reorder view includes current stock context, usage per day, a recommended quantity, restock cost, incoming quantities and a planning horizon. It also shows an estimate of revenue at risk.
The revenue estimate uses a recent daily sales rate multiplied by the days in the selected horizon that are not covered by estimated stock. In simplified form:
days at risk = max(0, planning horizon − estimated days covered)
revenue at risk = recent daily sales revenue × days at risk
For an illustrative $80 daily sales rate, a seven-day horizon and four days of cover, the estimate is $80 × 3 = $240. It is exposure under those assumptions, not a forecast of guaranteed lost sales or profit. Customers may substitute or wait, and several ingredients can contribute to the same finished sale, so avoid treating overlapping item exposures as independent revenue losses.
Use the number to compare attention, then review supplier timing and criticality. A low-price ingredient can stop a high-value recipe even when its direct sales history is limited.
Check the quantity before adding it to the cart
Recommendations depend on stock and usage data, configured planning settings and supplier constraints. Validate opening counts, item mappings and pack units first. Recipe sales estimate ingredient use only after the recipes and yields are mapped.
Incoming stock should remain visible separately from usable on-hand stock. Check its expected arrival and unresolved changes before placing another order. An incoming-quantity column alone does not prove the receipt will cover the shortage in time.
For perishables, a statistical planning loss is different from an expiry or safety decision. Use valid lot information and receiving/count procedures. Do not increase an order solely to cover modeled decay if the quantity cannot be used while acceptable.
Automatic cart preparation keeps a review point
Configured replenishment can add an item when its trigger is met. This removes the repeated cart-building step for suitable items. It does not remove responsibility for quantity, supplier, budget or final sending.
In the five ordering workflows, the demo distinguishes manual buying, inventory recommendations, automatic cart building, AI-assisted carts and dropship POs. Choose the path that matches the actual order.
For stocked replenishment, demonstrate the trigger and review point before relying on it. Do not assume an automatic draft means a scheduled autonomous purchase has been authorized. For dropshipping, test supplier/location mappings, custom fields, ship-to addresses, duplicate handling and cancellation changes separately.
The alert is not resolved when a PO is drafted
A draft has not reached the supplier. A sent order is not a supplier commitment. A commitment is not a receipt.
Track the supplier's confirmation and accepted changes on the living PO. If the supplier confirms only part of the order, the buyer must decide how to handle the remaining need. Receiving records the actual accepted quantity and feeds the next planning cycle.
The finance handoff then carries the PO, accepted changes, receipt and invoice context, with account mappings and review controls. A stock alert does not authorize a bill or payment.
A useful trial
Start with a small set of items: a steady seller, an intermittent item, a perishable if relevant, and one item with a partial incoming order. Check each recommendation against the source data.
Have a second operator review the cart, process a changed supplier reply and receive a short delivery. Measure review time per order line, duplicate orders, unresolved balances and stock availability over comparable periods.
Native POS alerts may already be sufficient for a simple workflow. LineNow inventory management is worth evaluating when the team also needs the supplier-order and receiving handoffs connected. The acceptance test should demonstrate that added work, not merely another low-stock notification.