What you can import
The wizard handles six kinds of master data:| Entity | What it covers |
|---|---|
| Customers | The buyers you sell to, with their default terms. |
| Vendors | Factories and suppliers, each typed as a garment factory, fabric mill, or accessory supplier. |
| Fabric masters | Your catalog of fabrics (main materials). |
| Accessory masters | Your catalog of trims and accessories. |
| Colors | The shared color list used to build colorways. |
| Units | Units of measure (such as yards or pieces). |
Import in dependency order
Some records refer to others, so import them in this order:- Units and colors first. These are referenced by other records and stand on their own.
- Vendors second. A fabric or accessory master can name its vendor, and that vendor must already exist.
- Fabric and accessory masters last. They reference vendors, categories, and units.
Preparing your data
For each entity, download the template from the wizard. The template is a CSV with the correct column headers and a couple of sample rows. Fill in your data under those headers — keep the header row exactly as provided.The match key
Every entity has a match key — the column the wizard uses to tell whether a row is a new record or one that already exists:| Entity | Match key |
|---|---|
| Customers | name |
| Vendors | name |
| Fabric masters | article_no |
| Accessory masters | item_code |
| Colors | name_en |
| Units | code |
RI-026A and RI026A are treated as the same item.
Everyone else matches on the plain name or code, ignoring case and surrounding
spaces.
Columns by entity
The tables below list each column and whether it’s required. Anything not marked required is optional. Customers — match keyname:
| Column | Required | Notes |
|---|---|---|
code | Yes | Unique customer code |
name | Yes | Customer or brand name |
country, address, notes | No | Contact and free-text detail |
payment_terms_days | No | Net payment days (e.g. 30) |
default_trade_term | No | Default trade term (e.g. FOB) |
default_destination | No | Default ship-to destination |
name:
| Column | Required | Notes |
|---|---|---|
name | Yes | Vendor or factory name |
vendor_type | Yes | Garment factory, fabric mill, or accessory supplier |
code, country, address | No | Identification and location |
contact_name, contact_email, contact_phone | No | Primary contact |
currency, payment_terms | No | Commercial defaults |
article_no:
| Column | Required | Notes |
|---|---|---|
article_no | Yes | Article number (match key) |
description, content, finish, weave, weight | No | Fabric specification |
width_inches, gsm | No | Width and weight per area |
lead_time_days, moq, mcq | No | Sourcing terms |
standard_cost, currency | No | Cost and its currency |
min_stock_qty | No | Reorder level |
vendor | No | Fabric mill (must already exist) |
category, unit | No | Created automatically if new |
item_code:
| Column | Required | Notes |
|---|---|---|
item_code | Yes | Item code (match key) |
item_name | Yes | Item name |
colour, size_spec | No | Description |
moq, lead_time_days | No | Sourcing terms |
vendor_quote_price, customer_quote_price, budget_price | No | Pricing (with matching currency columns) |
min_stock_qty | No | Reorder level |
vendor | No | Accessory supplier (must already exist) |
category, unit | No | Created automatically if new |
name_en:
| Column | Required | Notes |
|---|---|---|
code | Yes | Color code |
name_en | Yes | English color name (match key) |
name_zh | No | Chinese color name |
code:
| Column | Required | Notes |
|---|---|---|
code | Yes | Unit code (e.g. YDS) |
description | No | Description |
A note on file encoding
Save your file as CSV. UTF-8 is recommended, but files saved from a Chinese-locale copy of Excel (Big5 or GBK) are also accepted — the wizard detects the encoding for you, so Chinese names import correctly either way.Two import modes
The wizard offers two modes. Choose the one that matches what you’re doing:- Create only — every row must be a new record. If a row matches an existing record, it’s reported as an error. Use this for initial onboarding, when the workspace is empty and every row should be new.
- Fill blanks — for rows that match an existing record, only the empty fields are filled in; a field that already has a value is never overwritten. Use this to enrich existing records — for example, adding lead times or vendors to masters you imported earlier.
Running the import
- Open Settings → Data Import.
- Pick the entity you’re importing.
- Download the template and fill it in with your data.
- Choose the mode — “Create only” or “Fill blanks”.
- Upload your completed file.
- Review the preview — the wizard parses and validates every row without saving anything yet (see below).
- Fix any errors and re-upload until the preview is clean.
- Commit. The wizard writes the data and shows a summary of how many records were created, enriched, and added by reference.
Reading the preview
The preview validates your whole file before anything is saved. It shows each row and flags any problems in a per-row table, telling you the row, the column, and what’s wrong — a missing required field, a vendor that doesn’t exist, a duplicate in “Create only” mode. The import is all-or-nothing: if even one row has an error, nothing is saved. Fix the flagged rows in your file and upload it again. This means you never end up with a half-imported file to untangle.Minted on reference
On a master row, thevendor, category, and unit columns refer to other
records by name or code:
- A vendor must already exist — that’s why you import vendors before masters. A master naming an unknown vendor is reported as an error.
- A category or unit is created automatically if it doesn’t exist yet — this is “minting on reference”. A unit created this way is identical to one you’d import through the units template, so you don’t have to pre-create every category and unit by hand.
After the import
- Verify the counts. The result summary tells you how many records were created and enriched — check it against what you expected from your file.
- Spot-check a few records in the relevant module to confirm the data landed where you expected.
- Continue in order. If you’re onboarding from scratch, run units and colors, then vendors, then the fabric and accessory masters — so each step’s references are already in place.