Skip to content
Ecomwith

Apps and Sales Channels: Review Permissions Before Install and Cleanup After Removal

  • Beginner
  • 75 minutes

An app can disappear from the app list while a storefront widget, outside subscription or copied customer data still needs attention. Before installing, ask what job it performs, what it can read or change, who owns it, and how to remove it. After removal, follow those paths and record what you find.

Start with Settings > Apps and Settings > Sales channels. Older instructions group them under Apps and sales channels. Confirm the store, page title, complete section, role and available features before planning a change. This chapter prepares approval and cleanup records; it installs nothing, publishes no products, changes no billing or credentials, and sends no customer data or messages.

Separate the app, channel and access paths

An app adds a capability, such as reviews, email, fulfillment or synchronization. A sales channel provides a selling or discovery route and may itself be installed through the App Store. Shopify displays those integrations under Sales channels. Keep its states separate: installed, connected to an external account, product published, feed accepted and order completed.

Staff permissions control what a person can do in the admin. App scopes control the data and operations an application requests. App-specific access does not grant installation or deletion rights. Manage and install apps and channels requires the permissions needed by that app or channel; Approve app charges is a separate permission, including for a free trial that becomes paid. Permission settings inside an app are another layer. Ask the owner or an appropriately authorized approver to review the actual request; a job title is not proof of authority.

The classroom store sells a physical desk-organization product with Variant A/B and plans to use US, USD and English. These inputs establish neither a US entity nor payment or channel eligibility. No prior lesson is assumed complete. First identify the people responsible for Billing, Users, Customer privacy and Customer events, then inventory installed apps, channels, theme embeds and external accounts.

Variant A and Variant B are labels for two sellable options of one product; the case assigns them no color or size. Recording each channel result separately keeps one option's status from standing in for the other.

For this launch plan, retain Online Store, necessary payment services and 1 explicitly owned measurement path. This is a classroom scope choice, not a Shopify app limit. Put review, email and advertising apps in the backlog until each has a job, owner, permission explanation, cost, trial end and exit condition. The historical development-store screenshots are a separate example, not a recommended app stack or evidence of plan availability.

Make approval and exit conditions inspectable

Create an app and channel register before choosing anything new. For each entry record purpose, current alternative, success measure, owner, approver, requested permissions, data categories, store surfaces, cost and billing basis, trial end, published products, pixels, webhooks, privacy impact, uninstall procedure and last review date. Add evidence locations, unresolved work and the next review owner. A vague promise to review permissions later is not approval.

Here, a pixel records customer events in the browser for measurement. A webhook sends an outside service a notification when a subscribed store event occurs. They use different paths, so record their connections, owners and observed destination results separately.

Register areaQuestions and evidence
Job and accountabilityWhat problem remains without this app? What alternative already exists? What outcome will justify keeping it? Who owns inputs, approves changes and handles failure?
Access and dataWhich Customers, Orders, Products, Themes, Marketing or settings data is read or edited? Where does a copy go? Why does the job need it? What does the developer's privacy policy say?
Money and trialWho approved the plan, usage basis or cap, trial end and cancellation condition? Is the subscription billed by Shopify or elsewhere? Where will the bill be reviewed?
Publication and integrationsWhich account, products, variants, markets and catalogs are involved? Which embeds, scripts, pixels, webhooks, order tags or server jobs does it add?
Exit and reviewWhat must be exported, backed up, disconnected, restored or requested from the developer? Who checks cost, residual behavior and retained data, and when?

Take the review app in the backlog. State its intended job, such as displaying customer reviews on product pages, then compare the permissions shown during installation with that job. If a requested permission has no clear explanation, ask the developer before deciding whether to approve it. The approver can then explain why the store needs the app and record why each permission is needed.

Adding an app brings another participant into store operations. The inherited SAP governance study helps frame that responsibility: its grounded-theory case followed SAP's move from an on-premises ERP product ecosystem toward a cloud innovation ecosystem, covering 2,012–2,019, with interviews from early 2,016 to mid-2,019. The public author manuscript carries the earlier copyright date; formal publication was 2,022. It identified tensions around top-down control versus bottom-up development, participants' professional roles and a shared organizing vision. Use that context to name the input owner, approver, rollback owner and decisions that stay under human control. This single enterprise-software case establishes no Shopify permission, pixel, webhook, sales or conversion result.

Historical development-store Apps page on the Installed tab, with account details masked.

