Extension Marketplace Policy

This policy defines expectations for extensions that integrate with the Shop3 ecosystem.

Compatibility Expectations

Extensions should follow canonical OpenCart conventions, avoid core edits, use predictable namespacing, respect theme boundaries, work with common OC3 store configurations, document assumptions, and avoid unnecessary storefront database reads.

Quality Expectations

Extension quality should include focused behaviour, clear admin settings, safe install/uninstall behaviour, no hidden vendor lock-in, no unexpected template overrides, no silent data migrations, admin input validation, and documented cache invalidation when applicable.

Naming Conventions

Theme ecosystem extensions should use canonical OpenCart naming and project-approved prefixes where relevant.

Examples should prefer underscore-separated names such as shop3_latest, not joined names such as shop3latest.

No Malicious Overrides

Extensions must not override unrelated vendor behaviour, hide malicious code, collect data unexpectedly, alter payment or checkout behaviour without explicit purpose, bypass permissions, modify admin users or credentials, or intentionally degrade other extensions.

No Core Hacks Policy

Core hacks are not acceptable for the Shop3 ecosystem. If integration needs a hook, use OpenCart events, documented extension points, or propose an architecture change.

Integration Guidelines

Good integrations should keep business logic in the module/integration layer, expose clean data to theme templates, avoid coupling to private implementation details, document routes/settings/events/cache behaviour, and provide graceful fallback when disabled.