Baseline (stock on hand) import

The baseline is the book quantity — what your system says should be on the shelf — for one job. The work is split: the admin owns the template, the supervisor uploads the file.

The template (Settings → Import Templates → Baseline)

One template per organization:

• Match field — what do the codes in your file stand for: barcode (the default), sku, or externalId?
• Column mapping:
  • Must map: the code column and the quantity column
  • Can map: location, retail price, product name, description
  • Fix-up rules are only allowed on the code column
• Encoding, fixed-width layout, and so on — see File formats & encodings

No template yet? Uploads fall back to guessing standard column headers like code, barcode, sku, 商品码, 数量, qty, 货位, 品名, 描述.

Uploading (Supervisor, job page → Baseline)

1. Preview first. The first 50 rows are checked and labeled: matched, unmatched, ambiguous, or invalid. It's only a preview — nothing is filtered out of the real import.
2. Apply. The job's entire baseline is replaced in one go.

What "replace" really means

• Applying an import wipes the job's current baseline and loads every valid row — including codes that aren't in your product catalog.
• If the file lists the same code at the same location twice, the first row wins.
• No product lookup happens during import. Matching happens when reports run: the file's code (cleaned up) is compared against your catalog's barcode, SKU, or external ID — whichever match field you chose. If several products match, the first one created wins; if none match, the report shows the name and description from your file.
• Because each import remembers its own match field and file contents, old and new baselines never get mixed up.

Common problems

• Everything shows as unmatched? Usually the match field is wrong — the file has SKUs but the template says barcode — or a fix-up rule is missing (like dropping a check digit). Fix the template and upload again; the new upload fully replaces the old data.
• Fixed-width TXT rejected? Those files need a template with column widths filled in. There's no guessing.
• Garbled characters? Pick the right encoding in the template (for older Chinese systems, that's often gb18030).