OmniStock

What is OmniStock?

OmniStock is Omnium's inventory aggregation engine that determines which products should be shown as available for online purchase. It combines inventory from multiple physical warehouses and stores into a unified view of online availability per sales channel.

At its core, OmniStock answers: "Can this product be ordered online, and which warehouses can fulfill it?"

For each product, OmniStock evaluates:

• Which warehouses have stock for the product
• Whether the product is in the warehouse's assortment
• Whether the warehouse is allowed to ship the product (based on business rules)
• The aggregate stock level across all eligible warehouses

The result is stored on the product as two fields:

• OmniStock — a list of store IDs where the product is available for online purchase
• OmniStockLevels — stock level indicators (High/Low/Out of Stock) per store

Key Concepts

Store Roles

OmniStock uses two store roles to define the relationship between online sales channels and fulfillment locations:

An OmniStock store defines where products are sold online. A ShipFromStore defines where products are shipped from.

Warehouse Linking

Each OmniStock store has an AvailableWarehouses list that links it to one or more ShipFromStore locations. Each linked warehouse has a priority value used during order allocation to determine fulfillment preference.

┌─────────────────────────────────┐
│  OmniStock Store ("Webshop-NO") │
│  Role: OmniStock                │
│  AvailableWarehouses:           │
│    ├─ CentralWarehouse (pri: 1) │
│    ├─ Store-Oslo (pri: 2)       │
│    └─ Store-Bergen (pri: 3)     │
└─────────────────────────────────┘
         │          │          │
         ▼          ▼          ▼
   ┌──────────┐ ┌─────────┐ ┌──────────┐
   │ Central  │ │  Oslo   │ │  Bergen  │
   │Warehouse │ │  Store  │ │  Store   │
   │ Role:    │ │ Role:   │ │ Role:    │
   │ ShipFrom │ │ ShipFrom│ │ ShipFrom │
   │ Store    │ │ Store   │ │ Store    │
   └──────────┘ └─────────┘ └──────────┘

A product is considered available on the OmniStock store if at least one of the linked warehouses has stock and passes all business rules.

Stock Levels

OmniStock calculates a stock level per store per SKU (variant). The levels are determined by comparing aggregate available inventory against a configurable threshold:

The threshold is configured tenant-wide via the OmniStockLowInStockThreshold setting (default: 10 units). Available inventory is the sum across all eligible warehouses for that store.

How OmniStock Works

OmniStock runs as a scheduled background task that periodically evaluates all products and updates their online availability. The process follows these steps:

1. Identify Eligible Stores and Warehouses

The system loads all stores with the OmniStock role that have at least one linked warehouse, and builds a lookup map:

{
  "Webshop-NO": ["CentralWarehouse", "Store-Oslo", "Store-Bergen"],
  "Webshop-SE": ["CentralWarehouse", "Store-Stockholm"]
}

2. Evaluate Each Product

For each active product, the system evaluates every OmniStock store by checking its linked warehouses against a series of conditions:

1. Warehouse has ShipFromStore role — only warehouses with this role can fulfill orders
2. Product is in warehouse assortment — checked via the product's StoreIds list or category-based assortment rules on the warehouse
3. OmniStock rules are satisfied — business rules configured on the warehouse (see OmniStock Rules)
4. Inventory exists — at least one linked warehouse must have stock for the product (or one of its variants)

3. Update Product Availability

The product's OmniStock field is set to the list of OmniStock store IDs where the product passed all checks. The OmniStockLevels field is populated with per-store stock level indicators for each variant.

Delta vs Full Recalculation

The scheduled task uses two processing modes:

Store change detection: The system takes a snapshot of relevant store properties (roles, markets, linked warehouses, and OmniStock rules) and caches it. If the snapshot differs from the cached version on the next run, a full recalculation is triggered. This ensures that changes like adding a new warehouse or modifying exclusion rules are reflected across all products.

OmniStock Rules

OmniStock rules are business rules configured per warehouse (ShipFromStore) that control which products are eligible for online fulfillment from that location. Rules are optional — if no rules are configured on a warehouse, all products in its assortment with available inventory will be eligible.

Rules are configured on the store's OmniStockRules property.

Rule Properties

Rule Evaluation Order

Rules are evaluated in the following order. If any rule fails, the product is excluded from that warehouse:

