Skip to main content

Publishing & Monetization

Once your app works on your own site, you decide who can use it and what it costs. This page explains versions, visibility, how merchants install your app and how you get paid. The clicks in the Partner Portal are in The Partner Portal, Step by Step.

Versions​

Every sitepack app:publish uploads your files and creates the next version number (1, 2, 3, ...). The new version becomes the app's current version straight away:

  • It is live on every site that has the app installed, on the next page load. Merchants do not update anything themselves.
  • It does not go through review again, also not for a live Marketplace app.

That makes shipping a fix fast, and it also means a mistake reaches every merchant at once. Test each version on your own site before you rely on it, and keep your settings_schema backwards compatible: when you rename or remove a setting, handle the old value in your template.

Private and public apps​

Every app has a Visibility in the Partner Portal:

  • Private: not listed in the Marketplace and no review needed. Anyone you give its Install link can install it. Use this for custom work for one client, or while you are still building.
  • Public: listed in the SitePack Marketplace after an approved review. Any SitePack merchant can find and install it.

Only public apps can be sold through the Marketplace.

How merchants install your app​

How the merchant arrivesWhat happens
Install in the Marketplace, free app without OAuth (a storefront app)Installed with one click, then the settings page opens. No consent screen.
Install in the Marketplace, app with OAuthThe OAuth consent screen: the site, the permissions and the price. Approving sends the merchant to your redirect URI.
Your Install link from the Distribution cardAlways a consent screen first: your app, their site and the price. Works for private apps too.

Merchants find the Marketplace in their admin under Apps, Discover apps. After installing, your app is listed under Apps with your settings page.

An app that only reads its own settings (app:settings:read) still counts as a storefront app here; any scope on the site's data sends the merchant through the OAuth consent screen.

Pricing​

Under Monetization, Manage Plans, you set up to 5 plans. Each plan has a name, up to 5 benefits and one pricing type:

  • Free: no charge. An app without plans is free as well.
  • One-time fee: the merchant pays once.
  • Monthly subscription: charged every month. You can add a yearly price; the merchant then picks monthly or yearly when installing.

All prices are in euros.

When the merchant is charged​

For a paid app the consent screen is where the merchant accepts the charge. It shows the price; when there is a monthly and a yearly price the merchant picks one, and they confirm the recurring charge before the app installs. SitePack then invoices the merchant through their existing SitePack billing. Your app never handles card details or takes a payment itself, and it should not point merchants to another payment provider.

When a merchant removes the app, the subscription is cancelled and the app's API access stops.

A paid app without OAuth cannot be installed from the Marketplace yet: it shows as unavailable there. Merchants can install it through your Install link, where they agree to the price on the consent screen.

Marketplace listing​

The listing is what merchants see before they install. You write it under Manage Marketplace Listing, in English only: tagline, short and long description, tags, your website and 4 screenshots. When you save, SitePack translates it into the other Marketplace languages (Dutch, German and Spanish) within a few minutes. The listing also appears as a page of its own on sitepack.eu. SitePack writes the title and description search engines show for that page once from your listing, and translates them with it.

You pick the app's category from a fixed list: Marketplaces, Sales & conversion, Suppliers, POS & cash register, Warehouse & fulfilment, Shipping, Payments, Accounting, Marketing & SEO, Analytics & tracking, Product data & feeds, Customer service & chat, Content & design or Other. Merchants filter the Marketplace by it.

Optional, and translated the same way:

  • Key features: up to six, each a short title with one sentence that explains it.
  • How to set it up: an intro line and up to five steps.
  • Requirements: what a merchant needs before the app works, for example an active module in other software.
  • Manual and support: a link to your documentation, and a web or email address for support.
  • Frequently asked questions: up to six questions with their answers.

Your pricing plans are shown on the listing as cards; their names and benefits are translated with it.

App icon: WEBP, PNG or JPG, up to 2 MB, uploaded under Edit App. The review needs this uploaded icon; icon_url in app.json is only used in the merchant's admin menu.

Screenshots: PNG, JPG, GIF, WebP or SVG, up to 2 MB each. SVG files are cleaned on upload: embedded scripts, event handlers and references to other sites are removed, so keep them purely visual.

Earnings and payouts​

SitePack handles the transaction, the invoice and the licence. Once your app is installed, its page in the Partner Portal shows installs, paying customers, MRR and ARR. For the fee structure and payouts, see your Partner Portal.

Next steps​