Method 2: Bulk import
When volumes are high, or the orders already live in your own system, use Import on the list page to create many orders at once. Creating them one at a time? See Method 1: Create in the console.
Step 1: Download the template
On the Parcel Outbound list, click Import. The dialog offers two templates:
| Template | How one order is expressed | Best for |
|---|---|---|
| Template 1 | One row = one order, extra products go across (SKU1…SKU20) | The normal case, a few SKUs per order |
| Template 2 | Several rows = one order, extra products go down | Orders with many SKUs |
The rest of this page uses Template 1 (ParcelOutbound_Import), which has six sheets:
| Sheet | What it's for |
|---|---|
| 小包出库单 | The only sheet you fill in — one row per outbound order |
| 仓库代码 | Warehouse name ↔ warehouse code |
| 物流渠道 | Channel name ↔ channel code, plus the warehouses each channel is bound to |
| 承运商 | Carrier name ↔ carrier code |
| 销售平台 | The sales platforms you can choose from |
| 国家或地区简码 | Country names ↔ two-letter codes |
Step 2: Fill in the 小包出库单 sheet
Same as Method 1 The field rules are identical to creating an order in the console — how a Japanese address maps onto the fields, what's required, the character limits. See Method 1 rather than repeating them here. The table below adds what's specific to the template: which columns take codes instead of names, and the channel-to-warehouse binding.One row = one order = one parcel. The columns come in two parts: 25 order fields, then up to 20 pairs of SKU + quantity.
Note The yellow-highlighted headers are the required columns: 仓库代码 (warehouse code), 物流渠道 (channel), 收件人 (recipient), 国家/地区简码 (country code), 城市 (city), 邮编 (postcode), 地址1 (address 1), SKU1, 出库数量1 (quantity 1).| Column | Required | How to fill it in | Example |
|---|---|---|---|
| 仓库代码 (Warehouse Code) | ✳︎ | The code, not the name — see the 仓库代码 sheet | TEST |
| 销售平台 (Sales Platform) | Dropdown, sourced from the 销售平台 sheet | Amazon | |
| 店铺 (Store) | Store name, free text | 楽天市場店 | |
| 参考单号 (Reference Number) | A unique id from your own system (ERP or order aggregator) — the easiest way to reconcile a bulk import | SO-20260902-001 | |
| 平台单号 (Platform Number) | Normally filled in automatically by platform sync; set it here to tie the imported order back to its marketplace order | 249-1234567-1234567 | |
| 物流渠道 (Shipping Service) | ✳︎ | The channel code — see the 物流渠道 sheet | T_YAMATO_NEKOPOS |
| 承运商 (Carrier) | Only when using your own label — see the 承运商 sheet | Yamato | |
| 物流跟踪号 (Tracking No.) | Only when using your own label | 460012345678 | |
| 签名服务类型 (Signature Type) | Dropdown: 间接签署 / 直接签署 / 成人签署 | 直接签署 | |
| 保险金额 (Insurance) | A number | 20000 | |
| 收件人 (Recipient) | ✳︎ | Local spelling | 佐藤 健太 |
| 电话 (Phone) | Not highlighted, but Yamato and Sagawa require it on the carrier side — always fill it in | 09012345678 | |
| 邮箱 (Email) | Required by some carriers | sato.kenta@example.jp | |
| 收件人税号 (Tax ID) | Needed for customs in some countries | ||
| 公司名称 (Company) | For business addresses | 株式会社サンプル商事 | |
| 国家/地区简码 (Country) | ✳︎ | Always JP for the Japan warehouse (dropdown; other countries' codes are on the 国家或地区简码 sheet) | JP |
| 省/州 (State) | Not highlighted, but always enter the prefecture (e.g. 東京都); "N/A" only for countries that have no state | 東京都 | |
| 城市 (City) | ✳︎ | For Japan, the ward / municipality | 渋谷区 |
| 邮编 (Postcode) | ✳︎ | Must match the city | 150-0002 |
| 门牌号 (House Number) | Leave empty for Japan — this column is not used | ||
| 地址1 (Address 1) | ✳︎ | For Japan, town name + chome-banchi-go. Max 16 full-width (half-width counts as 0.5) | 渋谷 3-15-7 |
| 地址2 (Address 2) | Building, room and so on. Max 16 full-width chars | グランドメゾン渋谷 502 | |
| 指定配送日期 (Delivery Date) | YYYY-MM-DD | 2026-09-10 | |
| 指定配送时间 (Delivery Time) | Time-slot code; differs per carrier | 14 | |
| 备注 (Remark) | Max 32 full-width (half-width counts as 0.5) | ネコポス投函、対面不要 | |
| SKU1 / 出库数量1 | ✳︎ | At least one pair is required | JP-TSHIRT-BLK-M / 1 |
| SKU2 … SKU20 | Add further SKUs in order for multi-item orders | JP-MUG-WHT / 2 |
Using your own label
Set the channel to Upload_Shipping_Label and fill in 承运商 (carrier) and 物流跟踪号 (tracking number) as well. For orders that need no shipping service at all, use No_Shipping_Service.
JPCHBND03;JPCHBUY01;TEST). A mismatched pair fails the import.Note The template's 说明 sheet says a maximum of 10 SKUs, but the header row runs to SKU20. For orders with more than 10 SKUs, test with a small batch before importing at volume.Step 3: Upload and fix the errors
- Click Import on the list page, then 选择文件 (Choose file) under the template you're using and pick your xlsx.
- The page says the import is being processed. Imports run asynchronously — no result on the spot.
- Check the outcome in the Task Centre: the download icon at the top right, just right of the freight-estimate button.
| Status in the Task Centre | Meaning | What to do |
|---|---|---|
| Processing | Still running | Wait and refresh |
| Import completed | Everything went in | Check the new orders on the list |
| Import failed | Some rows failed validation | Click download the failure file — it spells out the reason per row |
Common causes: a name entered where a code belongs, a channel not bound to that warehouse, a country code that isn't on the list, a SKU that doesn't exist in that warehouse, or not enough available stock.
Note Don't re-upload the same file while it still says processing — the background job is still running and you'll end up with duplicate orders.Important Imported orders behave exactly like hand-keyed ones: where they go after submission depends on the channel. Yamato goes straight to Awaiting; Sagawa stops in Drafts → To be submitted and needs one more submit. See Method 1, Step 6 and Getting the label and tracking the shipment.Video coming soon
Once recorded, pass src (direct link) or embed (embed URL) to this component.