This document is still a draft and might change
This document provides a structured overview of the Supplywise client solution in Norce Commerce, focusing on product types, categorization, enrichment, pricing, and availability. Each section is self-contained for clarity and AI-friendly reading.
Supplywise manages a large assortment of products, primarily sourced from suppliers. Products are created automatically in Norce Commerce from supplier data, then enriched with external content (e.g., Etilize) and, for the primary assortment, sometimes manually.
- Product Types: Most products are initially of type “Extended” and are transformed to “Standard” when first ordered.
- Volume: The client manages over 100,000 products.
Supplywise uses a four-level category hierarchy to organize its large assortment. Categories are based on internal business segmentation and the structure provided by content suppliers. Online storefront navigation is managed separately via CMS design.
Category Hierarchy Example:
- All products
- Electronics
- Conference
- Phones
- Sound
- TV
- Computers
- Laptops
- Workstations
- Accessories
- ...
- ...
- Office supplies
- ...
- Electronics
- Non-buyable products
- ...
Note: A master category "All products" enables business rules to be applied to all buyable products, excluding placeholders or containers.
Product flags are used to segment business logic, such as special purchase handling. Flags are assigned as IDs and can be resolved to details using Norce APIs.
Parametrics are structured product attributes (e.g., size, color, technical specifications). These are enriched from supplier data and external content systems.
Supplywise classifies products into several types, each with a specific handling in Norce Commerce:
| Classification | Description | Norce Type | Notes |
|---|---|---|---|
| Self-stocked | Purchased from supplier, stored in client's warehouse | Standard | Uses standard type in Norce |
| Long tail | Not pre-purchased; ordered from supplier as needed | Extended | Extended type; supplier info sent to ERP for purchase order creation |
| Packages | Pre-packaged products from suppliers | ManagedErpPackage | Hard bundles; kits contain other catalog products |
| Bundles | Sold as bundles for better price (e.g., cartons, pallets) | ManagedStructure | Soft bundles; SKUs can be sold separately |
| Fees | Environmental fees or taxes | Fee | Not physical products; cannot be out of stock |
| Services | Additional services for some offers | Services | Not physical; can be added to orders by relations or promotions |
Supplywise uses an "extended assortment" to offer a wide range of products not fully handled in backend systems until needed. This approach attracts customers with niche products and enables upselling or suggesting alternatives.
- Standard products: Fully managed in ERP.
- Extended products: Managed in Norce until purchased.
Product Type Distribution:
Text alternative: The following pie chart shows the number of products by type in the catalog: 10,000 Standard, 100,000 Extended, 500 Package, 1,500 Structure, 50 Service, 50 Fees.
Products are created in Norce based on supplier data and rules, then enriched and made buyable. Standard products are created in ERP immediately; extended products remain in Norce until ordered.
Lifecycle Sequence Diagram (Text alternative):
- Supplier sends new products to Norce.
- Standard products are created in ERP; extended products remain in Norce.
- Products are enriched.
- Products become buyable online.
- When an order is placed, extended products are created in ERP as needed.
- Some assortments are created directly in ERP after Norce creation, triggered by product type.
- Activation: Extended products are activated automatically when in supplier stock; standard products are activated manually or by schedule.
- Deactivation: Standard products are deactivated when expired and out of stock; extended products are deactivated when no supplier sells them.
See more about status automation here.
Most product enrichment is automated via integrations. Product managers validate and activate new products.
Enrichment Workflow (Text alternative):
- Products are categorized automatically by creation rules.
- Supplier integrations check for existing SKUs and import content.
- New products are matched and enriched from Etilize.
- Product managers validate content before activation.
Image: Product enrichment workflow diagram (../images/pim-workflows-enrichments-new-supplywise.png)
Supplywise uses a layered price list structure to manage pricing for all products and customers.
Price List Structure (Text alternative):
- Base price list: Contains all products and creation rules.
- Market price lists: Inherit from base, can exclude products by rules or supplier availability.
- Supplier price lists: Market-specific purchase costs.
- Customer price lists: Contract or supplier agreement-based.
- Company discounts: Category or flag-based rules.
Image: Price list structure diagram (../images/prices-inventory-new-supplywise.png)
- Base price list: Cost-based prices (purchase cost for extended, unit cost for standard).
- Contract price lists: Fixed prices.
- Bid/agreement price lists: Purchase cost-based, using supplier price lists.
Norce setting: "Discard public prices when price list seed is used" is enabled. This allows business customers to see agreement or discount prices, even if higher than campaigns, supporting non-monetary agreement benefits.
When enabled, the storefront must specify all relevant price lists in the PriceListSeed parameter for best price calculation.
- Core assortment uses local warehouse; most products use supplier dropshipping.
- No market- or store-specific warehouses.
- Availability is calculated with a supplier focus.
See Availability structure for more details.