Custom tabular export
Map a stable spreadsheet-style export during assisted onboarding.
When to use it
A practical fit for your existing workflow.
ERP, PIM, and legacy back-office exports that cannot yet emit the standard Legend headings.
Input contract
Fields and structure
Use stable field names and meanings across every refresh. Legend normalizes the values, but the source contract should not drift silently.
Required or expected
Stable header rowMerchant SKUProduct titlePriceCurrencyProduct URL
Recommended fields
Barcode or GTINBrandBottle sizeStockDeliveryImage URL
Supported variations
- CSV, TSV, or spreadsheet-style source
- One approved mapping per source
- Fixed worksheet and header row
- Documented stock conventions
Copyable example
Custom column export
Replace the demonstration values with your own catalogue data. No customer, order, or payment data belongs in an inventory feed.
CSV
Item Code,Product Name,EAN,Pack,Web Price,Currency,Available,Product Page
DEMO-001,Legend Demo Single Malt,5010327000142,70cl,39.50,GBP,Yes,https://merchant.example/products/demo-001From source to live offer
Connection workflow
Every route uses the same quality gates before an offer becomes public.
Send a representative export with no sensitive customer data.
Agree a field map and stock conventions.
Validate a full snapshot and review unmatched products.
Lock the mapping before scheduled production imports begin.
Before publication
Validation checklist
These checks keep bad prices, stale stock, and uncertain product matches out of the public marketplace.
- Custom mapping is an assisted pilot.
- Column names and meanings must remain stable.
- Macros and executable spreadsheet content are not required.
- Changes to the export contract trigger a new validation review.
Other connection paths