> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stockful.app/llms.txt
> Use this file to discover all available pages before exploring further.
# SKU overrides
> Per-variant lead time, safety stock, thresholds and manual sales rates
Not every product has the same supply chain. From **Settings → Forecasting**, click **SKU overrides** to customise settings per variant.
Each variant can override:
| Override | What it does |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Lead time** | Supplier-specific lead time for this SKU |
| **Safety stock** | Custom buffer for high-value or volatile items |
| **Low stock threshold (days)** | Override the global days-of-cover low-stock threshold for this SKU |
| **Restock-to days** | Custom restock target for this SKU |
| **Demand adjustment** | SKU-specific seasonal or promotional adjustment |
| **Reorder policy** | Whether this SKU is replenished from the **forecast** (the default) or from a **min/max** rule you set yourself. |
| **Minimum** | Under min/max, the stock level that triggers a reorder. Only editable once the policy is set to min/max. |
| **Maximum** | Under min/max, the level you want topped back up to. Only editable once the policy is set to min/max. |
| **Order on demand** | Whether this SKU is bought against the orders already taken, with no forecast, safety stock or target stock level. **Follows shop setting** defers to the switch in Settings, then Forecasting, which reads Shopify's continue-selling setting. **On** and **Off** decide it for this SKU whatever the shop is set to. |
| **Manual sales rate** | Pin a fixed daily sales rate (units/day) for this SKU. When set, it replaces the calculated velocity and any demand adjustment, and the SKU is projected at that flat rate, so its days of supply, reorder point and reorder quantity all follow it. Use it for a new product or a known upcoming change the sales history can't show yet. |
Leave a field blank to inherit the global default; leave **Manual sales rate** blank to use Stockful's calculated velocity. A blank field means the SKU uses the default, not an override you have set.
You can search by product name or SKU, filter by **Order on demand** to see which SKUs are set explicitly and which still follow the shop setting, and reset individual overrides back to defaults.
One per-variant setting lives only on the inventory detail page, not in this grid: **Forecast basis**, which lets a brand-new product borrow its forecast from a similar one. See [new products](/user-guide/forecasting/new-products).
## Minimum and maximum stock levels
Some products don't want forecasting. A slow but critical spare, a safety item, a line you simply always keep ten of: for those, set the numbers yourself.
Switch a SKU's **Reorder policy** to **Min/max** and fill in a **Minimum** and a **Maximum**. From then on, Stockful ignores the forecast for that SKU and follows your rule instead:
* It's flagged for reorder when stock drops to or below the **minimum**
* The suggested quantity is whatever brings it back up to the **maximum**
* Incoming stock and units already on an open purchase order are still netted out, so you're never told to order twice
Min/max applies **at every tracked location**. A minimum of 10 across four locations means each of them is kept at 10, not 10 across the business.
Because there's no forecast involved, none of the demand-based settings apply to a min/max SKU: lead time, safety stock, restock-to days, demand adjustment and the sales rate are all bypassed. The numbers you typed are the whole rule.
This is also the one policy that surfaces products with **no recent sales at all**. A SKU that hasn't sold in months is invisible to a forecast, but if you've told Stockful to keep ten on the shelf, it will say so the moment you have nine.
Both fields are required once the policy is set to min/max, and the maximum has to be at or above the minimum. A SKU can't be on min/max and **Order on demand** at the same time, as both replace the reorder calculation.
You can set the policy here, on a single product from its inventory detail page, or in bulk by [importing a CSV](#importing-overrides). SKUs on a min/max rule are marked on [reorder recommendations](/user-guide/purchasing/reorder-recommendations), where the badge also shows what the forecast would have suggested, so you can see the two side by side.
Coming from Stocky and used to setting min and max per product? This is the same idea. See [migrating from Stocky](/user-guide/purchasing/migrating-from-stocky).
## Exporting your overrides
**Export** downloads your per-SKU settings as a **CSV** or **Excel** file. Choose what goes in it:
| Scope | What you get |
| ------------------------------------ | ------------------------------------------------------- |
| **This page** | Just the rows on screen |
| **All SKUs** | Every variant, ignoring your current search and filters |
| **Selected** | The rows you've ticked |
| **All matching the current filters** | Everything your search and filters currently match |
**Selected** and **All matching the current filters** are only available when you've actually ticked rows or applied a filter.
The file is generated on the server and streamed straight to your browser, so a large catalogue doesn't need to be loaded into the page first.
## Importing overrides
**Import** takes a CSV back in, which is the fastest way to set values across hundreds of SKUs at once. **Download a template** from the import window if you'd rather start from a blank one, or export what you have, edit it, and import the same file back.
Rows are matched on **variant ID**, **SKU** or **barcode**. You only need one of the three filled in per row, and an exported file already has all three.
**A blank cell leaves that setting alone.** It does not clear it. To clear a setting, put a dash (`-`) in the cell.
That rule is what makes the round trip safe: export fifteen columns, change one, import it back, and the other fourteen are untouched.
Before anything is written you get a preview of every row and what will happen to it:
| Status | Meaning |
| ------------------------- | ------------------------------------------------------------------------- |
| **Will update** | The row matched and has changes to apply |
| **Not found** | No variant matches that ID, SKU or barcode |
| **Matches more than one** | The identifier is ambiguous, so the row is skipped rather than guessed at |
| **Not tracked** | The variant is excluded or not tracked by Stockful |
| **Already in this file** | An earlier row already matched the same variant |
| **Nothing to change** | Every cell in the row was blank |
| **Could not read** | A cell couldn't be understood, and the column is named |
Only **Will update** rows are applied. Everything else is skipped and left exactly as it was.
Recommendations recalculate after an import, so it takes a few minutes for the new numbers to appear on [reorder recommendations](/user-guide/purchasing/reorder-recommendations).
## AI-suggested thresholds
On the SKU overrides page, click **Suggest with AI** to have Stockful's assistant recommend values for lead time, safety stock, low-stock threshold, and restock-to days. Suggestions are based on each SKU's actual sales history, variability, and supplier link. Each suggested field comes with a one-sentence explanation; you can apply suggestions individually or all at once. Bulk mode runs across many selected SKUs; the same suggestion is also available in the inventory detail modal for single-SKU tuning.