1. Brand exclusion — Is the product's brand in the excluded list?
2. Season exclusion — Is the product's season in the excluded list?
3. Promotion exclusion — Is the product on an excluded active promotion?
4. Category inclusion/exclusion — Does the product satisfy category rules?
5. Product exclusion — Is the product explicitly excluded?
6. Profitability threshold — Does the product meet the minimum margin?

Configuring rules in the Omnium UI

Open the warehouse under Stores, then select the Online assortment rules tab. The tab requires administer access to stores. It edits the store's omniStockRules and saves them together with the rest of the store when you click Save store.

The header of each section shows the number of selected values. Rules that are left empty are ignored.

Saving new rules changes the store snapshot described in Delta vs Full Recalculation, so the next scheduled run re-evaluates every active product.

Example: Store API Configuration

When creating or updating a store via the API, OmniStock rules are set on the omniStockRules property:

{
  "id": "Store-Oslo",
  "name": "Oslo Store",
  "isWarehouse": true,
  "storeRoleIds": ["ShipFromStore"],
  "availableOnMarkets": ["NO"],
  "omniStockRules": {
    "excludedBrands": ["BrandX", "BrandY"],
    "excludedSeasons": ["SS2023"],
    "excludedPromotionIds": ["promo-clearance-2024"],
    "includedCategoryIds": ["clothing", "accessories"],
    "excludedCategoryIds": ["clothing-outlet"],
    "excludedProductIds": ["PROD-123", "PROD-456"],
    "profitabilityThreshold": 50.00,
    "currencyCode": "NOK"
  }
}

In this example, Store-Oslo will only ship products that:

• Are not from BrandX or BrandY
• Are not from the SS2023 season
• Are not on the clearance promotion
• Belong to clothing or accessories categories (but not clothing-outlet)
• Are not PROD-123 or PROD-456
• Have at least 50 NOK margin

On store PUT and PATCH, a missing or null omniStockRules leaves the existing rules unchanged. A value replaces the whole rule set. Send an empty object ("omniStockRules": {}) to remove all rules.

Where OmniStock Is Used

Product search

The SearchProducts endpoint and the product query endpoints accept isAvailableOnline. The store is taken from storeId on the search request, or from the first entry of storeIds on a query request:

POST /api/Products/SearchProducts
Content-Type: application/json
 
{
  "storeId": "Webshop-NO",
  "isAvailableOnline": true,
  "take": 50,
  "page": 1
}

Ship-from-store allocation

When an order is placed on a store with the OmniStock role and the shipment is a delivery, the same warehouse assortment and OmniStock rules gate reallocation of order lines to a ship-from-store warehouse. A line is only moved to a warehouse whose rules the product passes; inventory is checked separately by the allocation itself. Products that are not found in the catalogue are not restricted.

Configuration

Tenant Settings

Store Configuration

For OmniStock to work, stores must be configured with the correct roles and relationships:

OmniStock Store (Online Sales Channel)

ShipFromStore (Fulfillment Location)

Assortment Configuration

Products are matched to warehouses using assortment rules. Two approaches are supported:

1. Direct assignment: The product's StoreIds list explicitly includes the warehouse ID
2. Category-based rules: The warehouse's AssortmentIncludeProductCategoryIds and AssortmentExcludeProductCategoryIds control which product categories are in its assortment

If the product has a StoreIds list, only stores in that list are considered. Otherwise, the category-based rules on the warehouse are evaluated.

The category-based assortment is edited on the store's Assortment → Categories tab and is described in Store Categories. OmniStock rules on the Online assortment rules tab are applied on top of the assortment and never modify the products.

Product Data Model

OmniStock writes the following fields on each product:

Product.OmniStock

Type: List<string> (nullable)

A list of OmniStock store IDs where the product is available for online purchase. Set to null if the product is not available at any store.

Product.OmniStockLevels

Type: List<OmniStockLevel>

Per-store stock level indicators, set on each variant (or on the product itself if it has no variants).

{
  "omniStockLevels": [
    { "storeId": "Webshop-NO", "stockLevel": "HighInStock" },
    { "storeId": "Webshop-SE", "stockLevel": "LowInStock" }
  ]
}

Stock levels are set for all OmniStock stores, including those where the product is out of stock. This allows frontends to reliably check availability without needing to interpret a missing entry.

