Put one or more prices to a product in Omnium. Will overwrite existing price if found, or add a new price if no match is found. The price is identified by checking CustomerId, CustomerGroup, VariantId, MarketId, MarketGroupId, CurrencyCode, SalesCode, PromotionId, StoreId, and PriceListId. If IgnoreDates is false, dates are also considered when fetching existing prices. <br />By default (PricesMergeMode = Replace) a matched price is overwritten in full, so fields you do not send are reset to their defaults. Set PricesMergeMode to AddOrUpdate or UpdateOnly to only apply the fields you send and keep the existing values for the rest. See OmniumPriceUpdateRequest.PricesMergeMode for details. <br /><br />ProductId can be omitted when every price in the request carries the SKU in its Code property - Omnium then resolves the product from the SKU. This is intended for source systems that only know the SKU. SKUs that match no product (UnresolvedCodes) or more than one product (AmbiguousCodes) are skipped and returned in the response; the rest of the request is still applied.

Sample request using SKU only (no ProductId). Use this when the source system does not know Omnium's ProductId. Each price is matched to its variant by "code", so sizes/colours can have different prices:

PUT /api/prices/AddMany
[
  {
    "prices": [
      { "code": "SKU-SHIRT-S", "unitPrice": 199, "currencyCode": "NOK", "marketId": "NOR", "validFrom": "2026-01-01T00:00:00Z" },
      { "code": "SKU-SHIRT-L", "unitPrice": 249, "currencyCode": "NOK", "marketId": "NOR", "validFrom": "2026-01-01T00:00:00Z" }
    ]
  }
]
        

The SKUs above may belong to different products - Omnium groups them per product on its own. Response:

{
  "updatedProductCount": 1,
  "unresolvedCodes": null,
  "ambiguousCodes": null
}
        

Sample request using ProductId (unchanged behaviour). "code" still selects the variant, and omitting it puts the price on product level:

PUT /api/prices/AddMany
[
  {
    "productId": "P-12345",
    "ignoreDates": true,
    "prices": [
      { "code": "SKU-SHIRT-S", "unitPrice": 199, "currencyCode": "NOK", "marketId": "NOR" }
    ]
  }
]
        

Sample response when some SKUs could not be used. The prices for these SKUs were NOT applied, everything else in the request was. "unresolvedCodes" means the SKU does not exist in Omnium; "ambiguousCodes" means it exists under several products, so send ProductId for those:

{
  "updatedProductCount": 42,
  "unresolvedCodes": ["SKU-DISCONTINUED"],
  "ambiguousCodes": ["SKU-DUPLICATED"]
}
        

NB! Sending the SKU in "productId" does not work - the price would be silently ignored. Either leave "productId" out entirely and set "code" on every price, or send the real ProductId.