Published at: 2026-10-12

Maintain product SKUs and product SPUs

Maintain the product and merchandise relationship so the mall can sell them.

Before you begin

❗

Applicable scope: ShareOrder Professional Edition.
Role and permission: Use an admin account with ShareOrder management permission.
Prerequisites: Prepare test accounts, products, and price data.

Steps

Maintain merchandise sales information

Maintain merchandise and products

SKU mode

After a new enterprise is enabled, the product object is enabled by default. The mall needs richer product display, including images, rich-text introductions, and attribute descriptions. Complete product fields as much as possible, including product images, Product Category, and rich-text Product Details.

To give Downstream dealers, partners, and accounts a good ordering experience, maintain the following information as the basic mall product data:

Images: ShareOrder aims for a B2C ordering experience similar to JD.com or Taobao, so image maintenance is required.
Product Category: Do not set too many category levels. For FMCG, apparel, and appliances, keep it within 2 levels.
Rich-text details: Users can view the introduction in Product Details so dealers can understand product features quickly.
Price: The product base price can be a reference for dealers. Maintain it if needed. If you do not maintain it, Downstream can only see the Price Book Price.
Barcode: After you maintain a barcode, users can scan to order in ShareOrder.
Safety Stock: After inventory is enabled, the Safety Stock field is added. When inventory is below Safety Stock, Inventory Management admins are prompted.

For confidential product fields such as purchase price and original price that you do not want dealers to see, hide them from dealers.

#### SPU mode

For FMCG or durable-goods accounts that need multiple specifications, enable the merchandise object. Path: Administration > CRM Platform Administration > Business Rule Management > Merchandise/Product Configuration

The core of the merchandise object is multiple specifications. Maintain multi-spec records, plus merchandise images, merchandise categories, and merchandise rich-text details.

NOTE:

If you need multiple units, enable multi-unit together. See the video below.
If you need batch or serial number management, enable batch and serial number together. See the video below.

Image management

For accounts with a large SKU or SPU volume, especially in FMCG, batch add or Update product/merchandise images to improve SPU and SKU operations.

Use this feature to batch manage, upload, and Update merchandise/product images. You can upload images to the cloud drive, delete or add images for the current product/merchandise, and sync current SPU images to SKUs.

Select Add merchandise, batch-select the merchandise whose images you want to Update, then select Add images and choose images from the cloud drive.

Tag management

Enabling ShareOrder adds a Tag field on the product/merchandise object. Select tags as needed. Manage tags in the backend, including edit, add, and disable.

The mall can display data based on tags.

Mobile portal setting example

Web portal setting example alt text

Mall categories

If the category shown in the mall differs from the internal management category, enable mall categories.

Enable mall categories.
Associate mall categories on the merchandise/product object.
On the mall front end, filter the product list by mall category.

For details, see ordering mall business parameters.

Generate SPUs from ERP materials

Background

Some existing CRM accounts now using ShareOrder want Downstream dealers to view and buy products by multiple specifications. Original ERP sync only generated the product (SKU) object. They now want to enable the merchandise (SPU) object. After SKU has been enabled and the system has run for a while, you cannot enable SPU directly. Because go-live was urgent, product and R&D provided an emergency path: upgrade SKU to SPU so the mall can show multiple specifications.

For similar new projects, implementation owners may not know how to generate multi-spec SPUs during ERP integration. Existing accounts that need to upgrade to multi-spec SPU may also not know how to proceed. This topic describes the ERP sync SPU solution.

ERP material sync options

ERP integration should be familiar. For mainstream ERP systems such as SAP, Kingdee, and Yonyou, you can use the connection platform and complete integration with no-code implementation. The following two methods both depend on this basic capability.

Option 1: ERP materials sync to SKUs

This option is the simplest and is used by many projects. Use the standard integration platform. See the integration document: https://help.fxiaoke.com/9bfb/c68f/b923/4308

Option 2: ERP materials sync to SPUs

Many FMCG or durable-goods enterprises need to enable SPU when ShareOrder goes live. For ERP-synced enterprises, start from option 1, then organize, analyze, and process ERP material data. Decide which material fields sync to the merchandise object and which sync to the spec/spec-value object. Then sync them with object mapping rules on the ERP integration platform.

Detailed steps are below. See also: https://help.fxiaoke.com/9bfb/c68f/b923/4308

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

Detailed steps to generate SPUs from ERP materials

ERP sync to SPU has four steps, as shown in the figure.

Step 1 is the core. Step 2 configures mapping rules on the ERP integration platform. Steps 3 and 4 check the data after sync.

The following example explains the core step 1.

The table below shows SKU data synced from ERP. You need to merge it into SPUs. You can use Product name as the SPU uniqueness rule. The same product name generates the same SPU. Color and Spec can be specifications. Values such as White, Red, and Yellow, and 11 and 11.5, can be spec values. With clear rules like this, you can upgrade.

Use product name, color, and spec to merge SKUs into SPUs

Also note:

Merge SPUs by unique Product name: - Product names must match exactly, with no extra spaces. - The same product cannot belong to multiple categories. - The same product cannot have multiple units.
Generate specs/spec values from Color and Spec. When checking data, color and spec must both have values. Otherwise you can only generate an SPU without specs.

R&D support process

Generate SPUs for a new account

For ERP-synced accounts that need to generate SPUs, see the ERP integration document. If you have questions, contact the CSM and ask R&D for help.

New account ERP sync SPU support process

Contact CSM and R&D for ERP SPU generation

Upgrade existing accounts to SPU

Existing accounts have usually been in use for some time. SKU data cannot be deleted, and business cannot be affected. Upgrade has risk, so R&D needs to join. Contact technical staff if needed. The process is as follows.

The core is still step 1, similar to enabling a new enterprise. Confirm the merchandise merge standard and spec dimensions. After you confirm the standard and adjust SKU data, 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 not affected. The mall supports multi-spec selection and ordering.

For syncing new ERP materials, adjust the ERP sync strategy. The operation is the same as for a new enterprise. NOTE:

Existing data already synced to CRM is upgraded only once. Adjust the sync strategy for incremental data, then sync.
Before you upgrade existing data to SPU, stop ERP sync.
Data checks during upgrade may repeat several times and can last several days. After each check, correct the data in a Timely way. Reserve implementation time.
This check is not tool-based yet. Contact R&D first.

Expected results

Use a test account to confirm the saved settings take effect on the related pages and records.

Undo or roll back

Return to the configuration entry, restore the previous switch, layout, or rule values, and re-verify with a test account.