Publishing

Plugin guidelines.

These guidelines outline the requirements for publishing plugins on the Orbit Commerce Plugin Store. Following them helps keep the experience excellent for merchants and gets your plugin approved faster.

Overview

The Orbit Commerce Plugin Store is a marketplace where developers distribute plugins that extend Orbit Commerce stores. We're committed to maintaining a high-quality ecosystem that merchants can trust.

All plugins submitted undergo a review process to ensure they meet our quality, technical, and content standards.

Note: These guidelines may be updated periodically. Check back before each submission to ensure your plugin meets current requirements.

Quality standards

Plugins must meet high standards to be listed on the store. We evaluate based on the following criteria.

Functionality

  • Plugin must work as described without errors or crashes
  • All advertised features must be fully functional
  • Must be compatible with the current version of Orbit Commerce
  • Must not negatively impact store performance or page load times
  • Should handle edge cases gracefully without breaking

User experience

  • Clear and intuitive user interface
  • Consistent design that matches Orbit Commerce admin aesthetics
  • Helpful error messages and validation feedback
  • Accessible to users with disabilities (WCAG 2.1 AA compliance)
  • Responsive design that works on all screen sizes

Value proposition

  • Plugin must provide clear value to merchants
  • Features should not duplicate core Orbit Commerce functionality
  • Pricing must be fair and clearly communicated
  • Free trial or demo should be available when possible

Technical requirements

All plugins must meet these technical requirements to ensure security, performance, and compatibility.

Security

  • All data must be transmitted securely using HTTPS
  • User data handled in compliance with GDPR and other privacy regulations
  • No storage of sensitive payment information
  • Proper input validation and sanitization to prevent XSS and SQL injection
  • Authentication tokens securely stored and transmitted
  • Third-party API keys never exposed to the frontend

Performance

  • Must not increase page load time by more than 500ms
  • Efficient database queries with proper indexing
  • Lazy loading for non-critical functionality
  • Proper caching where applicable
  • Minimal impact on Core Web Vitals

Code quality

  • Clean, well-documented code following best practices
  • Proper error handling and logging
  • No deprecated functions or libraries with known vulnerabilities
  • Semantic versioning for all releases
  • Comprehensive changelog for each version

Compatibility

Minimum requirements

  • • Compatible with the latest version of Orbit Commerce
  • • Modern browsers (Chrome, Firefox, Safari, Edge — latest 2 versions)

Content guidelines

Your listing is how merchants discover and evaluate your plugin. Follow these guidelines to create an effective listing.

Plugin name

  • Must accurately describe the plugin's primary function
  • Cannot include "Orbit" or "Orbit Commerce" unless officially partnered
  • Must be unique and not confusingly similar to existing plugins
  • Cannot contain special characters or excessive capitalisation

Description

  • Clear, accurate description of what the plugin does
  • List all key features and benefits
  • Specify any limitations or requirements
  • Include setup instructions or link to documentation
  • No misleading claims or exaggerated benefits
  • Proper grammar and spelling

Screenshots & media

  • Minimum of 3 high-quality screenshots (1200x800px recommended)
  • Screenshots must show actual plugin functionality
  • No placeholder or mockup images
  • Images must be current and match the submitted version
  • Optional: demo video showing key features (max 3 minutes)

Pricing

  • All fees must be clearly disclosed upfront
  • No hidden charges or unexpected costs
  • Subscription terms must be clearly stated
  • Refund policy must be specified
  • Free plugins cannot require payment for core functionality

Prohibited content

The following types of content and functionality are not permitted.

Not allowed

  • Malware, spyware, or any malicious code
  • Features that violate user privacy without consent
  • Cryptocurrency mining or blockchain operations without clear disclosure
  • Adult content, gambling, or illegal activities
  • Hate speech, discrimination, or harmful content
  • Copyright-infringing materials or pirated content
  • Plugins that solely exist to display advertisements
  • Functionality that circumvents Orbit Commerce licensing
  • Scraping or harvesting merchant or customer data
  • Impersonation of other developers or brands
  • False claims about partnerships or endorsements
  • Plugins that require disabling security features

Support requirements

Good support is essential for merchant success and your plugin's reputation.

Required support

  • Respond to support requests within 48 hours (business days)
  • Provide documentation for installation and configuration
  • Maintain a FAQ or knowledge base for common questions
  • Offer a way for merchants to report bugs or issues
  • Provide timely updates for security vulnerabilities

Recommended

  • Live chat or ticket system for support
  • Video tutorials for complex features
  • Regular updates and feature improvements
  • Responsive to merchant feedback and feature requests
  • Active engagement with plugin reviews

Review process

All plugins undergo a review process before being published. Here's what to expect.

1

Submission

Submit your plugin through the Developer Portal with all required information, screenshots, and documentation.

2

Initial review

We check that your submission is complete and meets basic requirements. Usually 1–2 business days.

3

Technical review

We test functionality, security, and performance. Typically 3–5 business days depending on complexity.

4

Content review

We review listing content, screenshots, and documentation for accuracy and compliance.

5

Decision

You'll receive notification of approval, or feedback on required changes. Approved plugins are published immediately.

Average review time: 5–7 business days for new submissions. Updates to existing plugins are typically reviewed within 2–3 business days.

Next step

Ready to submit your plugin?

If your plugin meets these guidelines, we'd love to have you on the store.

Get startedContact us