Published at: 2025-10-31

Key Scenario Capabilities | ERP Material Synchronization to SPU Solution


Background

Recently, some existing CRM customers using Order Connector have requested the ability for their Downstream Distributors to view and purchase Products with multiple specifications. Previously, ERP synchronization only generated SKU (Stock Keeping Unit) objects, but there is now a need to enable SPU (Standard Product Unit) objects. However, since SKUs have already been activated and the system has been operational for some time, directly enabling SPUs is not feasible. Given the urgency of project deployment, the product team implemented an emergency solution: upgrading SKUs to SPUs, achieving a multi-specification effect for the online store.

For similar new projects, implementation personnel may not know how to generate multi-spec SPUs during ERP integration, or existing customers may need guidance on upgrading to multi-spec SPUs. This document outlines the ERP synchronization solution for generating SPUs.

image

ERP Material Synchronization Solutions

ERP integration is a familiar process. For mainstream ERP systems like SAP, Kingdee, or Yonyou, you can use the Interconnection platform for zero-code configuration. Below are two approaches, both leveraging this foundational capability.

Solution 1: ERP Material Synchronization to Generate SKUs

This is the simplest approach and widely adopted. It uses standard integration platforms. For detailed documentation, refer to: ERP Integration Guide.

image

image

Solution 2: ERP Material Synchronization to Generate SPUs

For fast-moving or durable goods industries, enabling SPUs in Order Connector is often necessary. This approach builds on Solution 1 but requires additional ERP data organization, analysis, and mapping to determine which fields sync to the Product object and which sync to the specification/attribute objects.

Key steps are outlined below. For details, refer to: ERP Integration Guide.

image

Note: Generating SPUs without specifications is similar to generating SKUs and is not the focus of this document.

image

Detailed Steps for ERP Material to SPU Conversion

The process consists of four steps (see below). Step 1 is the most critical. Step 2 involves configuring mapping rules in the ERP integration platform. Steps 3 and 4 involve post-sync verification.

image

Example: Core Step 1

The table below shows ERP-synced SKU data that needs consolidation into SPUs. Use [Product Name] as the uniqueness criterion for SPUs—identical names generate the same SPU. [Color] and [Specification] serve as attributes, with values like “White,” “Red,” “Yellow,” “1x1,” or “1x1.5” becoming attribute values. Clear rules like these enable successful upgrades.

image

Additional Notes:

1) Merge SPUs based on [Product Name] uniqueness:
- Product names must match exactly (no extra spaces).
- A product cannot belong to multiple categories.
- A product cannot have multiple Units.

2) Generate attributes/values from [Color] and [Specification] fields:
- Ensure both fields have values; otherwise, only non-spec SPUs can be created.

R&D Support Process

1) New Customers: Synchronizing SPUs

For ERP-synced customers needing SPU generation, refer to the ERP integration documentation. For questions, contact your CSM to engage R&D support.

image

image

2) Existing Customers: Upgrading to SPUs

For long-term SKU users, upgrading carries risks (e.g., data integrity, business continuity). R&D assistance is required. The process mirrors new customer setup but includes:
- Defining consolidation rules and attribute dimensions.
- Adjusting SKU data and undergoing R&D review.
- Executing batch upgrades (SPUs auto-activate; SKUs remain unchanged).

image

For new ERP material syncs, adjust the synchronization strategy (same as new customers). Key reminders:
- Batch upgrades apply only to existing data; new data requires sync strategy adjustments.
- Pause ERP syncs during upgrades.
- Data validation may take multiple iterations—allocate sufficient implementation time.

Currently, this process requires manual R&D support.

Full documentation:
- Order Connector - Admin Guide
- Order Connector - User Manual

Submit Feedback