The list shows Translate & Adapt and Flow, plus Installed, Uninstalled and Develop apps controls. It identifies the app-list surface; it shows neither requested permissions nor complete installation approval or cleanup.

Start the inventory from the installed list, then open the relevant app details for supported billing, activity, privacy and integration information. Shopify's activity tracking has coverage limits, including apps made by Shopify; an absent activity entry cannot prove that no data was accessed or retained.

Decisions before installation or expansion

ItemApproachReason and result to inspect
Install only for a defined jobApprove a problem, alternative, success measure, owner, cost and exit condition first.A recommendation or possible future use is insufficient. The completed approval card explains what will be tested and when the app should be removed.
Use the least access the job needsMatch requested read/write access and personal data to the actual task; ask the developer about excess access or choose another approach.Reduce unnecessary customer and order exposure. Read the saved permission state and keep its purpose, owner and review date.
Verify every used sales routeCheck account connection, data sharing, eligibility, publication, market/catalog scope and the destination's result separately.Active is a product status. It cannot establish channel acceptance, synchronization, storefront visibility or order handling.
Use the current custom-app routeUse Dev Dashboard for new custom apps and record scopes, authentication owner, credential storage and exit rules.An old admin token screen is not the new creation or authentication procedure. Existing legacy apps have a separate management path.

Follow the change through its actual surfaces

The steps below describe work for an authorized store operator. Prepare a controlled test and rollback plan before any later installation, charge approval, publication or removal. If a control is missing, first check the store, complete page title, role, subscription/features, market and required fields. Do not compensate by granting broad permissions or installing another app.

