Purchase order import

Overview

Export the purchase order from your ERP as a spreadsheet and upload it on the Import page. Accepted files: CSV, TSV, TXT, XLSX and XLS (first sheet only). The header row may sit below a title or blank rows, blank lines and totals footers are ignored, and up to 500 styles fit in one file.

Each row is one stock keeping unit: a style, in one colour, in one size, with its quantity. Rows that share a style number become one product; rows that share a PO number become one purchase order. The column names below are recognised automatically, and any column can be re-mapped in the wizard before importing.

Download the template

Columns

Required columns are marked. A column is matched by any of its accepted header names (case, spaces and punctuation are ignored, so Order No_ and Order No. are the same).

Composition

Two spellings are read. Percentage first with fibre names: 60% Cotton - Organic 38% Cotton 2% Elastane. Or ISO fibre codes glued to percentages, as most ERPs export them: CO 60% CO38% EL2%. Decimal commas (60,5%) and separators between fibres are fine. Each component must sum to 100.

A garment with several components (a shell and a lining) is written as the components one after another: CO 100% PES 100%. The first component seeds the product; the rest are shown in the editor for you to place as layers.

Fibres outside the approved list are imported under their real name and flagged in the editor, never dropped. Codes the import knows:

Dates and countries

ETD and ETA accept ISO dates (2026-11-15), day-first dates with dashes or dots (15-11-2026, 1.6.2026) and slashes when the day is unambiguous. Both are stored as ISO dates. Two-digit years are not read.

Country of origin takes a country name or an ISO code (PT, CN); codes are expanded to names on import.

Barcodes and quantities

Barcodes are EAN or GTIN numbers of 8 to 14 digits; spaces and thousands separators are removed, and Excel number formatting is undone. A barcode per size is what lets a passport be published per size. Quantities are whole units; a decimal quantity is reported as a row error rather than rounded.

Images

An image cell holds one or more public https links separated by spaces, commas, semicolons or pipes. Links on rows of the same colour are combined, and the images are fetched and stored by Seamdex (public hosts only, up to 8 MB each, 24 images per import).

Suppliers and purchase orders

The supplier column may carry a name or your ERP vendor code. Once you edit a purchase order's supplier in Seamdex, that vendor code is remembered for your organization and the name is applied on the next import.

Supplier records themselves (capabilities, certificates, materials and partner access) are imported from their own file: see the supplier import guide.

One style belongs to one PO number within a file; a style listed under two PO numbers is refused before anything is written. Files with one purchase order per style import as such.

Prices and extra columns

Price columns (headers starting with RRP, Retail price, MSRP) are kept on the purchase order for reference and never shown on a passport. Any other column, such as brand or season, is left unmapped and ignored; the wizard lists them so nothing is dropped silently.

Checks before importing

After the file is read, the wizard shows what will happen: how many compositions parsed, unrecognised fibre codes, dates it could not read, country codes it will expand, barcode problems, and vendor codes it remembers. Rows with problems are listed with their spreadsheet line number, and the import is refused until they are fixed.

Importing through the API

The same rows can be sent as JSON from your systems. See the API documentation for the endpoint, its limits and the publish requirements.