Published at: 2026-10-12

SKU and SPU relationships

Review the rules, scope, and limits for SKU and SPU relationships.

Overview

Review the rules, scope, and limits for SKU and SPU relationships.

Quick reference

Item	Description
Core rules	Use this page to quickly check SKU and SPU relationships.
Usage boundary	Conditions and limits are defined in the matching sections of this topic.

Rules

Product sales information

Product maintenance

SKU mode

New enterprises enable the product object by default. The mall needs images, rich-text introductions, and attribute descriptions, so complete product fields including Product Image, Product Category, and rich-text details.

To give downstream dealers, agents, and accounts a good ordering experience, maintain:

Images: ShareOrder aims for a B2C ordering experience. Image maintenance is required.
Product Category: avoid too many levels. For FMCG, apparel, and appliances, keep it within 2 levels.
Rich-text details: users view the introduction in Product Details.
Price: the base Product Price. If you do not maintain it, downstream sees only the Price Book Price.
Barcode: after a barcode is maintained, users can scan to order in ShareOrder.
Safety Stock: after Inventory Management is enabled, a Safety Stock field is added. When stock is below Safety Stock, inventory admins are notified.

Hide confidential fields such as purchase price and original price from dealers.

SPU mode

FMCG and durable-goods accounts often need multiple specs. Enable the merchandise object. Path: Management > CRM platform management > Business rule management > Merchandise/product configuration

The merchandise object is for multiple specs. Maintain spec records plus merchandise images, categories, and rich-text details.

Notes:

If you need multiple units, enable multi-unit together.
If you need lot or serial number management, enable that capability together.

Image management

For large SKU and SPU volumes, especially in FMCG, batch add or update product images to improve operations efficiency.

Use this capability to Upload Image files to the cloud drive, delete or add current product images, and sync current SPU images to SKUs:

Select products, then add images from the cloud drive.

Tag management

After ShareOrder is enabled, a Tag field is added on product/merchandise objects. Manage tags in Setup, including edit, add, and disable.

The mall can display data by tag.

Mobile portal example:

Web portal example:

Mall categories

If mall categories differ from internal management categories, enable mall categories.

Enable mall categories
Associate mall categories on merchandise/product objects
Filter the mall product list by mall category

See ordering mall business parameters.

ERP material sync to generate SPU

Background

Some existing CRM accounts that start using ShareOrder want downstream dealers to view and buy products by multiple specs. Original ERP sync created only product (SKU) objects. They now want to enable merchandise (SPU). After SKU has been running, SPU cannot be enabled directly. Product and R&D added an emergency path to upgrade SKU to SPU for mall multi-spec display.

This topic describes ERP sync solutions for generating SPU.

ERP material sync solutions

For mainstream ERP systems such as SAP, Kingdee, and Yonyou, use the integration platform with no-code mapping.

Solution 1: ERP materials sync as SKU

This is the simplest solution and uses the standard integration platform. See https://help.fxiaoke.com/9bfb/c68f/b923/4308

##### Solution 2: ERP materials sync as SPU

Many FMCG and durable-goods enterprises need SPU when ShareOrder goes live. On top of solution 1, analyze ERP material fields, decide which fields sync to the merchandise object and which sync to spec/spec-value objects, then use object mapping rules.

Details: https://help.fxiaoke.com/9bfb/c68f/b923/4308

NOTE: Generating SPU without specs is similar to generating SKU and is not the focus of this topic.

Detailed steps for generating SPU from ERP materials

There are four steps. Step 1 is the core. Step 2 configures mapping rules on the ERP integration platform. Steps 3 and 4 are post-sync checks.

Example: ERP synced SKU data needs to be merged into SPU. Use Product Name as the unique SPU key. Use Color and Spec as spec dimensions, and values such as White/Red/Yellow and 11 / 11.5 as spec values.

Notes:

Merge SPU by unique Product Name: - Product Name must match exactly, with no extra spaces - The same product cannot belong to multiple categories - The same product cannot have multiple units
Generate spec/spec values from Color and Spec. Both fields must have values, otherwise only a no-spec SPU can be generated.

R&D support process

New accounts generating SPU from sync

For ERP-synced accounts that need SPU, see the ERP integration docs. Contact the CSM if you need R&D help.

2. Existing accounts upgrading to SPU

Existing accounts already have SKU data that cannot be deleted. Upgrade has risk and needs R&D. Contact technical staff.

The core is still step 1: define merchandise merge rules and spec dimensions, clean SKU data, then ask R&D to check. After the check passes, upgrade existing data. After upgrade, SPU is enabled automatically, merchandise and specs are added, SKUs stay unchanged, CRM operations are unaffected, and the mall supports multi-spec selection.

For new ERP materials, adjust the ERP sync strategy the same way as a new enterprise.

Existing CRM data is upgraded once. Incremental data uses the adjusted sync strategy.
Stop ERP sync before upgrading existing data to SPU.
Data checks can take several rounds over several days. Correct data after each check and reserve implementation time.

This check is not tool-based yet. Contact R&D.

Usage boundary

Applicable scope: ShareOrder Professional Edition.
Edition check: Confirm the tenant edition and enabled capabilities first.
Permission: Entries are controlled by role and Data Permission.