Approval, channel verification and removal

  1. Write the pre-install approval card

    Record the problem, current alternative, success measure, purpose, owner, approver, cost, trial end, requested data and permissions, and the condition for removal. Inventory existing apps, channels, theme embeds and external services so the same job is not installed twice. Separate launch requirements from backlog. Review the actual pricing and developer privacy/cleanup documentation before approval.

    You should see

    The card identifies a real job, its acceptance test, an accountable owner and a workable exit. Do not proceed when the job or trial owner is missing.

    Caution

    A pending approval or planned test is not a completed installation. If the card cannot explain the access or cost, ask the developer or select a narrower alternative before changing the store.

    Keep as evidence

    Keep the approved values, decision time, approver, evidence location and review arrangement. Redact shared material; a list screenshot is not a complete residue inventory.
  2. Review the requested data and permissions

    At the authorized installation screen, expand personal-data and store-data categories. Distinguish read from edit access across Customers, Orders, Products, Themes, Marketing and settings. Compare each request with the approved job and privacy policy. Confirm the installing person's app-management permissions and separate charge approval. After installation, review the app's actual details and supported activity/permission information.

    You should see

    The team can explain why each requested category is needed, which surfaces it can change and who reviews it. Register the permission state, job, owner and last review date.

    Caution

    A permission page cannot prove external copies are absent. If access is broader than the job, pause for the developer's explanation, a narrower configuration where supported or another solution; do not accept it just to finish setup.

    Keep as evidence

    Keep the actual saved/admin permission state and appropriate storefront or written developer evidence, with time and location. A missing product in a channel needs the channel investigation below, not repeated blind publication.
  3. Check sales-channel eligibility and product availability

    Open Settings > Sales channels and the channel actually used, such as Online Store, Shop, Google & YouTube or Facebook and Instagram by Meta. Inspect the connected account, supported region, eligibility, terms, data-sharing choices and product requirements. In Products, check the product's Publishing/availability and intended variants; then inspect the relevant Markets/catalog setup and the external channel's acceptance or feed result.

    You should see

    Each used channel has its own product, variant, account, market, publication and observed-result record. A connected account or Active product cannot stand in for these checks.

    Caution

    If a product is missing or rejected, inspect the reason, connection, market/catalog, publication and policy/feed status before retrying. If saved values differ from preview, recheck the store, scope and synchronization time. Do not expand the product scope to hide the fault.

    Keep as evidence

    Record channel, product/variant, market, account, result, check time and evidence location. Match an actual destination's product and price; order routing and fulfillment require a separate authorized test.
  4. Inspect embeds, pixels, webhooks and server paths

    After an authorized installation, inspect Online Store > Themes and the relevant theme's App embeds/blocks, Settings > Customer events, notification/webhook configuration and the connected platform. Trace scripts, pixels, webhooks, order tags, external credentials and server jobs. Compare storefront behavior and performance, event receipt, applicable consent behavior and duplicate-event handling with the baseline.

    You should see

    The team knows which storefront, browser-event and server/external paths the app uses. Each observed result has an owner; an admin save is not proof that an event reached its destination.

    Caution

    If a widget or duplicate event persists after removal, stop expansion. Identify the source, active theme, legacy snippets/scripts, separately configured pixel and caching before changing anything. Use developer instructions and a theme copy for code work.

    Keep as evidence

    Retain the theme and integration inventory, consent context, event name/identifier or redacted evidence location, destination result, performance comparison and unresolved items. Customer events alone does not enumerate every script or server integration.
  5. Distinguish new custom apps from legacy admin apps

    From the start of 2,026, new legacy custom apps can no longer be created in the Shopify admin. Existing legacy apps remain manageable. For a new custom app, the documented route is Settings > Apps > Develop apps > Build apps in Dev Dashboard. A suitably authorized developer creates the app, defines a version, URLs, API/webhook configuration and minimum scopes, releases the version and arranges installation approval.

    The historical App development screen offered a Dev Dashboard launch control beside a Legacy custom apps section. That screen was not the Dev Dashboard itself. If an old Develop apps workflow is absent or behaves differently, confirm the current route and permissions rather than continuing to search for the old creation form.

    You should see

    Keep a secret-free record of app name, purpose, scopes, developer/operational owner, credential-storage responsibility, rotation/review date and revocation condition. New scope versions still require merchant approval; publishing a configuration is not a working API integration.

    Caution

    Dev Dashboard-created apps do not provide an admin token to copy and send. The developer chooses the supported authentication flow; client credentials is scoped to stores in the developer's own organization. Record token renewal, secret rotation and revocation procedures for that flow. Never put client secrets or Admin API tokens in storefront code, screenshots or shared records.

    Keep as evidence

    Keep the current path, approved scopes/version, owner and redacted test/rollback results. The older legacy token flow has different reveal/reinstall consequences; do not uninstall a working integration merely to follow an old screenshot.
  6. Remove with a documented exit checklist

    Before authorized removal, export necessary data, review billing cycle and outside subscriptions, identify dependent features/automations and arrange a theme/configuration backup. Fulfillment-app inventory and committed work need their own transfer/dependency plan. Uninstall an app from Settings > Apps or a channel from Settings > Sales channels only after those effects are understood.

    Then check each of these surfaces: theme code and embeds, scripts/pixels, webhooks and access, DNS, pages/menus and external accounts/data. Verify stopped future Shopify recurring charges, any current-cycle amount and separate cancellation outside Shopify. Request deletion or a documented retention basis from the provider as appropriate, and record the response and unresolved scope.

    You should see

    Uninstalled is one checkpoint. Close the item only when cost, behavior, access, dependencies and external-data questions have evidence or an explicitly owned, justified retention arrangement.

    Caution

    Unknown residue or billing stays open with an owner and next review. Reinstallation may not restore settings or data; permanent custom-app deletion is a separate irreversible action. Local record reset cannot undo either action.

    Keep as evidence

    Record export/backup locations, removal time, affected surfaces, verification results, billing/cancellation and provider deletion/retention correspondence. Keep sensitive data in controlled evidence, not in this public exercise.

Read channel results at the destination

The historical product example showed a snowboard marked Active, with Online Store and All catalogs under Publishing. That locates product publication and catalog controls; it showed no external channel approval, feed receipt or successful order. For the desk product, inspect Variant A/B separately where the channel's availability or feed requires it. Keep the snowboard's sample price and stock out of this store's plan.

Shopify currently documents that adding a channel makes existing products available to it by default. Review exclusions before expansion. In channel Markets, a catalog adds alongside the parent country/region catalog; it does not replace or exclude the parent's products. Those products still need publication to the channel. Check supported regions, preferred currency and the actual product set. A small channel catalog alone is not an exclusion test.

Distinguish traffic-generating channels, which send customers to the online store, from order-generating channels, which support purchase in the third-party channel. A referring listing needs a matching online-store destination and price. A native-channel order also needs correct attribution, inventory, order import, payment/fulfillment responsibility and a rollback plan. Channel permissions, publication and feed acceptance establish none of those downstream results by themselves.

