Last updated

Introducing Norce Commerce

Norce Commerce is a composable, API-first commerce and PIM platform, delivered as true SaaS on Azure. It serves both B2B and B2C businesses from a single commerce engine and unified product catalog, and is built to fit into an existing system landscape rather than replace it — Norce is often a central component that integrates with your ERP, CMS, search, payment, and shipping services through open, documented APIs.

Norce Commerce inherits the best from both Norce [Storm] and Norce [Jetshop]: the rich functionality, service architecture and composability from Norce [Storm], combined with the cloud-native infrastructure, security and robustness from Norce [Jetshop], with a 5-9 availability.

Main capabilities

Product information management (PIM)

Norce Commerce has a built-in PIM that is feature-rich enough to be offered as a standalone product, and is designed to handle large assortments — from hundreds of thousands to millions of products.

  • An open product model you can tailor to your assortment, with attributes (parametrics) in data types such as text, numbers, HTML and lists.
  • Variants on any attribute and in any number of dimensions (for example size, color, or packaging).
  • Texts and translations with side-by-side editing and Google Translate assistance to reach new markets quickly.
  • Images and files per product or variant, organized by category with drag-and-drop ordering.
  • Relations (up-sell, cross-sell, spare parts, series) and bundles to increase sales.
  • Flags to categorize and merchandise products, such as "new arrivals" or "popular".

Pricing and promotions

Norce Commerce can act as the master of prices or receive them from your ERP, and is built to handle thousands of price lists if needed.

  • Customer-specific prices and assortments, mirrored from an ERP or set up directly in Norce.
  • Cost-based pricing methods that calculate sales prices from purchase cost to protect margins.
  • Quantity breaks (volume-based pricing) set per price list.
  • Campaigns that define an assortment (by categories, manufacturers or flags) and granular pricing rules per subset.
  • Promotions that trigger in the cart based on requirements — for example three-for-two, free shipping, or a percentage off with a discount code.

Checkout and orders

Norce Commerce handles the entire checkout journey — from basket management through shipping and payment to finalizing the order and handing it to the ERP.

  • Find and follow carts and orders by date, status, products, promotions, shipping or payment method.
  • Follow the full payment process, which helps when something doesn't go according to plan.
  • Adapter-based integrations to leading payment providers such as Klarna, Walley, Svea, Adyen and Qliro.

Customers and companies (B2B)

Norce Commerce holds basic data — names, payment and delivery addresses — for both customers and the companies they belong to, and lets you attach any additional variable or flag for a tailored experience.

  • Customer-specific prices and assortments by tying price lists to a customer or company.
  • Additional discounts applied on top of agreed prices, per category or flag.
  • Company hierarchies and roles, so, for example, many individuals can create orders while only certain managers approve them — enabled by the headless architecture and tailored in the frontend.
  • Support for per-customer portals, invoice customers, and multiple users per account.

Delivery

The delivery engine is easy to configure and supports multiple delivery methods for the customer to choose from.

  • Suggest or filter methods based on logistical data such as weight and measurements.
  • Restrict methods by ZIP code, product type, or payment method.
  • Set delivery methods per market when selling internationally.

One platform for B2B and B2C

Norce supports both B2B and B2C customers on the same platform, with a single commerce engine and unified product catalog, including multi-brand support. It is built for international sales across multiple cultures, currencies and countries, with VAT handling per market. Its headless approach lets you integrate any CMS, search service or other components you need, and it can share your product data and prices with resellers, marketplaces and search engines.

APIs and components

Norce Commerce is made up of several APIs and components for different purposes:

  • Norce Commerce Services — for your shopping site or apps (product, order, shopping, customer and metadata services).
  • Norce Commerce Connect — for ERP and other system integrations, such as importing products, prices and inventory.
  • Norce Commerce Query — for retrieving data directly from Norce's data layer, for example product feeds and other data for external use.
  • Norce Commerce Event — for subscribing to events via webhooks, primarily used by the integration layer.
  • Norce Commerce Product Feed — for pushing product data to channels like marketplaces, Google, or customers.
  • Managed adapters — pre-built integrations to other systems, most commonly PSP (payment) adapters.
  • Norce Admin UI — the management tools to manage and monitor your data and processes.

For AI and agentic applications, Norce also provides the Norce Commerce MCP Server.

See the solution architecture for how these components fit together in a typical solution, or the developer portal to start building.

Built on Azure

Norce hosts its SaaS solution in the cloud on Azure-native technologies such as Azure Kubernetes Service, Azure SQL and Azure Cosmos, primarily in Sweden Central, with the option of single-tenant environments worldwide. Authentication uses OAuth2. Read more about the infrastructure.

Coming from Norce [Storm] or Norce [Jetshop]?

If you are upgrading from an existing Norce product, most features carry over, though some names and behaviors have changed.

Most features are included from Norce [Storm] to Norce Commerce, except the obsolete and legacy features and services, which are removed completely. Some functionality has changed to take the new infrastructure into account — for example Norce Commerce Event, which uses webhooks instead of Azure Service Bus. See the upgrade guide for the full list of changes.

For Norce [Jetshop] users and customers there are more differences, since the new product's feature-set is built on top of a whole different product. Most features you have in the Jetshop platform are there, and might even be more advanced, but it might need some time getting used to. Check out our coming training and tutorials, or ask us for more information through our contact center.

New names and terms

There are some changes to names and terminology to be aware of:

Norce Commerce Services

Old name(s)New name(s)Notes
Storm API and Norce [Storm] APINorce Commerce Services / Commerce ServicesThe old Storm API is now referred to as just "Services" or "Norce Commerce Services", with this change we want to stress the move to more autonomous service components that are less dependent on the each-other.
We also move the versioning from path/v1.1/productservice to be under the service like path/productservice/v1.1 instead.

Norce Commerce Connect, Query, Event and Feed

Old name(s)New name(s)Notes
Storm Connect API / Norce [Storm] Connect APINorce Commerce Connect / Commerce ConnectIn documentation it is sometimes shortened to Norce Connect, or just Connect.
Storm Query API / Norce [Storm] Query APINorce Commerce Query / Commerce QueryIn documentation it is sometimes shortened to Norce Query, or just Query.
Storm Event / Norce [Storm] EventNorce Commerce Event / Commerce EventEvent has undergone a change, using webhooks instead of allowing for direct connection to our Azure Service Bus.
Read more about this in the upgrade article.
Storm Channel Feed / Channel Service or Norce [Storm] Channel ServiceNorce Commerce Product feed / Product feedThe channel service or channel feed are now just called Product Feed. It is more accurate naming for what it does.

APIs and versioning

The API reference documentation has gotten a version feature, where each API currently has a Norce [Storm] version and a Norce Commerce version. At the time of writing they are identical, but might change in the future (2024->and forward). When needed, we will add a new minor (0.x) or major (x.0) version to the reference documentation, alongside the older ones.

API versions

Read more