Supported import formats
CSV and JSON Lines through the published import contract — five entities, documented in full so you can check an export against it before you start. Shop and ERP connectors from the integrations directory cover the rest.
Switching to Zuduno
Move in controlled stages, not one big-bang cutover.
Map the sources, validate data in staging, compare the operating view and activate channels in a sequence your team controls.
The six stages
Each one has a decision in it, and the decision is yours.
- 01
Import
Products, variants, identifiers, inventory and orders come in from CSV, your shop or your ERP. Every import lands in staging first, never straight into the live record.
You decideWhich sources to bring, and in what order. Nothing is written until you say so.
- 02
Validate
Mappings, duplicates, missing identifiers and channel gaps are reported against the staged data, in full, before anything is committed.
You decideWhether to commit. You review the report; then you commit — or you don't.
- 03
Run in parallel
Your current system stays live. Zuduno's view of stock, readiness and orders sits beside it so the two can be compared on real data.
You decideHow long that runs. It ends when you trust the numbers, not when a plan says so.
- 04
Connect
Channels are activated one at a time. A channel goes live only when its readiness is green.
You decideWhich channel goes first. Usually the one with the rejection history.
- 05
Cut over
The operation moves when the data agrees — per channel, per market, rather than as one event.
You decideThe order and the schedule. A market that is not ready does not hold up one that is.
- 06
Export anytime
A full, machine-readable export of your tenant is available at any point in the process.
You decideNothing. This one is not conditional, and it stays true if you leave.
Implementation details
What we need from IT
A read-only export or API credentials per source. No changes to your systems of record, no agent installed anywhere, and no write access to anything until you activate a channel.
Rollback
Imports are staged and reversible by import id, so a bad mapping is undone rather than repaired by hand. Channels deactivate independently: switching one off does not touch the others.
Historical data
Orders and inventory history import with their original timestamps, so last year's numbers are still last year's after the move.
The implementation timeline is scoped from your catalogue structure, source systems, data quality, channels and market sequence. The proposal records the assumptions and decision points before migration starts.
Plan the migration around your operation.
Share the source systems, catalogue profile, channels and markets that belong in the first controlled scope.