Agentic storefronts need their own review. Eligible stores can have them active by default without installing an app. Current guidance points to Sales channels > Agentic; Settings > Sales channels also exposes their management area. Review eligibility, Shopify Catalog access, automatic management/enrollment, data sharing, product policy and supported checkout behavior. Agentic channels cannot be added to channel Markets. Product discovery through Catalog is different from guaranteed ranking or purchase: Shopify's search preview is directional, and AI channels can rerank it. Turning off Catalog access has a propagation period and does not remove every web-crawled listing or the separate Shop presence. Record the actual setting, scope and later readback instead of marking all AI surfaces closed immediately.

Know what removal does and does not cover

Some Shopify-managed components are removed automatically. Use the exit checklist to establish what the platform removed, what belongs to separately installed code or external systems, and where the observed result differs from the expected behavior.

SurfaceExpected boundary and check
Theme app extensionsAssociated extension blocks are automatically removed when the app is uninstalled. If something still appears, identify the actual app, theme and implementation; do not describe all embeds as permanent residue.
Legacy theme code and scriptsOlder injected snippets, Liquid edits or JavaScript can remain. Compare the theme copy and developer instructions; inspect the customer route and performance after a controlled correction. Blind deletion can break another feature.
Pixels and server eventsIdentify app pixel, custom pixel, legacy tag and server integration separately. Inspect Customer events and the provider. A successful browser callback is not destination receipt, and a server path is still subject to applicable privacy/consent settings. Check duplication and consent states rather than bypassing them.
Webhooks, access and jobsShopify documents automatic cleanup of app-associated webhook subscriptions and admin links. Independently created webhooks, outside credentials, queued work and other apps need their own inventory and owner verification. A single app's API query is not a store-wide integration audit.
Billing and dependenciesFuture Shopify recurring charges stop with uninstall, while the current cycle can still be billed. Outside subscriptions require separate cancellation. Verify app-managed inventory, automations and order/fulfillment dependencies before removal.
External data and connected servicesRemoving access does not prove previously copied data was erased. Track provider deletion/retention responses, outside accounts, DNS, pages and menus. Shopify App Store privacy webhooks, including shop/redact, are platform requirements and requests, not proof that a provider completed deletion. Actual legal obligations and justified retention depend on the entity, jurisdiction, service and data involved.

Identify the source of any remaining widget or event before acting. If you cannot explain it, keep cleanup open and pause further installations or channel rollout. Record what was checked, what remains, who handles it and when it will be reviewed.

Playable chart

The list says Uninstalled: what is still left?

As text: the whole walk-through
  1. Shows Uninstalled Click uninstall: the list shows Uninstalled and the six places each react.
  2. Old code traced Compare the theme copy and developer notes, then fix under control.
  3. Events traced Check Customer events and the provider to tell which kind it is.
  4. Webhooks and access listed List separately made webhooks, outside credentials and queues.
  5. Billing checked This cycle may still bill; cancel outside plans separately.
  6. External data tracked Track the provider's deletion or retention reply, outside accounts and DNS.
  7. Register written Write what was checked, what remains, who handles it and when it is reviewed.

Illustrative: only the six places in the lesson's table; labels follow your store's current screens.

Watch three things: which cells the platform handles, which you still check, and how a checked source is logged.
Historical legacy custom-app overview with Install app, integration configuration and masked development-history user cells.

The screen shows ECOM_Vault's legacy admin overview and install/uninstall history. It contains no visible token value and is neither a current Dev Dashboard authorization screen nor proof that permissions, external data or cleanup are complete.

The old screen centers on an admin token, which is why its instructions can lead to the wrong workflow today. Choose the procedure for the app's actual type using current documentation; do not create, reveal, rotate or revoke a credential merely to match the illustration.

Judge the old-app cleanup scenario

The scenario deliberately presents an observed leftover. Current theme extensions normally remove their associated blocks. If a page still appears to contain an embed or pixel, establish whether it is legacy code, a separately configured integration, another app or an unresolved state. That investigation preserves the decision: list status or stopped billing alone cannot close the cleanup.

Decision · 1 question0/1 answered

Distinguish list status from completed cleanup

An old app shows Uninstalled, but its app embed remains in the theme and its pixel remains in Customer events. Is cleanup complete?

Self-check not answered

Checklist0 / 3 required
Review this store's actual evidence
  • Retain purpose, alternative, success measure, approver, data/cost/trial/exit details, evidence and review date; a list alone cannot fill the register.
  • Keep each actual channel/account/product/variant/market/catalog result, destination and time. Active is insufficient.
  • Identify managed versus separate components, browser/server event results, consent, duplication, external receipt and performance; unresolved items stay open.

