Illustration of a warehouse feeding a product catalogue

Maintaining a large online catalogue by hand becomes difficult when several suppliers update their prices, stock or product ranges at different times. Even a good-looking store can become unreliable if product codes do not match, images go missing or availability is out of date.

We help businesses plan and build product catalogue integrations so their websites use information from the right source.

What a product feed can do

Depending on the supplier, a feed may provide product references, categories, sizes, colours, images, availability and prices. It may arrive through an API, spreadsheet, XML feed or another supported format.

We first check what the supplier actually provides. We then decide which fields should update automatically and which information your business should control locally.

For example, a supplier might own stock and cost prices while your website owns selling prices, margins, category descriptions and SEO copy. Automatically overwriting everything would erase valuable work.

How the catalogue should behave

A sound catalogue setup needs clear rules for:

  • New supplier products and items removed from the feed.
  • Duplicate SKUs across suppliers.
  • Variations such as colours and sizes.
  • Image changes and missing photographs.
  • Currency, VAT treatment and margin calculations.
  • Out-of-stock or discontinued items.
  • Products temporarily absent because a feed failed.
  • Notifications and error logs for staff.

These decisions are particularly important where thousands of products may be affected by one sync job.

One supplier or many?

A single documented supplier API is usually simpler than combining several suppliers with different identifiers and fields. When multiple suppliers sell the same item, we may need a separate mapping layer and a deliberate choice about price and availability.

For WooCommerce stores, read about WooCommerce API integrations. If customers need to request prices rather than pay online, the catalogue versus ecommerce guide may help.

A sample integration process

  1. Examine the supplier documentation and a representative sample of records.
  2. Agree which fields come from the supplier and which remain editable in the website.
  3. Test a small set of products, including variations and awkward edge cases.
  4. Define scheduled updates, validation and failure alerts.
  5. Reconcile the catalogue before enabling regular syncs.

More ecommerce services

What we need to scope your project

Approximate product count, number of suppliers, data formats, sample records, desired update frequency and whether the public website is a shop or quote catalogue.

Ask us about a supplier catalogue integration.