These are the known limitations of the Catsy integration for iPaaS.com. They are inherent to the current design of the integration and to the capabilities of the Catsy API, and they apply to all subscribers.
Platform Scope and Tested Versions
Built for: Catsy, the product information management (PIM) platform, at https://api.catsy.com/.
API generations used: the integration works with Catsy's current production endpoints, which span both the v3 and v4 generations of the Catsy API.
Last validated: end-to-end against Catsy's documented production endpoints in July 2026.
Not built for: any other vendor's PIM, e-commerce, or catalog product. If Catsy introduces a separate product line or a materially different API generation in the future, this integration will not automatically support it.
1. Initialization Is Not Supported
Initialization — a bulk import of all existing Catsy records the first time the subscription connects — is not supported. Records are brought into iPaaS.com through the scheduled product and category polls and through Manual Sync.
What this means for you: To bring existing Catsy data into iPaaS.com, run the product and category polls or use the Manual Sync page to transfer specific records by ID. There is no single action that imports the entire Catsy catalog at once. This is expected at the time this documentation was written.
2. Changes Are Detected on a Polling Schedule
The integration detects new and changed Catsy products and categories on its polling schedule rather than through instant event notifications. The Product Poll Search Days setting controls how far back the first product poll looks for changes.
What this means for you: A new or updated Catsy record appears in iPaaS.com on the next scheduled poll, so there may be a short delay between a change in Catsy and its appearance in iPaaS.com. You can also transfer a specific record immediately from the Manual Sync page. This is expected at the time this documentation was written.
3. Category and Collection IDs Require a Type Prefix
Catsy organizes products under both categories and collections, and both are transferred into iPaaS.com as categories. Each record's type is identified by a prefix on its ID — Cat for a category and Col for a collection — and the prefix is case-sensitive.
What this means for you: When you transfer a category or collection from the Manual Sync page, enter the full ID including its prefix (for example, Cat4000696937 or Col4000012345) with exact casing. An ID that does not begin with Cat or Col is rejected. This is expected at the time this documentation was written.
4. Deletions Are Not Synchronized
When a product, category, or collection is deleted in Catsy, that deletion is not propagated to iPaaS.com. The integration transfers additions and updates only.
What this means for you: If you remove a record in Catsy, remove the corresponding record in iPaaS.com separately if you want the two systems to match. This is expected at the time this documentation was written.
5. Category Sets Are Not Synchronized
Catsy category sets — groupings that organize categories — are outside the scope of this integration. Categories and collections are transferred, but the category sets that group them are not.
What this means for you: Manage category sets directly in Catsy. They are not created or updated in iPaaS.com by this integration. This is expected at the time this documentation was written.
This document covers 5 known limitations. For detailed, per-flow behavior, see the individual mapping collection descriptions in the iPaaS.com mapping configuration.