Integration
CSV & SFTP and Zuduno
The published import contract, over a file. Five entities — orders, lines, refunds, customers and products — as CSV or JSON Lines, dropped on SFTP or uploaded directly. Every file lands in staging and is previewed before it is committed, and a committed import is reversible by its import id. A platform with no API is still an integration.
What syncs
Four things move, and the arrow says which way.
Nothing here is maintained separately. What arrives lands on the same records every channel is served from.
- Products
- Zuduno receives.Products arrive as the canonical record, or as an update to one Zuduno already holds.
- Inventory
- Zuduno receives.On-hand by location arrives and lands on the same records the channels read from.
- Orders
- Zuduno receives.Orders and their exceptions land in the same worklist as every other source.
- Prices
- Zuduno receives.Prices arrive with the product data and become part of the record.
Markets
Where this one applies.
European Union
Markets, not marketplaces. The same channel can serve two countries whose rules differ, and readiness resolves against the country.
Readiness
What it supplies to the checks.
- Required attributes for each product type, as the source provides them
- Identifiers — GTIN, EAN, SKU, MPN — validated on arrival
- Compliance fields the market requires, carried on the record rather than in a document
- Category values, mapped to Zuduno's taxonomy on import
What it needs from you
Credentials, and nothing else.
A file your system can already produce, or an endpoint that can post one. No changes to your systems of record.
Known limitations
What this one does not do.
- It does not write anything back. A source feeds Zuduno; publishing is a channel's job.
- It does not transform your data beyond the mapping you approve at import.
- It does not accept a file that fails validation — the import is staged, reported and discarded.
Evaluate CSV & SFTP in your operating scope.
Confirm the data flows, markets, account permissions and readiness rules your implementation requires.