Simplifying Catalog Updates: Relying on Static Product Feeds vs Using Topsort's Catalog API

Efficient Catalog Management with Topsort

At Topsort, we offer clients two primary methods for updating their catalogs: static product feeds and integration with our Catalog API. Each option has its advantages, allowing clients to choose the approach that best suits their requirements and preferences.

Static Product Feeds: 

Using static product feeds simplifies the integration process by providing a straightforward method for updating catalog entities. Clients can periodically supply a file or URL containing all relevant catalog information, including vendors, products, and categories. This method is particularly beneficial for catalogs with infrequent updates or smaller sizes.You can follow this documentation Product Feed (Recommended) to know the format on which to provide the feed file.

For Clients with Larger Catalogs: 

For clients with larger catalogs, static product feeds remain a viable option, especially when provided via URL and in formats such as CSV, TSV, or JSONL. This approach enables efficient catalog updates without overwhelming resources or introducing unnecessary latency.

Frequent Catalog Changes: 

In cases where catalogs undergo frequent changes, especially with regular additions of new products, clients may opt to utilize Topsort's upsert endpoints (Delete Vendors, Upsert Products and Upsert Categories). This method allows for lighter syncs, focusing on updating only vendors onboarded to Topsort and modifying or adding new products as necessary.

At Topsort, we ensure efficient catalog synchronization by employing various methods tailored to each client's needs. Whether clients choose static product feeds or integration with our Catalog API, we strive to facilitate timely updates and maintain accurate representation of catalog entities within our platform.