Skip to main content

Bulk update SKU overrides

Editing SKU settings one row at a time is slow when you have 500 SKUs. Use Bulk edit to give many SKUs the same value, or a CSV when each SKU needs its own value.

If every SKU from one supplier needs the same lead time or MOQ, set it once on the Supplier Overrides tab instead. Use SKU overrides for the exceptions.

Both ways only change SKU overrides. Supplier settings, Global Defaults and your Shopify catalog stay as they are.

  • Same value for many SKUs — tick the SKUs, then Bulk edit.
  • Different value per SKU — Download CSV, edit it in your spreadsheet, then Upload CSV.
  • Nothing saves by surprise — you always see a preview first. One error stops the whole batch, so you never get half a save.

Where to find it​

  • From the Dashboard — click Configure replenishment. It opens the SKU Overrides tab.
  • From the menu — open Supply Planning → Replenishment Config, then select the SKU Overrides tab.

You need the Owner or Admin role to save changes. Members can still download the CSV.

Select SKUs​

  • Search and filter — search by product, SKU or supplier. Filter by Supplier (or Unmapped) and by Has overrides.
  • Tick rows — use the checkbox on each row.
  • Select page — ticks every SKU on the current page.
  • Select all matching — ticks every SKU that matches your search and filters, on every page. The count shows exactly how many.

Your ticks stay when you change pages. They clear when you change the search or filters, and RevoStock tells you when that happens.

Option 1 · Bulk edit​

  1. Tick the SKUs and click Bulk edit.
  2. For each field, choose one of three options:
    • Leave unchanged — every SKU keeps its own value. This is where every field starts.
    • Set value — every selected SKU gets this value as its override.
    • Use inherited — removes the SKU override. The SKU follows its supplier, then Global Defaults.
  3. Click Review changes and check the preview.
  4. Click Apply changes.

Back from the preview keeps everything you entered.

tip

Set value creates an override even when the value matches what the SKU inherits today. Later supplier or Global changes will not reach that field. Use Use inherited when you want the SKU to follow its supplier again.

Option 2 · CSV round trip​

  1. Click Download CSV. Choose Selected SKUs or All SKUs matching your search and filters. The file name shows which one you picked.
  2. Edit the setting columns in your spreadsheet:
What you typeWhat happens
A whole number, e.g. 21Sets the SKU override. 0 is a real value.
INHERITRemoves the SKU override. The SKU follows its supplier, then Global.
Leave the cell blankNo change.
  1. Click Upload CSV, choose your file, and check the preview.
  2. Click Apply changes.

Rules for the file:

  • Keep the Variant ID column — it picks the SKU. Without it, RevoStock uses the SKU code, but only when exactly one variant has that exact code (capital letters matter).
  • Keep the Baseline column — it records each SKU's settings when you downloaded. If someone changed a SKU after that, RevoStock stops that row instead of overwriting the newer settings. Download a fresh file and redo the edit.
  • Download a fresh file after 30 days — older baselines are refused.
  • Trigger mode takes SmartDays, ManualQty, Hybrid or Disabled.
  • Product, Variant, Supplier and Effective columns are for reference — RevoStock never saves them. Effective columns show what each SKU uses today and where the value comes from.
  • Rows you delete stay as they are. Upload only the rows you are changing if you like.
  • Uploading an unchanged file saves nothing and shows No changes.

Save the file as UTF-8 CSV. The upload limit is shown on the upload screen.

tip

Format the Variant ID column as text. If your spreadsheet turns an ID into a number like 4.40123E+13, RevoStock will ask you to copy it from a fresh download.

Reading the preview​

The preview shows four counts — New overrides, Updated, Unchanged and Rows with errors — and every field that changes:

  • SKU override — the stored value before and after. "Inherited" means no override.
  • Effective value — what the SKU will actually use, and which layer it comes from (SKU, Supplier or Global).

RevoStock blocks the whole batch when it finds an error, and shows the row, field, reason and fix. Click Download errors for the full list, fix your file, then Replace CSV. Common errors:

  • Not a whole number — negatives, decimals like 2.5, and text like 10 days are refused. RevoStock never rounds or guesses.
  • Manual Qty or Hybrid without a static reorder point — set one on the SKU, its supplier or Global Defaults. 0 is allowed.
  • Unknown Variant ID — the variant is not in your synced catalog, or the ID belongs to another store.

Some things are warnings, not errors. You must tick I've reviewed these warnings before you can apply:

  • MOQ above the max quantity cap — RevoStock never orders past the cap, so orders for that SKU can come in below the MOQ.
  • SKU code changed in the file — RevoStock matches the row by Variant ID and does not rename the SKU.

Two behaviours to know​

  • Clearing the max quantity cap does not mean "no limit". It means the SKU uses its supplier's or Global cap. To remove a limit everywhere, clear it at every layer.
  • Changing the trigger mode keeps the static reorder point. In Smart Days or Disabled it shows as inactive. It works again if you switch back to Manual Qty or Hybrid.

After you apply​

  • Your settings save together — all of them, or none if something changed while saving.
  • Live SKU Config updates right away — check the Source pills there.
  • Restock suggestions update after the next sync — the result screen says Settings saved — planning needs recalculation. Click Sync now, or Recalculate now on the Dashboard.

A sync that was already running when you saved does not include your changes. RevoStock waits for it to finish, then offers another sync. If a sync fails, your settings stay saved — just run the sync again. See Re-syncing after configuration changes.

There is no undo. To change a SKU back, edit it again or set its fields to Use inherited.

Next step: open SKU Overrides, tick the SKUs that need an exception, and click Bulk edit.