Where data comes from

File upload, URL, FTP, JSON endpoint or a connected store — and the difference between a product import and a price and stock sync.

Products can arrive four ways. The choice is made once, and every subsequent run re-reads the same source.

File upload

Upload a CSV directly. Your original filename is kept, so a month later it is still obvious which export it was. A re-run of an upload-sourced import needs a fresh upload — there is nothing for MarketplaceHub to go and fetch.

URL

A location your supplier or ERP publishes to. Each run collects whatever is there at the time, which makes this the usual choice for a scheduled import.

FTP

The same as a URL, with credentials. Each run connects and collects the current file.

JSON endpoint

An API that returns your products. It is read like any other feed — the shape is mapped to system fields the same way a CSV's columns are, so there is no middleware to write.

Or skip files entirely

If your products already live in a connected Shopify, Etsy, Amazon or eBay account, import from there directly. No export step, and products arrive carrying the category the source marketplace already filed them under — which lets classification be skipped entirely when you are publishing back to the same platform and country. See Marketplace integrations.

A note on fetched URLs

URLs you supply are fetched through a path that resolves the host and refuses to connect to private or reserved addresses. This is checked at connection time and on every scheduled re-fetch, including after redirects, so a host cannot pass validation during setup and later resolve somewhere internal.

Two kinds of import

There are two, and they are configured separately because they do different work:

• Product import — brings products in, classifies them and publishes listings.
• Price and stock sync — updates numbers on products that already exist. No AI, no publishing. See the price and stock feed.