Never miss a
reorder again

Nuso calculates sales velocity by analysing your Shopify order data over configurable time windows — typically 7, 14, 30, 60 and 90 days. For each product and variant, the system divides total units sold by the number of days in the period to produce a daily sell-through rate. It then applies a weighted moving average that gives more importance to recent sales, so the velocity figure reacts to genuine trend changes (like a product going viral or a seasonal slowdown) without overreacting to a single quiet day. You can view velocity at the variant level, the product level, or aggregated across an entire Shopify collection.

A reorder point is the stock level at which you should place a new purchase order to avoid running out before the new shipment arrives. Nuso calculates it using the formula: reorder point = (daily velocity x supplier lead time) + safety stock buffer. For example, if a product sells 3 units per day, your supplier takes 14 days to deliver, and you want a 7-day safety buffer, the reorder point would be (3 x 14) + (3 x 7) = 63 units. When current stock drops below this level, Nuso flags the product with an "Order Now" alert and tells you exactly how many units to reorder to cover your target days of coverage.

Yes. Nuso allows you to configure lead times on a per-supplier basis. Each supplier profile stores a default lead time in days, and you can override it at the product level if certain SKUs from the same supplier have longer or shorter production cycles. When Nuso calculates reorder dates and suggested quantities, it automatically uses the correct lead time for each product's assigned supplier. This is particularly useful for brands that source from both domestic (7-14 day lead) and overseas (30-60 day lead) manufacturers, because a single global lead time would be far too inaccurate to be useful.

When you sell a bundle — such as a gift set that contains a tote bag, a scarf and a gift box — Nuso maps the bundle to its component SKUs and tracks inventory at the component level. The system identifies the "constraining SKU", which is the component that will run out first and therefore limits how many bundles you can actually sell. For example, if you have 18 tote bags, 42 scarves and 56 gift boxes, you can only assemble 18 more bundles, regardless of how much scarf stock you hold. All stockout forecasts, reorder alerts and velocity calculations for the bundle are driven by this constraining SKU, so you always know the real availability, not an inflated figure.

Nuso's weighted velocity calculation naturally adapts to demand changes because it gives more weight to recent sales. If a product starts selling faster in the run-up to Black Friday, the velocity figure adjusts within days. For more proactive planning, you can manually adjust the target days of coverage — for instance, increasing from 30 to 60 days before a peak period — so that suggested reorder quantities account for the expected demand surge. Nuso also allows you to compare velocity across different date ranges, so you can look at last year's peak season and use that data to inform this year's buying decisions.

When a product drops below its reorder point, Nuso marks it with a colour-coded status badge in the inventory dashboard: red for under 7 days of stock, amber for under 14 days, and green for 30 or more days of coverage. The product is also surfaced in the "Reorders Due" section at the top of the planner and included in the daily inventory digest email. You get the exact number of units to reorder, the date by which you need to place the order (factoring in supplier lead time), and an estimate of potential lost revenue if the product goes out of stock before the next shipment arrives.

Nuso generates suggested reorder quantities and allows you to export them as a CSV that can be imported into most purchase order or ERP systems. Direct API integrations with popular inventory management tools are on the roadmap. For now, the export includes product name, SKU, suggested quantity, supplier name and lead time — all the fields you need to create a purchase order in your existing system. The goal is to make Nuso the intelligence layer that tells you what to buy and when, while your existing tools handle the procurement workflow itself.