ShopentlyLearn
← All documents

Shopently Developer Platform limits

See how many themes, sections, apps, previews and versions your plan can maintain.

How access works

Your plan defines the available project types and quotas. Your organization role defines which actions a particular person can perform.

Marketplace submission also requires partner verification and a separate review. A plan never publishes a theme or app by itself.

Plan limits

Basic includes 1 theme project, 50 sections per theme, 1 app, 1 active preview, 25 monthly builds and 10 project versions.

Standard includes 3 theme projects, 100 sections per theme, 3 apps, 3 active previews, 3 collaborators, 100 monthly builds and 25 project versions.

Professional includes 10 theme projects, 250 sections per theme, 10 apps, 5 active previews, 10 collaborators, 500 monthly builds and 100 project versions.

Advanced includes 25 theme projects, 500 sections per theme, 25 apps, 10 active previews, 25 collaborators, 2,000 monthly builds and 250 project versions.

Plan changes and updates

An active subscription keeps its saved limit snapshot. A later plan catalogue update does not replace it without a controlled plan change.

Updating a theme or app does not change the store layout, administrator configuration or subscription limits.

Publication security

Projects, previews and artifacts are isolated from customer data. Publication requires a versioned artifact, integrity checks and the correct access.

A missing or damaged policy blocks developer features. It never assigns limits from another store.

App permissions in a store

Every app version declares exact versions of its required permissions and entitlements. A store runs only a signed version whose scope matches that store and app.

Missing consent, an expired entitlement, an unknown contract version or replay of an older decision blocks the operation. A catalogue update never expands an installed app's access automatically.

Store events are versioned, filtered by data classification and delivered idempotently. An app does not receive fields outside its approved contract.