Also confirm the current custom-app path and protected credential ownership, plus removal checks for code, cost, data and external accounts. Those jobs remain necessary even though the local checklist has only the original proof items.

Expand only when responsibility and results are clear

Done whenStop if
Every retained item has an owner/job, permissions and cost are explainable, product/event paths are tested, and removed items have residual checks. New custom apps use the appropriate current route with protected credentials and a rollback owner.
If an app has no job, asks for excess access, has an ownerless trial, or removal residue is unchecked, do not expand. Pause for missing channel acceptance, duplicate events or unexplained ongoing data paths.
Evidence
App/channel register, approval, actual product and event results, current access state, exports/backups, cost and removal records, provider responses, evidence locations, review date and owner. An app list, permission page, or Uninstalled state does not prove theme code, pixels, webhooks, and externally stored data are removed.

The choice and ticks below feed the same local browser record automatically. Keep full registers and sensitive evidence in controlled files; use redacted summaries and locations here. Export before changing devices. Reset clears this exercise and its local decision, checks and notes; it does not uninstall an app, cancel a subscription, restore a theme or erase provider data. If browser storage is unavailable, the exercise can work in memory without a durable local save.

What the learning record establishes

Hold

Make the scenario decision first

Choose an action after reviewing the observed residue. An unselected decision cannot count as complete.

The final stage uses test orders and launch QA to connect the preceding 19 setup steps into a reversible launch path. Reconcile this register with the actual test plan; do not infer that earlier work is already complete.

What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Self-check not answered

FAQ

Why review app permissions before installation?

The request defines what the app can read or edit, including personal data and Customers, Orders, Products, Themes, Marketing or settings. Match each category to the job and privacy policy, separate human install/charge permissions from app scopes, and question excess access before approval. An App Store listing does not remove the merchant's security, privacy or operational review.

Is cleanup complete if billing stops or the app is Uninstalled?

No. Distinguish automatically removed extension blocks and app-associated webhooks from old theme edits, separately configured pixels, credentials, queues and outside accounts. Check cost, dependencies, DNS, pages/menus and provider-held data. Record deletion results or a justified retention basis and owner; current-cycle amounts and outside subscriptions need separate review.

Does Active publish a product everywhere?

No. Inspect each used channel's account, eligibility, product/variant publication, market/catalog, policy/feed acceptance and destination. New-channel defaults and parent catalogs can include more products than expected. An accepted listing still does not prove successful order, payment, fulfillment or event delivery.

Where should a new custom app be created?

Use the current Dev Dashboard route with appropriate developer access. Existing legacy admin apps can remain, but their old creation/token screen is not the procedure for a new app. Keep scopes, version approval, credentials, authentication renewal, rotation, revocation and deployment ownership together; never put secrets in the storefront or this record.

What if the old Develop apps entry is missing?

Confirm store, role and current Apps > Develop apps > Build apps in Dev Dashboard guidance. Distinguish the admin launch page from Dev Dashboard itself and existing legacy management. Record the current path or blocker rather than trying an old new-legacy-app workflow or widening access without a reason.

Continue with the unresolved path

Work it out: which uninstalled app still bills

Four apps that have already been uninstalled (example data). Rule: disappearing from the list is not the same as being exited — check how it charged and where it still runs; billing and leftovers are two separate cleanups.

What four uninstalled apps left behind

ItemHow it chargedStill running after uninstallCurrent state
App AFree, read-only ordersOne snippet in the themeComponent still renders
App BExternal subscription, billed in-appThe subscription itself, outside the platformSubscription still renewing
App CUsage-based, billed inside the platformChannel sync stoppedProducts no longer update
App DOn trial, end date not reachedNothingTrial still running

Decide before you read on. Say which one still produces a charge after uninstall, and why C, with its broken product sync, is a different kind of problem.

Answer key: App B — it collected payment inside the app, so uninstalling removed the integration while the subscription keeps running outside the platform and the invoice arrives as usual. C's damage is data: channel sync stopped and products no longer update, which calls for a reconnect or another channel and produces no charge. A leaves a display leftover; D's trial will also convert to a paid plan at its end date, so it has to be cancelled before then, which makes it a scheduled charge rather than a settled one — not charged yet and will never charge again are different states. C is the trap, because broken sync looks worse while it is a data repair rather than money still leaving.

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Clarified Variant A/B, pixel, and webhook meanings, and added a review-app example for matching requested access to its intended job. Existing sections and practice remain intact.