Setup Guide

Step 1: Configure Warehouses as ShipFromStore

For each warehouse or store that should fulfill online orders, ensure:

1. Set IsWarehouse to true
2. Add "ShipFromStore" to StoreRoleIds
3. Set AvailableOnMarkets to the relevant markets
4. Optionally configure OmniStockRules to control product eligibility

Step 2: Create OmniStock Stores

For each online sales channel, create a store with:

1. Add "OmniStock" to StoreRoleIds
2. Set AvailableWarehouses linking to the ShipFromStore locations, with priority values
3. Set AvailableOnMarkets to the markets this channel serves

Step 3: Configure Threshold

Set the OmniStockLowInStockThreshold in tenant settings to control the boundary between High and Low stock level indicators.

Step 4: Ensure Products Have Inventory

Products must have inventory records at the linked warehouses. Inventory is typically imported via the Inventory API.

Step 5: Verify

After the scheduled task runs, products should have OmniStock and OmniStockLevels populated. You can verify by querying products via the API and checking these fields.

Integration Scenarios

Scenario 1: Single Webshop with Multiple Warehouses

A retailer has one online store serving Norway, with a central warehouse and two stores that also fulfill online orders.

Configuration:

• Create warehouse stores: CentralWarehouse, Store-Oslo, Store-Bergen — all with ShipFromStore role
• Create OmniStock store: Webshop-NO with OmniStock role, linked to all three warehouses
• Set warehouse priorities: Central=1, Oslo=2, Bergen=3

Result: Products with stock at any of the three locations appear as available on the webshop. Order allocation uses priority to prefer the central warehouse.

Scenario 2: Multi-Market with Separate Channels

A retailer operates online stores in Norway and Sweden, each served by different warehouses.

Configuration:

• CentralWarehouse (ShipFromStore, markets: NO, SE)
• Store-Stockholm (ShipFromStore, market: SE)
• Webshop-NO (OmniStock, linked to: CentralWarehouse)
• Webshop-SE (OmniStock, linked to: CentralWarehouse, Store-Stockholm)

Result: Norwegian customers see availability based on central warehouse stock. Swedish customers see combined availability from both the central warehouse and Stockholm store.

Scenario 3: Selective Ship-from-Store with Rules

A retailer wants physical stores to fulfill online orders, but only for certain product categories and only when profitable.

Configuration:

• Physical stores have ShipFromStore role with OmniStockRules:
  • includedCategoryIds: ["clothing", "accessories"]
  • excludedBrands: ["PremiumBrand"] (only sold in-store)
  • profitabilityThreshold: 100
  • currencyCode: "NOK"

Result: Only clothing and accessories with at least 100 NOK margin (excluding PremiumBrand) will be available for ship-from-store fulfillment.

Troubleshooting

Product Not Showing as Available Online

1. Check store roles: Verify the OmniStock store has "OmniStock" in StoreRoleIds and linked warehouses have "ShipFromStore"
2. Check warehouse linking: Confirm the OmniStock store's AvailableWarehouses includes the correct warehouse codes
3. Check inventory: Verify the product has inventory records at the linked warehouses with quantity > 0
4. Check assortment: Confirm the product is in the warehouse's assortment (via StoreIds or category rules)
5. Check OmniStock rules: Review the warehouse's OmniStockRules — the product may be excluded by brand, season, category, promotion, or profitability threshold
6. Wait for scheduled task: OmniStock updates are processed by a background task. Changes may take a few minutes to reflect.

Product Available at Wrong Stores

1. Review the AvailableWarehouses configuration on each OmniStock store
2. Check that warehouse AvailableOnMarkets matches the intended markets
3. Verify assortment category rules are correctly configured on the warehouses

Stock Level Incorrect

1. Verify the OmniStockLowInStockThreshold tenant setting
2. Check that inventory is correctly reported at all linked warehouses
3. Remember that stock levels are aggregated across all eligible warehouses for each store

Full Recalculation Triggered Unexpectedly

A full recalculation runs when the system detects changes to any of the following on stores with ShipFromStore or OmniStock roles:

• Store role assignments
• Available markets
• Linked warehouses (codes or priorities)
• OmniStock rules (any field)

Review recent store configuration changes to identify the trigger.