Installing an app

Manage → Apps. The screen has two halves: Installed and Browse the marketplace.

Before installing: read the listing

Press Details on an app card. The listing carries:

• The publisher name — shown as "by …". Apps built by the platform show by sBuilder.
• A description and screenshots.
• Three links: Website, Support, Privacy policy.

The Support link is where you go when the app misbehaves. The platform does not provide support for third-party apps — if an app breaks, the person you need is behind that link.

The privacy policy says what the app does with the data it reads from your store. Worth reading, especially for anything touching customers or orders.

The "Runs code" badge

Some cards carry a Runs code badge. It means that app runs its own JavaScript on your published pages.

The badge appears before you install, deliberately. The platform can check the size and format of that code, but it cannot check what the code does — the control on that is the version review, and it is the only one there is. So you are told beforehand rather than finding out afterwards.

The consent screen

Press Install and you reach the consent screen. It tells you:

The app's name, and its developer.

"This app will be able to:" — exactly the permissions this version asks for, in plain language rather than technical codes. "View your orders", "Create and edit your products". See What you are granting.

You can untick individual permissions. "Untick anything you would rather not grant. The app may not work fully without it." That is a real trade: less access means less risk, and possibly less function.

Press Install to agree, or Cancel.

The unreviewed-app warning

If you see:

"This app has not been reviewed by sBuilder. Only continue if you trust its developer."

it means precisely that. You are installing a version that has not been through review — usually because the developer sent it to you directly. Think it over, and install only if you know who they are.

After installing

The app appears under Installed. Press Open for its own screen, framed inside the Manage screens.

The app runs in an isolated frame. It can show its interface, ask you to confirm something, show a message, and navigate you within this store's manage area — but it cannot read your cookies or browser storage, and it cannot reach another store.

When the app's screen will not open

Message	Means
"Its address did not pass the safety check"	The app's page refuses to be framed. Contact the developer.
"It may have been suspended or its version withdrawn"	The app is currently unavailable
"No longer installed on this store"	It has been removed
"You do not have permission to open apps on this store"	Your role is not sufficient
"This app failed to load"	The app's own server is not responding — try again shortly

The first three need the developer or an administrator; the last usually clears itself.

How apps update

When a developer ships a new version that asks for exactly the same permissions, your install moves to it automatically — nothing for you to do, no fresh consent, because you are not being asked for anything new.

If the new version asks for more, it stops and asks you on the consent screen.

That is why a bug fix reaches every store at once, while a widening of access is never quiet.

An empty marketplace

If you see "There are no apps in the marketplace yet — check back later", then there genuinely are none. You can build one yourself — see Build an app.