Any channel.
No connector required.
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.
Book a demo
TEMPLATE · RETAILER_NL_V3
$ nexera feeds run retailer-nl
→ building retailer_nl_v3 … 12,128 rows
→ validating schema … OK
→ connect sftp://feeds.retailer.nl:22 (key auth) … OK
→ upload catalog_nl_20260811.csv (8.4 MB) … OK
✓ delivered in 42s · next run 06:00 CET
Every partner wants
a different file.
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.
Their column names. Your data. No scripts.
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.
Reusable templates: clone retailer_nl_v3 to make the BE variant
Per-feed locale: the DE partner gets German copy automatically
Live preview over real catalog rows, before anything ships
Every dialect they ask for.
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.
CSV
Any delimiter (comma, semicolon, tab, pipe), quoted or raw, with or without header row. The dialect your partner already parses.
UTF-8
Latin-1
; , | tab
XML
Nested structures for comparison engines and marketplaces, including Google Shopping's RSS schema. Namespaces and CDATA handled.
nested nodes
CDATA
JSON
Clean arrays for modern endpoints and internal tooling. Pretty or minified, paginated or single file.
NDJSON
minified
XLSX
For the partner who lives in Excel. Typed columns, frozen header, ready to open. No "how do I import a CSV" call.
typed cells
gzip optional
Export at 04:00.
Sleep at 04:00.
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.
Sane presets plus full cron for the special cases
Pause, resume and run-now per feed
Failure alerts with the exact row and reason
feeds · scheduled
Ship the change, watch the pulse.
Delta-aware exports
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.
Health & history
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.
Atomic uploads. Paranoid on purpose.
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.
SSH keys managed in NEXERA, rotated without downtime
Retries with exponential backoff, then alert
Receipts you can forward when a partner says "we got nothing"
Middleware,
minus the middle.
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.
Bring their file spec.
Leave with the feed.
In a 30-minute walk-through, we’ll show you how NEXERA fits your catalog, your channels and the way your team works, giving you a clear view of how it can simplify your product data from day one.
Book a demo