The app store

Apps extend a store — new admin screens, storefront widgets, background jobs reacting to orders. The app store is where merchants install them and where partners publish them.

For merchants

Installing an app

Browse at Apps. Each listing shows what the app does, its screenshots, its pricing and its reviews.

Read the permissions before you install. Installing grants the app access to specific parts of your store — products, orders, customers — and the install screen lists exactly which. An app asking for write_orders can change your orders. If the scopes look broader than the app's job, that is worth questioning before you approve.

Installed apps live under Apps, with whatever admin screens the app adds nested inside.

Updates that change permissions

An app can publish an update that asks for more access than you originally granted. When that happens the update waits for you — Eekaam shows what changed and the app keeps running on its old permissions until you approve. You can also skip an update and stay where you are.

An update that does not change permissions applies without asking.

Uninstalling

Uninstall from the app's page in Apps. This revokes its access token immediately — it can make no further API calls. Data the app wrote into your store, like a metafield on a product, stays unless the app cleaned it up.

For partners

Building an app means joining the partner programme at partners.eekaam.com.

Building

app init writes an eekaam.app.toml manifest describing the app: its handle, the scopes it needs, its OAuth redirect URLs, the webhooks it subscribes to, and any admin pages or storefront extensions it adds. deploy pushes that manifest to Eekaam.

The full lifecycle — the OAuth install flow, calling the Admin API, receiving webhooks — is in Building an app, and every endpoint is in the App Developer API Reference.

Testing

Installs the current draft on one of your own dev stores, with no admin approval. This is how you exercise the real install flow before submitting. Create a dev store with eekaam store create if you do not have one.

Submitting

Review checks that the app does what its listing says, that it requests only scopes it actually uses, that the OAuth flow and webhook handling are correct, and that it fails gracefully. Requesting scopes you do not use is one of the commoner reasons for rejection — ask for the narrowest set that works.

After listing

The partner dashboard shows installs, revenue and reviews.

Publishing an update that adds scopes does not silently expand your access: existing merchants keep the old permissions until each of them approves. Plan for a period where some installs are on the old scope set and some on the new, and make the app handle both.