If you run a Shopify store and want to drop an old app, start with an order that would be hard for your team to fulfill without it. For a store that sells personalized wallets, that might be a wallet with two initials. Follow the initials from the product page to the place where staff actually read them. If the app still supplies a required step or record, keep it in place until the replacement works there.
A clean product page can hide the real problem. The new initials field may look right and save the choice in Shopify, while the person at the packing bench still gets their instructions from the old app. In that case you have a storefront change and an unfinished handoff.
AI-generated photo of a fictional leather-goods shop owner checking a wallet order at the packing bench.
Find out where the app still does work
Pick one product the app touches and ask the person who fulfills it to show you a recent order from start to finish. Watch where they get the product details, what they copy or print, and what happens if something is missing. Check where they would find the information on an order that is still open.
Then look at the storefront. Shopify apps can add visible blocks, run through embeds that shoppers may never see, or add code directly to a theme. A missing widget tells you little about what the app still supplies elsewhere. Use Shopify’s guide to app blocks, embeds, and theme code to identify the pieces you can see. Ask the app developer about anything your team cannot trace.
Check the app’s own settings and support instructions before planning the removal. Shopify’s uninstall guidance explains that dependent workflows can stop, theme code can remain, and some app data may be unrecoverable. Export the records you need while you can still open them, then spot-check an open order against the export. Also check for a subscription billed outside Shopify, which may need to be canceled separately.
Follow one detail all the way to packing
In this hypothetical example, a wallet shop is replacing an old personalization app. The new product field collects the initials JR. The team runs a test, opens the saved Shopify order, and sees JR alongside the wallet. At the packing bench, though, the usual packing view still has no initials. The packer can see them only by opening the old app.
The owner has two plausible fixes. The team could fulfill from the Shopify order if that view has everything the packer needs and the team can work from it reliably. Or the store could update the packing view to show the initials beside the right item. Shopify supports saving information such as engraving text with an individual item through line item properties. The store still needs to prove that the chosen packing view displays that information.
Run the same check on an unpersonalized order. Staff should know it is a standard wallet without having to guess whether initials went missing. If customers can buy two wallets with different initials in one order, test that too. The packer should be able to match each set of initials to the correct wallet.
Decide whether to keep, replace, or remove it
- Keep it while the app supplies a required step or holds records you still need. Record the specific dependency so you know what would have to change.
- Replace it when the job still matters but another setup can do it. Test the replacement from the customer’s choice through the staff handoff, including how staff will finish orders already in progress.
- Remove it when you can account for each dependency, the records you need are available, and the agreed tests pass. Follow the developer’s cleanup instructions and confirm who will check the first orders afterward.
A duplicate theme is useful for trying the new storefront field without editing the live theme. A preview checks the storefront layer while the app is still installed. Agree on a separate way to verify checkout, saved order details, and the packing step. Plan that test with whoever manages payments and fulfillment so it won’t interrupt live checkout or send a package by mistake. Shopify lists those considerations in its test order guide.
Before the change, name the person who can pause the affected offer if an order arrives without the required detail. Keep access to the records needed to finish existing purchases. Plan that fallback separately from a theme backup because reinstalling an app may leave earlier settings or data unavailable. Right after removal, rerun the standard and personalized paths under the agreed test plan before relying on ordinary customer orders. If either fails, use the fallback.
Scope the work around the handoff
You can make the first pass yourself with a product link, an order you can trace, and a staff member who knows the packing routine. If the app’s code, order data, or packing integration is hard to separate, Website & Store Care can scope the troubleshooting and post-change checks. The work can cover a short list of dependencies, the planned change, and the two order paths someone will verify. Your team supplies a sample of the order detail staff need and confirms who can verify the packing handoff. Agree separately on any replacement or integration work the review uncovers.
That connection between the storefront and the work behind it also matters in ongoing support. Our El Mayorista case study documents buying-path review and continued Shopify store support alongside catalog organization. For your store, the starting point can be smaller. Bring the app name and one affected product link to discuss whether the job is straightforward cleanup or a replacement that needs to be tested in stages.
