People ask for a number because a number feels safe. Shopify will not punish you at “seven apps” and bless you at “three”. The store pays for every script that loads, and you pay every monthly bill. The useful question is how many jobs you actually have.
Which jobs are worth an app is in apps new stores actually need. Which types get expensive is in apps that slow a store. This page is only the count.
Install as few apps as the jobs require. A first catalogue on a decent theme is often two to four extras (reviews, email, anything the gateway requires). If you cannot explain an app to a colleague in one sentence, remove it.
A simple counting rule
Write the jobs: take payment, collect reviews, send email, search a large catalogue, run subscriptions. One app per job. If two apps share a job, pick one. If a job is “make the homepage prettier”, that is the theme editor, not an app. See theme customisation.
Admin-only apps (reporting, bulk edit) are cheaper on the storefront than widgets that load on every page. Count those separately. They still need a reason.
| Store situation | Typical extra apps |
|---|---|
| New theme store, small catalogue | Gateway-related if required, maybe reviews later |
| D2C with email and reviews | Two to four, if you will use both |
| Subscriptions or wholesale | Add those jobs only when they are live |
| Agency leftover install | Often too many. Audit before you add more |
What “too many” looks like
Two popups. Two review widgets. A page builder on a theme that already has sections. A speed optimiser sitting on top of the rest. That is not a strategy. Walk the speed checklist after you cut, not before you shop the App Store.
A unique buying flow is still custom development, not app number 21.
NP SoftTech can say what loads and what you can drop. Send the store URL.