Replace SKU

---

Contents

• 1. Use Cases
• 2. Feature Guide
• 3. FAQ
• 4. Related Features

---

1. Use Cases

Quick Links: Standardize Format | Supplier Code Change | Fix Incorrect SKUs

Scenario 1: Merchant Wants to Standardize Coding Format

Situation: Merchant A wants to change 300 product SKUs from numeric codes to branded prefix format (e.g., 123456 → BrandA-123456).

How to do it:

▸ Prepare CSV File

1. Click "Download Template" to get the standard format
2. Enter Old SKU in column A in Excel
3. Use a formula in column B to generate New SKU: ="BrandA-"&A2
4. Select column B → "Copy" → "Paste Special" → "Values"
5. Save as CSV (UTF-8 encoding)

▸ Upload and Execute

6. Select the merchant
7. Upload the CSV file
8. Click "Next" to view validation results
9. Confirm all are "Valid" then click "Confirm"

Result: Execution results show success and failure counts. Search the new SKUs in "Product List" to confirm successful replacement.

---

Scenario 2: Supplier Updates Product Codes

Situation: The merchant's supplier updated their coding system. 200 product SKUs need to be synced.

How to do it:

▸ Get Mapping Table

1. Obtain the old-new code mapping table from the merchant
2. Organize into a CSV with "Old SKU" and "New SKU" columns

▸ Upload and Validate

3. Select the corresponding merchant
4. Upload the CSV file
5. System checks if old SKUs exist and if new SKUs are duplicated
6. If there's "Invalid" data, identify issues from error messages

▸ Execute Replacement

7. Fix issues and re-upload
8. Confirm all are "Valid" then execute

Result: Warehouse system SKUs stay consistent with supplier, avoiding confusion during procurement.

---

Scenario 3: Fix Incorrect Codes Found During Warehouse Operations

Situation: During picking, 50 products were found with incorrect SKU codes, often leading to wrong items being picked.

How to do it:

1. Compile the list of 50 products needing correction
2. Confirm correct SKUs with the merchant
3. Create an "Incorrect SKU → Correct SKU" mapping table
4. Upload CSV to execute replacement
5. Update warehouse shelf labels

Result: After SKU correction, picking errors are reduced and operational efficiency improves.

---

2. Feature Guide

Replace SKU allows you to batch update product SKUs. When merchants need to standardize coding formats, suppliers change product codes, or bulk corrections are required, you can upload a CSV file to replace multiple product SKUs at once, saving significant time compared to manual editing.

Quick Jump: Steps | CSV Format | Validation Rules

2.1 Steps

▸ Step 1: Select Merchant and Prepare CSV File

1. Select the merchant whose SKUs you want to replace from the dropdown
2. Click "Download Template" to get the standard format
3. Fill in "Old SKU" and "New SKU" in Excel
4. Save as CSV (UTF-8 encoding recommended)

▸ Step 2: Upload and Validate

1. Click or drag to upload CSV file
2. Click "Next"
3. System automatically validates each record
4. View validation results table

▸ Step 3: Confirm Execution

1. Check for any "Invalid" data
2. If issues found, click "Previous" to fix and re-upload
3. After confirming, click "Confirm" to execute replacement

▸ Step 4: Verify Results

1. View execution results (shows success and failure counts)
2. Click "Close" to return
3. Search for new SKUs in "Product List" to confirm successful replacement

---

2.2 CSV File Format

Fields marked with * are required

Field Name	How to Fill	Notes
*Old SKU	Enter the product SKU to be replaced	Must be an existing SKU under the selected merchant
*New SKU	Enter the new SKU after replacement	Cannot duplicate existing product SKUs

File Format Requirements:

• Only .csv format accepted
• UTF-8 encoding recommended (avoids character encoding issues)
• First row is header, data starts from second row

---

2.3 Validation Rules

System automatically checks the following:

Check Item	Error Message
Old SKU or New SKU is empty	"SKU cannot be empty"
New and old SKU are the same	"New and old SKU cannot be the same"
Old SKU doesn't exist	"Old SKU not found"
New SKU is already in use	"New SKU already exists"
Duplicate new SKUs in CSV	"Duplicate New SKU in CSV"

Preview Table Columns:

Column	Description
Old SKU	SKU to be replaced
New SKU	SKU after replacement
Status	"Valid" (green) or "Invalid" (red)
Message	Shows failure reason when validation fails

---

3. FAQ

Quick Jump: FAQ | Notes

3.1 FAQ

▪ What data is affected after replacing SKU?

Data Type	Affected?
Product SKU	Updated to the new SKU
Inventory Data	Inventory follows the product; quantities unchanged
Historical Orders, Inbound/Outbound Records	Documents still link to the same product, so they will show the new SKU when viewed later
Edit History	The SKU change is recorded in the product's "Edit History"

📌 Note: Before replacing, make sure on-site labels and the merchant's reconciliation data will be updated accordingly, so SKUs don't get out of sync.

---

▪ What if some data fails validation?

System uses a "partial success" mechanism:

• Only "Valid" data gets replaced
• "Invalid" data is skipped
• Execution results show success and failure counts

It's recommended to fix all errors before executing to avoid missing any.

---

▪ How many can be replaced at once?

Recommended not to exceed 1,000 records per batch.

If over 1,000 records:

1. Split CSV into multiple files
2. Execute in batches
3. Verify results after each batch

---

▪ What encoding should the CSV use?

UTF-8 encoding is recommended.

Excel Save Method:

1. Choose "Save As"
2. Select format "CSV UTF-8 (Comma delimited) (.csv)"

Google Sheets:

1. "File" → "Download" → "Comma-separated values (.csv)"
2. Google Sheets defaults to UTF-8

---

▪ Why does it show "Old SKU not found"?

Possible reasons:

• SKU typo or copy error
• Product hasn't been created yet
• Product has been deleted
• Wrong merchant selected

Search in "Product List" to confirm if the SKU exists under the selected merchant.

---

▪ Why does it show "New SKU already exists"?

This SKU is already being used by another product under the same merchant.

Search the new SKU in "Product List" to identify which product is using it, then plan a non-duplicate SKU.

---

▪ Can I revert after replacement?

There's no automatic revert function. To revert:

1. Prepare a "reverse mapping table" (swap new and old SKUs)
2. Execute the Replace SKU feature again

It's recommended to export the product list as backup before executing.

---

▪ How to batch add prefix or suffix?

Use Excel formulas to quickly generate:

Add prefix "CUS-A-": In B2 enter ="CUS-A-"&A2

Add suffix "-V2": In B2 enter =A2&"-V2"

Steps:

1. Put old SKUs in column A
2. Use formula in column B to generate new SKUs
3. Select column B → "Copy" → "Paste Special" → "Values"
4. Save as CSV and upload

---

3.2 Notes

⚠️ About Replacement Operations

• Replacement cannot be auto-reverted; revert requires executing replacement again
• Recommended to export product list backup before executing
• Large data sets should be processed in batches (1,000 records or less each)

⚠️ About SKU Uniqueness

• SKUs cannot be duplicated within the same merchant
• New SKU cannot match an existing product's SKU
• New SKUs in CSV also cannot be duplicated

⚠️ About Historical Data

• Historical documents still link to the same product and will show the new SKU when viewed later
• The change record is kept in the product's "Edit History" on the details page
• Confirm with the merchant before replacing, so reconciliation SKUs don't get out of sync

---

4. Related Features

Feature	Description	Link
Product List	View, search, edit products	Go
New Product	Manually add a single product	Go
Import Products	Batch import product data	Go