Prices

Introduction

This guide explains how prices work in Omnium, including how they are structured, stored, and retrieved. It covers price levels, ID generation, and options for managing large price sets. You will also find details on using external price services and handling market-specific pricing.

Product Prices

Price Levels

Prices can be set at two levels:

1. Product-level (ProductId)
2. Variant-level (SKU)

If prices are identical, it's recommended to use product-level prices for better performance. Use both levels only if variants require unique pricing.

Price ID Generation

Price IDs follow this convention:

{CustomerId}_{CustomerGroup}_{VariantId}_{MarketId}_{MarketGroupId}_{CurrencyCode}_{SalesCode}_{PromotionId}_{StoreId}_{PriceListId}_{ValidUntil}_{ValidFrom}

Override this convention using an ExternalId for prices fetched from external systems.

Key Features

• Market-Specific Prices: Prices can also be specific to customers, groups, or stores.
• External Promotion Support: Use IsExternalPromotion for prices tied to external systems.
• Flexible Date Handling: Use null for dates if no validity range is required.

Separate Prices

For products with 50+ prices, prices can be stored separately to improve update performance. Use dedicated price search endpoints to retrieve these.

The separate prices setting can be found in config -> products -> prices "storage options" -> separate prices.

External Price Service

Configure external services to fetch prices if needed, but note that slow external services may impact product search performance.