Orders

Load the BackerKit shipping export, pick the Service Guids for this batch, then generate the warehouse packing list and the YunExpress import sheet.

1. BackerKit export

Drop the Shipping Address export here.xlsx or .csv · one column per item
No export loaded

2. Service Guids to ship

or drop a filter sheet (column "Service Guid")
GuidBackerCountryMethodItemsDeclaredProblems

SKU map

One row per BackerKit item column. The warehouse name goes on the packing list; the YunExpress SKU and declaration fields go on the import sheet. Items are combined into one declaration line only when they share a Merge group.

BackerKit columnWarehouse nameMeasure wordin/cmPackDeclareInsureBattery Merge groupYunExpress SKUUnit price $PiecesPack countUnit kgDeclared nameDeclared name (CN)HS code

Merge group: give related items the same group name (e.g. all glow-fob colours) and they are summed into one declaration line, using the declaration fields of the first row in that group that has a YunExpress SKU. Members can leave their own declaration fields empty.

Import sheet reads a spreadsheet with these column headings — Pack, Declare, Unit, Insure and Battery accept yes/no, y/n, true/false, 1/0, ✓/✗ or 否/off. A blank cell means no for Unit, Insure and Battery, and yes for Pack and Declare: only an explicit no turns those two off, whether the column is blank or missing entirely. Export sheet writes exactly this layout, so a file you export can be edited in Excel and imported straight back. Download template gives you the header row, plus a starter row for every export column that is not mapped yet.

Import accepts your existing "SKU - Shipping" sheet (SKU code, SKU, declared names, FOB, weight) and the two-column warehouse-name sheet; matching rows are updated, new codes are added. Rows greyed out are not present in the loaded export.

Tracking

Match a YunExpress tracking export back to the orders you generated, and write BackerKit's tracking import CSV. Matching is on the exact 客户订单号, so it only sees orders whose YunExpress sheet was generated from this campaign.

Drop a YunExpress tracking export.xlsx or .csv — order number from 客户订单号 / 参考号 / 订单号 / Customer Order No / Reference, tracking from 运单号 / 跟踪号 / 转单号 / Tracking No / Waybill

…or paste two columns, one shipment per line: order number, then tracking number, separated by a tab, comma or space.

Export

{tracking} is replaced with the tracking number.

Rows

Order numberGuidBacker IDE-mailTrackingStatus

Shipping & tax

How each order is routed and labelled on the YunExpress sheet.

Shipping method

The method code for every destination with nothing above it; the battery code is used when any item in the parcel has Battery ticked. Start typing for the YunExpress method list.

Method code, top wins: signature method → insured method → country override → default. A US address in the islands list reads the island field of each level first, and falls back to the general one when it is empty.

 

Country overrides

CountriesMethod codeBattery codeExtra service

Countries accept ISO codes or names, separated by commas, semicolons or new lines — a name with a space in it, like United Kingdom, stays one entry. "EU" expands to all EU members. The battery code is used when any item in the parcel has Battery ticked; leave it empty to route both the same way.

US islands

For US addresses in these states only. Mainland US resolves like every other country.

Each pair sits at one level of the ladder above: an island parcel takes the island field for its level and falls back to the general one when it is empty. A battery code is used when any item has Battery ticked; leave it empty to route both the same way.

Tax label

Shown in the review column of the YunExpress sheet, based on the declared total in USD.

CountriesModeRule

Threshold: label "under" when total ≤ threshold, otherwise "over". Bands: "limit:label" pairs, "*" for the rest.

Order & sender

Customer order number = Service Guid + suffix, e.g. 88ZENZSWGS.

Rules

Entries are "COUNTRY:value" separated by commas. A country is an ISO code; "EU" applies to every EU member and an exact country entry wins over it.

Package splitting

Declared value

Insurance & signature

The first row that names the destination decides both: the parcel is insured when the insured-items total reaches its Insure ≥, and asks for a signature when the order total reaches its Sign ≥. A blank cell never insures / never signs, and a country in no row does neither.

CountriesInsure ≥ $Sign ≥ $

Insured total = SKU map rows with Insure ticked, at their real unit price; the order total is everything the backer bought. Fixed uses one amount, By tier looks it up, Actual value insures the insured total itself rounded up to the next "Round up to" step (205 → 210) and capped by "Max amount". The amount goes to 自定义保价保额, the code to 保价服务, and the method codes (when set) to 运输方式代码 — the signature one beats the insured one, and both beat the country override and the default.

Declaration merge by country

In the listed countries the matching items are declared as one line under the rule's group, whatever their Merge group says. Everything else falls back to the SKU map.

CountriesGroupSKUs

SKUs are BackerKit column names, comma separated. * matches any run of characters, so CROWN-REFILL-* catches every refill variant. Matching ignores case, spaces and dash style.

Unit suffix on packing list

Applied only to SKUs with "Unit" ticked in the SKU map. Countries accept ISO codes or full names, separated by commas.

Settings

Campaign naming, packing-list layout and YunExpress sheet options. Export the configuration to back it up or to start a new campaign from it.

Campaign

Files are named prefix + date, e.g. ZEN发货20260901.xlsx.

Configuration

Those act on the active campaign; importing one creates a new campaign rather than overwriting this one.

Cloud sync

Keeps every campaign in a KV store behind this site, so another machine can pull the same setup. The token is stored in this browser only and is never part of an export. With a token saved this runs by itself: the cloud copy is checked on load and taken when it is newer (you are asked first if this browser has changes that never went up), and every change is pushed 1.5s later. The sidebar shows where it stands.

Not checked yet.

Packing list layout

YunExpress sheet