A: Product attributes are used to define the characteristics of individual products that a merchant is sourcing or selling. These attributes include information such as Brand, Color, Size, Vendor ID, UPC, SKU, Images and other details commonly displayed on a Product details page (PDP).
On the other hand, Category attributes are used to define the characteristics of categories used by merchants to manage catalogs. These attributes are not associated with products but rather define the properties of the categories themselves. For instance, if a merchant wants to display an image on a Category List Page (CLP) for a particular category, they can include a category attribute that contains the corresponding image URL.
A: No, once products have been assigned to a category level, that level becomes a leaf category, and it is not possible to add further levels to it.
A: Collections represent multiple merchandising objectives, including organizational needs, regional and channel assortments, and marketing campaigns. Products are assigned to collections based on predefined rules for each collection. These rules can involve category inclusion or exclusion as well as attribute specifications. Collections are frequently employed for events like seasonal sales.
Q: Can I bulk import all of my product from my current catalog management system into fabric Products?
A: Yes, you can. fabric Products offers a convenient bulk import functionality, enabling you to effortlessly import your product data using a CSV file. Additionally, you have the option to download a template that precisely outlines the required format for a seamless and successful import process.
A: Typically, when making individual edits, it takes approximately a minute for the product data to be displayed in Offers service. However, when performing a bulk import of products through a file, the synchronization time for the product catalog within Offers can range from several minutes to up to an hour.
Q: I want to make sure a specific attribute is always present and has a value for every single product in my catalog. How do I enforce?
A: You have the flexibility to designate an attribute as mandatory for the entire catalog. However, it is advisable to establish these mandatory rules during the initial catalog configuration to avoid the hassle of filling in missing data later on. In Copilot, when viewing the attribute, simply select "Yes" to the prompt "Is this attribute mandatory." Alternatively, when creating or updating the attribute through API, you can set
required": true. This configuration blocks any products from being published unless all mandatory attributes contain values.
To create variants of a product, you have multiple options: utilizing the Product API, the Copilot UI, or performing a bulk CSV import through S3. When creating a new variant, ensure to input the necessary attribute fields based on the desired category association and specify the parent product. If you wish for the variant to inherit some or all attribute values from the parent product, you have the option to do so.
See specific instructions for creating a variant in Copilot - V2 and V3, S3 bulk import - V2 and V3, or API - V2 and V3.
Q: I need product data to be fed to a non-fabric system, like a Content Management System. Can I subscribe to events for Product?
A: Yes, you can subscribe to Products events you need for one or more non-fabric systems. Available Products events are: product create, update, and delete. Details on how to subscribe can be found here for V2.
A: There are no restrictions or limitations on the number of categories you can have.
A: You have the ability to limit edit access to Products by assigning specific roles to individual users. Only those with the Products editor role are granted permission to make changes to products.