English

中文

English

中文

Appearance

Import Return Orders ​

Table of Contents ​

1. Use Cases ​

Quick Links: Bulk-create from a List | Multiple Return Orders at Once | Update Imported Return Orders

Scenario 1: A Large Return List Arrives — Create in Bulk ​

Situation: A 貨主 sends a return list with dozens of items. Creating them one by one is too slow, so you import them from Excel.

Steps:

▸ Prepare the file ​

  1. Click "Import" to open the "Import Return Orders" window
  2. Select the 貨主 and click "Download Template" to get the Excel template
  3. Fill the return list into the template

▸ Upload ​

  1. Back in the import window, select the completed file
  2. Click "Upload" to start importing

Result: Check the result under "Data Exchange Logs" → "Import Logs"; successfully created return orders appear in the return list.

Scenario 2: Import Multiple Return Orders at Once ​

Situation: You need to create several return orders at the same time, each with different items.

Steps:

  1. In Excel, use different Return Order Number values to separate the return orders
  2. Put each return order's items on consecutive rows; the Return Order Number only needs to be filled on the first row of each group
  3. Upload and import

Result: The system groups rows by Return Order Number and creates multiple return orders automatically.

Scenario 3: Update Previously Imported Return Orders ​

Situation: A previously imported return order has wrong quantities. The package hasn't arrived and the status is still "Pending", so you re-import a corrected file.

Steps:

  1. Fix the Excel content, keeping the same Return Order Number
  2. Check "Override existing data" in the import window
  3. Upload and import

Result: Return orders with the same number that are still "Pending" are updated (their item details are fully replaced). Return orders that already started checking cannot be updated via import.

2. Features ​

When there are many returns, use import to create return orders in bulk from Excel instead of typing them one by one. Click "Import" on the return list to open the import window, download the template, fill it in and upload; results are available in the import logs. Multiple rows with the same number merge into one return order.

Quick Jump: Import Fields | Steps | Import Logic

2.1 Import Fields ​

▸ Required fields ​

FieldDescription
*Return order numberUnique number of the return order. For multiple items on one return order, fill it only on the group's first row
*SKUThe returned product's SKU; must exist in the 貨主's product data
*QuantityExpected return quantity

▸ Optional fields ​

FieldDescription
Extra numberA secondary reference number (e.g. from the 貨主's own system)
Order numberThe related original order number
NoteReturn order note
Inventory typeThe code of the 貨主's inventory type, used to classify restocked goods
Expiration dateThe product's expiry date; follow the sample format in the template
BatchThe product's batch number
Item noteNote for an individual item

2.2 Steps ​

▸ Download the template and fill in data ​

  1. Click "Import" on the Return List
  2. Select the 貨主 (imported return orders belong to it)
  3. To apply a saved column mapping, choose an "Import Template"
  4. Click "Download Template" to get the Excel template
  5. Fill in the data — each row is one returned item

▸ Upload and check results ​

  1. Select the completed Excel file
  2. Check "Override existing data" if you intend to update existing return orders
  3. Click "Upload"
  4. Check the per-row results under "Data Exchange Logs" → "Import Logs"

2.3 Import Logic ​

  • Multiple items per return order: consecutive rows with the same return order number (or with the number left blank to continue the previous row) merge into one return order, each row becoming an item
  • Number already exists: without "Override existing data", the row fails with a "return order already exists" error. With it checked, return orders still in "Pending" are updated (item details fully replaced); ones that already started checking fail with a cannot-update error
  • Inventory type code: must be an existing inventory type code of the 貨主; an unknown code fails that row. Leave it blank to decide during checking

3. FAQ ​

3.1 FAQ ​

▪ What should I do when an import fails? ​

Open the import record under "Data Exchange Logs" → "Import Logs" — it lists the error for every row. Common causes: missing required fields, unknown SKU, wrong inventory type code, duplicate numbers. Fix and re-upload.

▪ Why did some items fail to import? ​

Possible causes: the SKU does not exist in the system, or it belongs to another 貨主. Verify the product data and retry.

▪ What goes in the inventory type column? ​

The code of the 貨主's inventory type (not its name). If unsure, ask whoever manages inventory type settings, or leave it blank and choose during checking.

▪ Can an import be undone? ​

Not as a whole. If the data is wrong, re-import corrected data with "Override existing data" (only works for "Pending"), or handle the affected return orders individually.

▪ Where do I see the import result? ​

After uploading, check the per-row results under "Data Exchange Logs" → "Import Logs"; created return orders appear in the Return List.

▪ When do I need the expiry date and batch columns? ​

When the product needs expiry management or batch tracking. The same product with two different expiry dates or batches should be on two separate rows.

▪ What does "return order cannot be updated" mean? ​

The return order with that number already started checking (its status is no longer "Pending"), so import can't modify it. To correct check results, use the return order detail page instead.

3.2 Important Notes ​

⚠️ Important ​

  • Always use the latest system template; adding or removing columns yourself breaks the import
  • Select the right 貨主 first — SKUs and inventory type codes are validated against that 貨主's data
  • "Override existing data" only updates "Pending" return orders, and replaces their item details entirely
  • After uploading, check the import log; when some rows fail, only the failed rows need fixing and re-uploading