Collection allow more fine grain control over products in terms of manually sequencing them, allowing shared characteristics like special price for a select customer audience (like a buyer), keeping a collection private and secure and any custom action one may want on a group of products as a collection.

For display purposes we may choose to show Products part of a Collection. However we may not want to invest time defining a permanent hierarchy or even care about that. More so need the ability to Sequence and control attributes around the collection in addition to the products that combine to form the collection. If your project supports campaigns, please refer to the Campaign section for more documentation.
Do not confuse this with a Business campaign or a landing Page showing a bunch or products.
Impacts: Display of a Catalog or Collection usually, Indexing taxonomy for showing Search results for a Collection.
Admin: Catalog > Collections

Geek Stuff!

A Collection is a Product with additional special attributes. It shares the same data model as Product. The products in the collection use the field related Groups in the Product data model. The attribute Key/Name can be a name for the collection attribute or a composite key in <Collection Attrib Name>-<Product Code> form, that can represent the collection and a product within the collection.

Collections should be avoided if your requirements are simpler and can be met by any of the other categorization / relation methods available in Catalog. The reason is that Collection's are designed to accelerate custom needs on a group of products. It incurs additional project level maintenance overheads, design considerations, data and performance overheads; since it requires manual curation, your time and effort to maintain them.

Catalog Collections Dashboard

Collection Types

More sophisticated projects, may need to define different types of Collections with different attributes. For example lets assume a hypothetical scenario where a set of Collections is intended for Lookbooks, while another for selling. Clearly, the collections for selling will have some custom requirements that may not be shared with the ones for a lookbook. By default, the collection types dropdown list has one item. But the list is provided to accommodate future upgrades for the project if it requires.

Collection Dashboard

On selecting a Collection Type, a dashboard appears that shows all the collections within the type. The Excel export feature will also export this list (as you see on your screen).

Collection Details

Catalog Collections Details

On selecting a collection from the dashboard view, you will see a collection details view. This view will contain some standard fields and all the custom fields for your collection type. The standard fields include:

Other than the standard fields, we can customize the collection type to include any number of custom fields. However of interest are Metric, Meta or Tracking fields. These are custom fields, however they have special significance. It is important to understand the difference in these metrics.

Actions on Collections

You can save or delete a collection. Actions are controlled by authorization policies defined in the User module.

Please refer to Cache & Index to understand some internal behaviors of a Save action, if you notice a save is not immediately resulting in the changes you intended. It could be related to the Index or Cache.

Disable or Suspend a Collection

Disable a collection
One can disable and enable a Collection by using the Disable Toggle action. It will toggle the Disabled state. A disabled collection will also show a warning sign when you open it in the details panel. Additionally, they can also be spotted in the listing panel with a grey background around key columns.

How a disabled collection maybe interpreted is application specific, by default it will cause an Authorization error and be directed to an Unauthorized or Validation landing page. Similar to how the application will respond incase of a private link unauthorized access.

Cache & Index

Caching and Inexing are techniques used to improve performance to the end user who views your website. Learn more here.

Collections, are a type of Product and hence subject to the same rule. For convenience sake we have provided an automatic trigger on the index and cache when you save a collection so no additional measures are required. However this may differ from project to project based on the data size and impact of caching and indexing on the system.

Misc Screenshots

Back to Top