Supported formats
Šis saturs vēl nav pieejams jūsu valodā.
CatalogRelay imports CSV, XML, and JSON. Connection type (HTTP, FTP/SFTP, paginated API, spreadsheet) is separate from file format.
Most common supplier format. Header row becomes mappable columns.
sku,name,price,stock,eanABC123,Widget Pro,29.99,45,5901234123457DEF456,Gadget Plus,49.99,0,5901234123464European number formats can be normalized via mapping transforms.
Common for distributors and ERP exports. During mapping you may set the row element (repeating product tag). Child nodes become columns.
<catalog> <products> <product> <sku>ABC123</sku> <name>Widget Pro</name> <price>29.99</price> <stock>45</stock> <ean>5901234123457</ean> </product> </products></catalog>Typical for modern APIs and file exports. Arrays of product objects are flattened into columns for mapping.
{ "data": { "products": [ { "sku": "ABC123", "name": "Widget Pro", "price": 29.99, "stock": 45 } ] }}Paginated API (connection type)
Section titled “Paginated API (connection type)”Not a fourth file format. Use the Paginated API tab when the supplier serves CSV/XML/JSON page by page. Configure auth, page parameter, and max pages; probe + map as usual.
Spreadsheets
Section titled “Spreadsheets”Google Sheets and Excel Online are fetched as CSV via a public share link. See Connecting a data source.
Encoding & size
Section titled “Encoding & size”Feeds are processed in streaming chunks. Prefer UTF-8. Very large catalogues are supported; slow supplier servers may hit download timeouts — contact support if needed.