Publish Bundle Requirements
To help standardize component bundle development and streamline reviews, please follow the requirements below when submitting your component for publishing in Salla Themes Marketplace.UI / UX Review#
To fulfill the UI/UX review follow the below requirements list:The bundle must contain at least 1 component and at most 15 components.
Bundles do not support global components such as Header or Footer.
Each component type must be unique within the same bundle; duplicates are not allowed.
All components in the bundle must be compatible with the theme structure.
The bundle must not negatively impact the theme’s performance.
Each component in the bundle must be usable independently.
Components must be responsive and work properly on all screen sizes.
Bundles should support future updates without affecting existing themes.
Technical Review#
The Technical review covers seven areas explained below:Bundles should follow Salla coding standards; code must be well-structured and readable.
Bundle size should be optimized and not affect performance.
Use localization instead of static strings.
Ensure all components are compatible with the current bundle version.
Bundles should not negatively impact theme loading speed or network requests.
All bundle components must display correctly on all screen sizes and devices.
Cross-Browser CompatibilityBundle components must function correctly across popular web browsers (Chrome, Firefox, Safari, Edge).
No custom HTML or elements that may compromise security are allowed.
Test all components to ensure they work as intended and are bug-free.
Track future updates for bundle components to ensure compatibility with themes.
1.0. Bundle Name#
Follow these name style guidelines:1.1.Bundle and style names should stand apart from Salla Products, Events, or Branded content.
1.2. They should also differ from Partner names.
1.3. Avoid overlap with website, e-commerce, or SEO-related terms; for instance, steer clear of names like Performance, Mobile, or Sales for your Bundle.
1.4. Ensure unique names not resembling industry or collection names from the Theme Store, such as Fashion, Electronics, or Jewelry.
1.5. Keep names clear and hint at the purpose of the Bundle.
1.6. Communicate what merchants can expect from the Bundle , encompassing core concepts and the intended audience.
1.7. Opt for noun-based or adjective-based names.
1.8. Choose easily pronounceable names to aid in recall and searching for merchants.
1.9. Consider different dialects and regional meanings; consult an idiom dictionary if needed.
1.10. Avoid using the same name on other platforms.
1.11. Name should be short, and not more than 3 words without emojis, spaces, or special characters in the Bundle or style name.
2.0. Bundle Support#
Merchants using the Bundle are advised to address any concerns they may have with the bundle developer. It is not Salla's responsibility to manage bundle support, so you need to fill in all of the following fields:Active Email that is dedicated to getting inquiries and issues related to the bundle.
Company, Personal website or social media where Merchants can get more information about you .
Active Mobile / Office number for getting inquiries and issues related to the bundle.
Active live chat link could be Telegram , WhatsApp or any other chat services. The response timeframe expected is within few hours .
An optional field you can use in case you would like to provide extra support services.
3.0. Bundle Pricing#
Salla allows you to charge Merchants a one-time payment for your Bundle. You are free to set the Bundle price as you see fit as long as it is a minimum 100 SAR for Public bundle and 250 SAR for Private bundle. Calculate the price of your Bundle based on a number of parameters:Size of the catalog it is intended for, and
When figuring out how much to charge for your bundle, don't forget to include in the expense of offering first-rate support. It will be required of you to address bugs and respond to inquiries regarding your bundle. Merchants' evaluation of your bundle may be influenced by the level of help and support you offer.
4.0. Bundle Screenshots#
Providing bundle screenshots provide a detailed glimpse of how the Bundle would look like once applied to the store.Follow the below rules when uploading bundle screenshots for publishing:4.1. Well-designed screenshots are required.
4.2. Screenshots should be provided in images or YouTube video formats.
4.3. Videos should be short and informative, 2 minutes maximum length is required.
4.4. Each Screenshot should have a unique title and description.
4.5. The title for each screenshot should reflect the bundle features for Merchants, for example, Smooth animations, Optimized performance, Easy setup with 20+ sections, etc.
4.6. The screenshot's title and description should be in Arabic and English.
4.7. A minimum of 4 screenshots of the bundle should be provided.
4.8. Screenshots should reflect all bundle features.
4.9. Screenshot images should not contain any texts or logos at all.
5.0. Bundle ChangeLog#
Your bundle should have a change log, a change log is a record that lists updates, fixes, and improvements made to the Bundle. It includes version numbers, release dates, and brief descriptions of changes such as new features, bug fixes, security updates, and performance enhancements. It helps users understand what's changed in each version and assists developers in tracking modifications and progress. Salla advises to only share relevant information and abstain from sharing inappropriate information. Modified at 2026-07-29 11:46:05
