A Salesive App is a third-party integration that a merchant installs on one store. It runs on the developer's own infrastructure and calls the Salesive API with scopes the merchant grants at install. It is not a theme, and it is not code running inside your dashboard. It is a separate service with limited, revocable access to your store.
What exactly counts as an app?
An app is a product built by someone else that does a job your store does not do on its own. It could sync orders to an accounting tool, run a loyalty scheme, produce a custom report, connect a supplier's system or add a workflow your team needs. The common thread is that the work happens outside Salesive, and the app reaches in through the API.
Each install belongs to one store. A merchant with two stores installs the app twice, and each install gets its own access. That sounds like a small detail, but it is what stops one store's data from leaking into another through a shared integration. The app knows which store it is working on because the token it holds is tied to that store.
What can an app read and write?
Apps can work with orders, products, customers, categories, shipping, discounts and blogs. Every one of those is gated by a scope. An app that only needs to read orders does not get permission to edit products, and an app that manages discounts does not automatically get customer records.
Scopes are granted at install, which is the moment the merchant can see what the app is asking for. That is the right place for the decision. A merchant should be able to read the list and understand why each permission is needed. If an app asks for more than its job requires, that is a reason to ask the developer a question before installing.
How does a merchant install an app?
Installation uses OAuth 2.1 with PKCE. The merchant is sent to Salesive, signs in, sees what the app is requesting, and approves it. Salesive then issues a per-store token with the granted scopes. The merchant never shares a password or an API key with the developer, and the developer never needs to hold a credential that works across stores.
That flow is the reason apps can be removed cleanly. The token belongs to one store and one install. When the merchant revokes it, the app loses access without anyone having to change a password or hunt through settings. It is a much better arrangement than the old pattern of pasting a permanent key into a third-party dashboard.
How do apps hear about changes?
Apps receive signed webhooks. Instead of asking Salesive every few seconds whether anything changed, the app subscribes to the events it cares about and Salesive sends a signed request when one happens. The signature lets the app verify that the request really came from Salesive and was not forged by someone who guessed the URL.
For a merchant, the practical effect is that an app can react quickly without polling your store all day. A new order can reach an accounting tool within seconds, and a stock change can update a supplier's system without a scheduled sweep. For the developer, the signature is the difference between a webhook and an open door.
How does an app reach the marketplace?
Apps are published to the Apps marketplace after review. Review is what makes the marketplace useful to merchants: it is the point where someone other than the developer has looked at the app and its permissions. Development and production configuration share one client ID, so the app a reviewer sees is the same app that will go live.
There is also a practical bridge during review. Review testers can install an app while it is still in review, which means the developer can test the real install flow against a real store before the listing is public. That catches the problems that only appear when someone outside the development team clicks through the consent screen.
What an app is not
An app is not a theme. It does not change how your storefront looks, and installing one will not redesign your product pages. It is also not a payment method: it cannot take money from a buyer's card on its own. If an app charges for its own service, that is a separate billing flow the store owner approves in the dashboard.
An app also does not run on Salesive's servers. The developer hosts it, which is why the scopes and the token matter so much. You are trusting the developer's service with the access you grant, so the reputation of the developer and the narrowness of the scopes are both part of the decision.
An app should ask for the access it needs, use it for the job, and lose it the moment the merchant says so.
Frequently asked questions
Do apps see my password?
No. Installation uses OAuth 2.1 with PKCE, so the merchant approves access in Salesive and the app receives a per-store token. The developer never needs your password or a permanent API key.
Can I remove an app after installing it?
Yes. The token is scoped to one store and one install, so revoking it removes the app's access. You do not need to change your password or rebuild your store.
Do apps run on Salesive servers?
No. An app runs on the developer's infrastructure and calls the Salesive API. That is why the scopes and the token are the boundary, and why it is worth checking who built the app before you install it.
Can an app access everything in my store?
Only what its scopes allow. Apps can work with orders, products, customers, categories, shipping, discounts and blogs, but each capability is granted separately at install. An app that only needs orders should not be asking for customer records.
How do I know an app is safe to install?
Read the scopes it requests and check that each one matches the job. Apps in the marketplace have been through review, which is a useful signal, but the permission list is still the thing you are agreeing to. If something does not make sense, ask the developer before you approve.
Apps are how a store gets capabilities that Salesive does not build itself, without handing over a password or a permanent key. Install one when the job is clear, read the scopes, and revoke it when you no longer need it. If you build software and want to publish your own, read how to build and publish a Salesive app. For the wider platform, see features and pricing, or browse the Salesive blog.