Exports & integrations
Export: fields, formats, and column order
Thirteen fields, two formats, tap order as column order — and why the TXT export has no header row. Everything about getting data out.
The field picker
Exporting is a Field Pro feature, and it starts with a picker of thirteen fields:
barcode, type, name, category, status, notes, location_name,
location_lat, location_lng, scanned_at, scan_count, quantity and added_by.
Twelve are on by default; added_by is opt-in.
The order you tap them in is the order the columns come out in. That is the whole column-mapping interface — no template file, no settings page. Your selection and order are remembered for next time.
Two formats
- CSV — comma-separated, quoted per RFC 4180, with a header row. For spreadsheets and anything modern.
- TXT — tab-delimited, no header row. For software that predates the cloud: the TXT export exists because a real user needed a legacy importer to accept the file, and positional importers treat a header line as a bogus first record. Tab characters inside a value collapse to a space, because TXT has no quoting to hide behind.
Both use CRLF line endings, and both guard against spreadsheet formula injection: a cell
starting with =, +, - or @ is apostrophe-prefixed. Negative coordinates start
with a minus sign, so they arrive as '-33.8688 — strip the apostrophe if you parse
them as numbers.
Phone and browser produce the same file
The export you trigger on the phone and the export you trigger in the web dashboard are built by the same code and are byte-identical given the same data and field selection. There is no “the desktop version has more columns” — pick whichever surface you are at.
Quantity and scan count are different numbers and both export: quantity is how many you have; scan count is how many times a camera saw the barcode. Neither is derived from the other.
The machine-facing exception
The API’s GET /export/csv is a separate, fixed-format dump for scripts: twelve fixed
columns in a fixed order, group_id included, quantity and added_by absent, LF line
endings, no TXT variant, no picker. If you are wiring an automated nightly pull, read the
REST API quickstart — for a human handing a file to
another human or another program, the in-app export is the one you want.
Shaping a file for a specific importer
Order the columns to match what the receiving system expects, export, done. Two worked examples: every client’s stock, in one clean import for a legacy accounting importer, and restock once, update every channel for marketplace bulk uploads.