A supplier product feed connects your store or selling system to catalog information such as product titles, descriptions, images, prices, stock and variants. The format matters because it affects how quickly your listings can be launched, how reliably inventory can be updated and how much maintenance your team will need.

What is a supplier product feed?

A product feed is a structured file or connection that transfers supplier catalog data into another system. Depending on the arrangement, it may include core product information, stock levels, pricing, media, variants, shipping attributes and identifiers such as SKUs or barcodes.

A feed does not automatically guarantee clean or complete data. Before integrating, check which fields are supplied, how often they change, whether discontinued products are removed and how errors are communicated.

  • Product titles, descriptions and specifications
  • Images and image URLs
  • Variants, sizes, colours and product identifiers
  • Stock availability and price fields
  • Categories, weights and other fulfilment data

CSV: simple and accessible

CSV is a tabular format that can be opened and reviewed in spreadsheet software. It is often a practical starting point when you are testing a range, importing products once or working with a modest catalog.

Its main limitation is that a CSV file is usually a snapshot. If the supplier sends a replacement file on a schedule, your store needs a repeatable process for importing changes, updating stock and handling products that no longer appear. Manual spreadsheet editing can also introduce formatting and mapping errors.

  • Choose CSV when you need a straightforward initial catalog import.
  • Ask whether the file is delivered once or refreshed on a defined schedule.
  • Confirm delimiter, encoding, column names, image links and variant structure.
  • Create rules for price, stock and discontinued-item updates before publishing products.

XML: structured scheduled data

XML represents data in a hierarchical structure, which can accommodate grouped products, variants and nested attributes more naturally than a basic table. It is commonly suited to automated, scheduled imports where a store or middleware system regularly retrieves and processes a feed.

XML is not automatically easier to integrate. Different suppliers can use different element names, optional fields and category structures. Your system may need a mapping layer, validation and handling for malformed or incomplete records.

  • Choose XML when the catalog has structured attributes or complex variants.
  • Request documentation for elements, required fields and update conventions.
  • Validate the feed before importing it into your live catalog.
  • Check how deletions, unavailable products, stock changes and image updates are represented.

API: real-time integration potential

An API lets one system request or exchange data with another through defined endpoints. Compared with file-based feeds, it can support more frequent synchronization and more targeted requests, such as retrieving a specific product or checking current availability before accepting an order.

The flexibility comes with greater implementation responsibility. You may need authentication, rate-limit handling, logging, retries, version management and monitoring for failed requests. An API also requires the supplier to document the available operations and data fields.

  • Choose an API when inventory or pricing changes frequently and automation is important.
  • Confirm whether the API supports product, stock, price and order operations or only selected data.
  • Check request limits, response formats, authentication method and error handling.
  • Plan for outages, timeouts and API version changes rather than assuming continuous availability.

A practical comparison

The best format is the one that matches your operating model, not necessarily the most technically advanced option. A small store validating a product range may gain little from building a full API integration. A high-volume operation with frequent stock changes may spend more time correcting stale files than it would have spent on a robust automated connection.

Treat the feed format as one part of supplier selection. You should also evaluate data completeness, update schedule, order processing, returns information, shipping coverage and the fit between the supplier's catalog and your sales channels.

  • Setup effort: CSV is generally lowest, XML is moderate, and API usually requires the most development.
  • Update control: CSV depends heavily on file delivery and import routines; XML supports scheduled processing; API can support frequent requests if the supplier's system allows it.
  • Data complexity: CSV works well for flat tables, XML handles hierarchy, and APIs can expose flexible resources and actions.
  • Maintenance: all formats need monitoring, but APIs usually require more technical oversight.
  • Scalability: recurring automated workflows matter more than the file extension alone.

Questions to ask before choosing a feed

Request a sample feed or technical specification before committing to an integration. Test it against a staging store with real product variations, missing values and stock changes rather than checking only a few ideal records.

Also establish ownership. Decide who maps categories, cleans descriptions, manages images, sets retail pricing and removes unavailable products. A technically successful import can still create a poor storefront if these responsibilities are unclear.

  • How often are product, price and inventory fields updated?
  • Are stock quantities provided, or only in-stock and out-of-stock statuses?
  • How are variants, bundles, backorders and discontinued products represented?
  • Are images hosted by the supplier, and may they be downloaded or reused?
  • Which identifiers remain stable between updates?
  • Is there documentation, a test environment or technical support for the integration?
  • Can the feed be used with your ecommerce platform, marketplace or order-management system?

What public supplier data suggests

In the published aggregated directory data as of 3 September 2026, wholesale capability appears across approximately 96% of listed suppliers and dropshipping across approximately 89%. Feed formats are much less commonly disclosed: API capability is listed for approximately 3%, CSV for approximately 2% and XML for approximately 1%. These figures are directory-level indicators, not guarantees that every supplier offers a format or that an undisclosed capability is unavailable.

The same data covers approximately 1,056 suppliers across 27 countries and 45 categories. The largest represented groups include dropshippers at approximately 85% of supplier types, with fashion, electronics, lingerie, home and living, wholesale and accessories among the larger category groupings. Use these figures to understand the breadth of the market, then confirm the exact integration options for suppliers relevant to your category and destination markets.

  • Treat published capability percentages as indicative and aggregated.
  • Confirm feed format, field coverage and update schedule directly during evaluation.
  • Do not select a supplier solely because it supports CSV, XML or API.
  • Keep supplier identities and contact details as part of your private sourcing workflow.

Frequently asked questions

Is an API always better than CSV or XML?

No. An API can support flexible and frequent synchronization, but it may be unnecessarily complex for a small catalog or infrequent updates. A well-managed CSV or XML workflow can be more appropriate when the data changes less often.

Can I use a CSV feed for automatic inventory updates?

Yes, if the file is refreshed and your ecommerce system or middleware can import it automatically. Confirm the delivery schedule, stable identifiers and how the file indicates stock changes and discontinued products.

What should a product feed contain?

At minimum, look for stable SKUs, product names, descriptions, variants, images, prices and availability. Depending on your workflow, you may also need weights, dimensions, categories, barcodes, shipping attributes and order-related data.

How do I test a supplier feed?

Use a staging environment. Import a representative sample, including products with variants and missing fields, then test price changes, stock changes, image updates and product removals before publishing anything to customers.

How common are CSV, XML and API capabilities?

In the supplied aggregated directory data dated 3 September 2026, API capability is listed for approximately 3% of suppliers, CSV for approximately 2% and XML for approximately 1%. These are published, rounded indicators and should not be treated as a complete market census or a guarantee for an individual supplier.