Supplier XML feeds and APIs, read properly.
Some suppliers publish a link or an API instead of a spreadsheet. Every one of them structures it differently, so OhoSync reads each with a reader written for that supplier rather than guessing at a generic mapping.
Updated
Short answer
OhoSync supports XML feeds and supplier APIs for suppliers it has a reader for. Send a sample of your supplier's feed and you get a straight answer on whether it works today, what would be involved, or that it is not a fit. CSV and Excel files work with any supplier.
Why a reader per supplier
An XML feed is not a format so much as a family of them: one supplier nests variants inside products, another lists every colour as its own product, a third sends prices in a separate file. A generic importer pushes that work onto you. A reader built for the supplier turns their structure into the same standard set of fields everything else in OhoSync works on, so pricing rules, product selection and locks behave identically whatever the source.
Supplier logins stay encrypted
Where a supplier's API needs a login, it is stored encrypted and only used to read the catalogue. OhoSync never places orders through a supplier's API.
Large feeds
Feeds are streamed rather than loaded whole, with a ceiling of 100 MB per file. Where a supplier API is slow for full product records, the reader fetches only stock and price on each run and refreshes texts and images less often, so a stock update takes seconds.
Questions
Is JSON supported?
Where a supplier publishes JSON through an API, yes, with a reader for that supplier. There is no generic JSON column mapper; spreadsheets are the generic route.
My supplier is not listed. What now?
Send us a sample or the feed link. You will hear whether it works today, what would be involved, or that it is not a fit.
Try it on your own products.
Free for up to 30 products, no credit card. Founding shops get 50% off any paid plan for the first 6 months with code FOUNDING50 (first 100 shops, until 31 March 2027).