Skip to main content

UNSPSC Mapping

Understanding and managing UNSPSC mapping in the Axiom system

Overview

UNSPSC (United Nations Standard Products and Services Code) Mapping is a feature that allows you to standardize product categorization across your procurement system. It provides a way to map your organization's specific classification codes to the standardized UNSPSC taxonomy, ensuring consistent categorization across different suppliers, platforms, and systems.

What is UNSPSC?

UNSPSC is a global classification system for products and services that provides a hierarchical structure for categorizing items. Each UNSPSC code consists of:

  1. Segment (first 2 digits) - The broadest category level
  2. Family (digits 3-4) - A subcategory of the segment
  3. Class (digits 5-6) - A group within the family
  4. Commodity (digits 7-8) - The most specific category

For example, in the code "41100000":

  • "41" represents the segment (Lab and Scientific Equipment)
  • "11" represents the family (Lab instruments and equipment)
  • "00" represents the class (Not specified at this level)
  • "00" represents the commodity (Not specified at this level)

Purpose of UNSPSC Mapping

UNSPSC Mapping serves several important functions:

  1. Standardization: Convert proprietary or supplier-specific product codes to universal UNSPSC codes
  2. Data Harmonization: Enable comparison and analysis across different product sources
  3. Spend Analysis: Facilitate accurate spend visibility and category management
  4. System Integration: Enable smooth data exchange between different procurement systems
  5. Regulatory Compliance: Meet industry or governmental reporting requirements

How UNSPSC Mapping Works

Mapping Structure

Each UNSPSC mapping in the system consists of:

  1. Mapped From: The source UNSPSC code that needs to be translated
  2. Mapped To: The target code and type information (currently supporting UNSPSC as the mapping type)
  3. Store Association: Each mapping belongs to a specific store
  4. Client Association: Each mapping is linked to a client organization

Version Control

The system supports different versions of the UNSPSC standard. Each store can specify which UNSPSC version it uses, and mappings are validated against the specified version.

Resolution Process

When a product with a UNSPSC code is processed (such as during checkout or reporting):

  1. The system checks if there's a mapping for the product's UNSPSC code
  2. If a mapping exists, the system uses the mapped-to value
  3. If no mapping exists, the original UNSPSC code is used

Managing UNSPSC Mappings

Viewing Mappings

Users with the appropriate permissions can view all UNSPSC mappings for a store. This list can be filtered and paginated for easier navigation.

Creating or Updating Mappings

To create a new mapping or update an existing one:

  1. Select the store where the mapping should apply
  2. Specify the source UNSPSC code (mapped from)
  3. Specify the target information, including:
    • Type (currently only UNSPSC is supported)
    • Value (the target UNSPSC code)

The system will validate that both the source and target UNSPSC codes are valid according to the store's specified UNSPSC version.

Deleting Mappings

Mappings that are no longer needed can be deleted from the system.

Use Cases for UNSPSC Mapping

Procurement Standardization

When purchasing products from multiple suppliers who use different categorization schemes, UNSPSC mapping allows for standardized reporting and analysis across all suppliers.

System Integration

When integrating with external procurement systems or e-catalogs, UNSPSC mapping ensures that product categories are correctly translated between systems.

Spend Analysis

By mapping all products to standard UNSPSC codes, organizations can perform accurate spend analysis across categories, regardless of the original product classification.

Supplier Onboarding

When onboarding new suppliers, their product catalogs can be mapped to your organization's preferred UNSPSC codes, ensuring consistency with existing procurement data.

Best Practices

  1. Maintain Version Consistency: Ensure that your store is using the appropriate UNSPSC version for your industry and region.

  2. Regular Review: Periodically review your mappings to ensure they still align with your organization's categorization needs.

  3. Mapping at Appropriate Levels: Map at the most specific level possible (commodity level) for detailed analysis, but consider whether family or class level mapping is sufficient for some categories.

  4. Documentation: Keep records of why certain mappings were created, especially for non-obvious cases.

  5. Bulk Operations: For large catalogs, consider using bulk import/export tools to manage mappings efficiently.

Technical Details

Validation

Both source and target UNSPSC codes are validated against the store's specified UNSPSC version to ensure they exist in the standard.

Performance Optimization

For efficiency, mappings are resolved in bulk whenever possible, reducing database queries when processing multiple products.

Integration with Other System Components

UNSPSC Mapping integrates with several other system components:

  1. Products and Services: Products and services can be assigned UNSPSC codes either directly or through mapping
  2. Checkout Process: During checkout, UNSPSC codes may be mapped to ensure consistent classification
  3. Reporting: Reports can use mapped UNSPSC codes for consistent category analysis
  4. Store Configuration: Each store can specify its preferred UNSPSC version

By effectively using UNSPSC Mapping, your organization can ensure consistent product categorization across all procurement activities, enabling better spend analysis, supplier management, and system integration.

Last updated on Mar 28, 2025 by omelbs