Precedence: Global → Vendor → SKU
RevoStock lets you configure replenishment rules at three levels of specificity — catalog-wide, per vendor, and per individual SKU. This article explains how those layers stack on top of each other and how to predict exactly which value RevoStock will use for any given product.
The four configuration layers
RevoStock has four layers, from least specific to most specific:
| Layer | Where it lives | Who it affects |
|---|---|---|
| Factory | Built into RevoStock; not editable | Every SKU with no other config set |
| Global | Global Defaults tab | Every SKU in your catalog |
| Vendor | Vendor Overrides tab | Every SKU from a specific brand |
| SKU | SKU Overrides tab | A single product variant |
The Factory layer ships with sensible starting values so your buying table works on day one, even before you configure anything. You can think of it as a read-only fallback that is always there below everything else.
Resolution order: SKU wins, Factory is the last resort
For each replenishment field on each SKU, RevoStock evaluates the layers in this order and uses the first value that is not blank:
Resolved value = first non-blank value in: SKU → Vendor → Global → Factory
If a SKU override has a value, that value is used. If the SKU override is blank for that field, RevoStock checks the Vendor layer, then Global, and finally falls back to the Factory default. The process stops as soon as a non-blank value is found.
Fields are resolved independently
The resolution runs field by field, not rule by rule. A SKU can override only its Lead time while inheriting every other field from the Vendor or Global layer.
Example: Your Global default sets Lead time to 14 days and Days of supply to 30 days. You create a SKU override for a fragile import product that only changes Lead time to 45 days. RevoStock resolves that SKU as:
| Field | SKU override | Vendor override | Global default | Factory | Resolved |
|---|---|---|---|---|---|
| Lead time (days) | 45 | — | 14 | 14 | 45 (from SKU) |
| Days of supply (days) | — | — | 30 | 30 | 30 (from Global) |
| Safety stock (days) | — | — | 7 | 7 | 7 (from Global) |
| MOQ | — | — | 1 | 1 | 1 (from Global) |
You only had to set one field on the SKU override — the rest flow through automatically.
Why three editable layers exist
Most stores share one set of planning rules across the majority of products. A handful of product families or individual SKUs are exceptions:
- Global — set your store-wide baseline once. Changes here cascade to every SKU that has not been overridden.
- Vendor — override an entire brand's settings in one place. Useful when a particular supplier has a non-standard lead time or enforces a large MOQ across all their products.
- SKU — pin the exact settings for a single variant. Reserved for strategic items, clearance lines, or products with unusual replenishment requirements.
This hierarchy means you rarely need to touch individual SKUs. Most tuning happens at the Global or Vendor level, and exceptions are isolated without affecting the rest of your catalog.
The Source pill
Throughout the RevoStock interface you will see a small colored label — the Source pill — next to resolved field values. It tells you which layer provided that value:
- SKU — the value came from a SKU-level override you set.
- Vendor — the value came from a Vendor-level override.
- Global — the value came from your Global Defaults.
- Factory — no overrides exist at any layer; RevoStock is using its built-in default.
The Source pill appears in two places:
- The Live SKU Config tab, in the column for each field.
- The SKU detail drawer inside the Buying Table, under the "Configuration Governing This SKU" section.
If a field shows "Factory" and you want to change it, you do not need to create a SKU override — editing Global Defaults is usually sufficient and affects every SKU at once.
Where to find each tab
Open Replenishment Config from the left-hand navigation. The page has four tabs:
- Live SKU Config — read-only view of every SKU's resolved settings with Source pills.
- Global Defaults — edit the catalog-wide baseline.
- Vendor Overrides — create or edit rules scoped to a specific brand.
- SKU Overrides — create or edit rules scoped to a single variant.
When troubleshooting an unexpected reorder quantity or trigger date, start with the Live SKU Config tab. Find the SKU in question, and the Source pills will immediately tell you which layer is driving each value — no guessing required.