The Lightspeed reorder workflow depends on your product series. In Retail R-Series, look for Reports → Reorder list. In Retail X-Series, inspect inventory reporting and the Replenishment view, with forecasting features dependent on your plan.
Check which series your store uses before following a tutorial. A reorder point, an R-Series desired level and an X-Series restock level do not mean the same thing.
R-Series: set the point and desired level
The R-Series reorder settings guide distinguishes the threshold for low stock from the desired quantity after replenishment. Set these on the item's Details or Reorder points page, reviewing each location.
Lightspeed's Need calculation considers current stock, incoming transfers, open purchase quantities and relevant box stock or box orders. The guide notes that assemblies are excluded and that negative on-hand quantities are treated as zero for this calculation. Check the source fields before treating a surprising Need value as a software error.
For an illustrative item below its reorder point, with five on hand, no incoming stock and a desired level of 20, the gap is 15. If another 12 units are already due, investigate that incoming order before buying the original gap again.
R-Series: run the report and inspect the result
Open Reports → Reorder list. Review the Needed, Reorder point, Desired level and quantity-on-hand information. The Comparison Location option helps you inspect stock at another shop before deciding between a transfer and an external purchase.
Use the result to prepare the relevant order, then review supplier, quantity, delivery location and purchase units. A calculated need is an input to a buying decision, not evidence that the supplier will deliver the requested pack or date.
R-Series also has a dynamic reorder report in Lightspeed Analytics. Its existence matters: describing every Lightspeed reorder option as a manually maintained threshold would overlook the available planning tools. Confirm the add-on and report configuration in your subscription.
X-Series: distinguish restock quantity from target stock
X-Series documents Reorder point and Restock level per outlet and variant. The point identifies low stock. The restock level is the default order amount when that item is added through the relevant reorder workflow; it is not the same as the R-Series desired post-receipt level.
For example, do not copy “target stock 20” into an order-amount field without checking what the draft will purchase. Test a known item and inspect the generated quantity. This catches a configuration error before a bulk import repeats it across the catalog.
X-Series: use demand forecasting where available
Lightspeed's current demand-forecasting guide describes Insights forecasting for Plus plans. In Reporting → Inventory reports → Replenishment, a forecast period and optional missed-sales adjustment inform the forecasted demand and suggested order quantity.
The documented suggested quantity subtracts closing and inbound inventory from forecast demand. Methods can use recent demand and seasonal history. The guide also explains that sparse sales history, new items and stockouts can affect the recommendation; inspect those conditions instead of assuming one model suits every SKU.
Use your supplier's lead time, delivery schedule, pack size and order minimum when reviewing the forecast horizon and final purchase. Confirm their actual treatment in the configured workflow. This guide does not infer that a capability is absent because one current help page does not describe it.
Review the order and receiving path
X-Series supports purchase-order creation and sending and partial receiving. Its receiving guide notes that the newer partially received order workflow is still rolling out across accounts. Test the available steps and how the outstanding balance is retained in your account, using the item you used for the report.
Use this worksheet when an order quantity looks wrong:
| Check | Evidence to inspect |
|---|---|
| Correct outlet and variant | Item and location identifiers |
| Correct field meaning | Desired stock level versus default order amount |
| Current stock and incoming orders | Actual balances and expected delivery dates |
| Forecast inputs | Time range, stockouts, seasonal history and new-item treatment |
| Purchase constraints | Supplier case size, minimum and cost basis |
| Receipt owner | One stock increase for the actual delivery |
If the supplier changes the shipment after sending, update the expected state and retain the confirmation. A report can inform the purchase; the team still needs to know what was accepted and what arrived.
When to evaluate another purchasing workflow
If native reporting, ordering and receiving cover your operation, keep them. If supplier changes repeatedly get lost between the buyer and stockroom, evaluate that coordination separately.
LineNow for Lightspeed connects supplier orders, reviewable email changes and receiving context. Demonstrate the supported Lightspeed series, item mapping and accounting path before relying on it. The Lightspeed purchasing guide also explains how NuORDER fits.
Sources and review
The linked Lightspeed documentation was reviewed September 23, 2026. These are documented workflows and illustrative checks, not measurements from a hands-on comparative trial.