Category Configuration
Each category in Shoppie requires its own configuration. This approach provides greater flexibility in how categories are managed, displayed, and customized. It also reflects certain Atlassian platform limitations that currently prevent shared configuration across multiple categories.
The Setting tab is divided into five sections, each offering specific configuration options: Category Image, Default Attributes, Category Details, Product Settings, and Advanced Settings.
Category Image
Product images are managed through Assets. The displayed image is the product’s avatar. More details are available on this page → Display Options (Products).
The category image is displayed on the landing page when the shop catalog opens.
It is automatically selected from one of the product images within the category, but it is possible to replace from the list of product in that category. If no product images are available, a default image is shown instead.
Product Attributes
Two key attributes are defined in this section:
Name (Required): serves as the product name. The default Name attribute is preselected, but it can be changed.
Price (Optional): Only float and integer attributes are available for price selection. This field can be left empty when the shop use case does not require prices, such as onboarding scenarios where items are preselected for the logged-in user and no budget is defined.
Category Details
In Category Details, options specific to each category can be customized:
Name & Icon: Retrieved from Assets by default, but both can be changed.
No price text: Text to display if the price is not configured or if a product has an empty value.
Limit to One Item Selection: Restricts the category so only one item can be selected.
Display Options
Display Options control how product information appears to users, both on the product card in the catalog list and on the product details view. These settings help ensure each category shows the most relevant information at the right level of detail, making it easier for users to compare products and find what they need.
Product card attributes: choose up to three attributes to display on the product card, giving users a quick summary before they open the full product details.
Product description: highlight key text based attributes to give users essential product information at a glance within the details view.
Product specifications: display concise technical details and features, with the option to enable filtering on selected attributes.
More details about each feature are available on their dedicated documentation page.
Product Features
Each category supports a set of features that can be configured to improve how products are displayed in shop. These features improve the user experience and help ensure accurate product information is shown.
In Stock: configures an attribute used to automatically display stock status, such as Out of Stock, Pre-order, or Only 4 left. This helps provide real-time inventory visibility.
Recommended Products: displays related products in the product details view and cart, suggesting complementary items and improving the shopping experience.
Advanced Filtering: allows users to filter products within a category by specific attributes, such as price, brand, or specifications. This makes it easier for users to quickly find the exact product they're looking for.
Product Variants: groups similar products, such as different sizes or colors of the same item, into a single product listing with selectable options. This keeps the catalog organized and simplifies the browsing experience.
More details about features are available on their dedicated documentation pages.
Advanced settings
Advanced settings provides additional customization options to accommodate advanced use cases and scenarios.
Object schema and Object type: these are used for informational purposes and cannot be edited here. They are defined during the catalog creation process, where assets are synced with the catalog.
Custom field to map to: map the category to an existing Assets custom field. Multiple object types can be assigned to a category. Objects from this category will be saved in the specified 'Assets' custom field when a customer request is submitted. This is particularly useful for REST API integrations and automation → Custom Fields + JQL Support.
Category-level AQL: an AQL filter can be added to the category level, giving admins the option to override the global AQL defined during catalog creation or retain it.