Retail partners, comparison engines, ad networks, ERPs: if it accepts a file, NEXERA feeds it. Build the exact layout they ask for in a visual template editor, schedule it cron-precise, and deliver it over SFTP or HTTPS with retries, checksums and a receipt for every run.
The wholesale partner wants semicolon-separated CSV in Latin-1 with their column names. The comparison engine wants XML with nested categories. The ad network wants JSON. The distributor still opens everything in Excel. None of them will change for you.
NEXERA treats file feeds as first-class channels: each one gets a template, a format, a schedule and a delivery target. The data comes from the same governed catalog as your Shopify sync, so the file is right for the same reason everything else is right.
Map any PIM field to any output column, in their naming, their order, their locale. Transformations are built in: truncate, round, uppercase, fallback chains, unit conversion, concatenation. A live preview renders real products as you build, so surprises happen in the editor, not at the partner.
The format is a dropdown, not a project. Delimiters, encodings, escaping, compression: configured per feed, handled correctly, tested against the partners who are pickiest about it.
Any delimiter (comma, semicolon, tab, pipe), quoted or raw, with or without header row. The dialect your partner already parses.
Nested structures for comparison engines and marketplaces, including Google Shopping's RSS schema. Namespaces and CDATA handled.
Clean arrays for modern endpoints and internal tooling. Pretty or minified, paginated or single file.
For the partner who lives in Excel. Typed columns, frozen header, ready to open. No "how do I import a CSV" call.
Every feed has its own recurrence: nightly, hourly, every 15 minutes, or a custom cron line, all in your timezone. Pre-flight validation runs on every scheduled build. If a run fails, you hear about it by email, Slack or webhook, and the previous file stays in place.
Files upload under a temporary name and rename into place only when complete, so a partner's importer can never read half a feed. SSH-key auth, host-key pinning, automatic retries with backoff, and a stored receipt (timestamp, size, checksum) for every single delivery. HTTPS PUT/POST for partners who prefer an endpoint.
Full catalog at night, deltas in between. The same content-hash engine behind syndication knows exactly which rows changed since the last run and ships only those. Payloads shrink by ~97%, partners parse in seconds, nobody throttles you.
Every run logs row counts, duration, outcome and delivery receipt. A failed delivery or a suspicious row-count drop (yesterday 12,128, today 118) alerts your team before the partner notices anything.
Middleware syncs a copy of a copy. Scripts rot the day their author leaves. NEXERA feeds are part of the catalog itself: same data, same rules, same audit trail.
A 30-minute walk-through. Bring one partner's feed requirements, we build the template live, schedule it, and deliver the first file to a test SFTP while you watch.