Shopify Product Review Cleanup Before Archiving or Replacing Products

Start by naming the catalog event correctly

Not every catalog change creates a new review problem. If the same product continues and you are only correcting copy, price, imagery or an ordinary option, editing the existing product can preserve the shopper's mental model. If the commercial object has genuinely changed, for example a new appliance generation with different dimensions, a reformulated cosmetic, a revised material or a device with different compatibility, treating the successor as the same reviewed product can make old evidence misleading.

Shopify's current product documentation distinguishes editing an existing product from duplicating one. A duplicate is a new product that can be changed independently of the original. That native behavior is useful for catalog creation, but it is not evidence that records owned by a third-party review app move with the duplicate. Before any replacement project, decide whether you are updating one continuing product or creating a genuinely new product whose review history should begin on its own terms.

Step 1: make a review-context snapshot before changing product status

Before archiving, deleting or replacing a reviewed product, record enough context to understand what the existing proof actually describes. Note the product title, handle or storefront URL, major variants, material or model version, and the date the reviewed version stopped selling. Then inspect the live review block and the moderation queue. You are not creating a fake archive of customer sentiment; you are giving the team a reference that prevents old proof from being attached to a materially different successor by accident.

If customer photos matter, also remember where the assets live. Yorum Kiti's current listing says approved review photos are stored in the merchant's own Shopify Files. That is useful because the media lives inside the Shopify store environment, but the listing does not promise that archiving or deleting a product performs media housekeeping for you. Treat product status and file cleanup as separate operational questions, and do not remove a file merely because a catalog record changed unless you know it is no longer needed.

• Product identity: title, handle or URL, model/version and meaningful variants.
• Review scope: what exact version or attributes the visible reviews describe.
• Media context: whether customer photos contain version-specific details future shoppers could misread.
• Replacement decision: same continuing product, minor revision, or genuinely new successor.
• Owner: who is responsible for review and URL QA after the catalog change.

Step 2: archive when you need reversibility; delete only when permanence is intentional

Shopify currently describes Archived products as no longer for sale and hidden from the storefront, while keeping the product record in the admin's Archived view. Shopify also warns that deleting a product permanently removes it and that deleted products cannot be restored. That makes archive the safer default when the merchandising decision might be reversed or when the team still needs the product record for operational reference.

Archiving does not magically decide what should happen to historical customer evidence. If the old product will no longer have a public page, the important work becomes preserving accurate internal context and deciding what, if anything, should appear on the successor. Never turn 'this new product replaced the old one' into 'these old reviews now describe the new one' unless the evidence genuinely applies and your review system explicitly supports the intended relationship.

Step 3: do not assume a duplicated product inherits app-owned reviews

Shopify's duplicate-product function creates a new product, even when it begins with copied native product details. Third-party review records are a separate layer. The current Yorum Kiti listing documents collecting, approving and displaying reviews on product pages, but it does not advertise automatic review cloning, grouping or transfer when a product is duplicated. That means the safe operating rule is simple: assume nothing until the review app explicitly documents the behavior you need.

This matters most when a merchant duplicates a strong seller to launch a new color family, model year or reformulation. The two pages can look almost identical in the admin while representing different customer experiences. If keeping historical reviews is essential, verify an explicit migration or grouping workflow before the catalog change. If the app does not provide one, launch the successor with its own review collection instead of manufacturing continuity the software has not promised.

Step 4: decide whether old reviews are still relevant to the successor

Review relevance is a product question before it is a software question. A replacement water filter with the same fit, materials and performance claims may have more continuity than a redesigned appliance with a new motor, controls and dimensions. A lipstick shade with new packaging but unchanged formulation is different from a reformulation that changes texture or wear. The closer the reviewed attributes are to the new product, the stronger the case for preserving context somewhere appropriate; the more the product changed, the stronger the case for collecting fresh proof.

Use a simple test: if a shopper read the old review without seeing the old product title, could the review cause a false expectation about the new item? If the answer is yes, do not present it as proof for the successor. Reviews are valuable because they reduce uncertainty. Reusing them where they no longer describe the thing being sold does the opposite.

Step 5: handle the retired product URL separately from the review decision

Old product links can live in search results, emails, social posts, customer bookmarks and support conversations. Shopify's current URL-redirect guidance says redirects work from broken URLs, and gives deleting a product then redirecting its old URL to a similar product as a common example. Shopify also notes that a URL that still loads a valid page cannot be redirected. That means URL cleanup needs to follow the actual storefront state, not an assumption that every status change immediately behaves the same way.

After the product change, test the old URL as a customer. If it is intentionally broken and a successor exists, create an appropriate redirect using Shopify's current redirect workflow. If the old page still resolves, a redirect will not take over until the source URL becomes eligible. Keep the destination honest: send a retired product to the closest useful successor or category, not to an unrelated high-margin item just because traffic exists.

Step 6: launch the successor's review experience deliberately

For a genuinely new successor, treat review setup as part of product launch. Yorum Kiti's current listing says its storefront blocks use theme app extensions. Place the rating summary and review list where they help the buying decision, then submit a test review, confirm it waits for merchant approval, approve it and inspect the public result on desktop and mobile. The point is to confirm the new product has a working path for new evidence rather than assuming the old product's proof will follow it.

Yorum Kiti is currently free with no paid plan according to the owner, so a catalog refresh does not require adding another recurring review subscription when its focused feature set is enough. It is available in English. The App Store CTA on ShopRadar uses the authentic `yorum-kiti` slug with `locale=en`; that requests the English listing locale and does not change installed-app language settings.

Step 7: keep a retirement checklist for future catalog changes

The easiest way to lose review context is to make catalog retirement an improvised task. Add a short checklist to every discontinuation or successor launch. It should force the team to classify the product change, review old evidence, decide whether the product should be archived or deleted, inspect customer-photo relevance, test the old URL and verify the successor's review block. The checklist is an operating process, not a feature claimed by Yorum Kiti.

For stores with frequent seasonal drops or model-year updates, this small discipline prevents two opposite mistakes: throwing away useful context too aggressively and carrying old social proof forward too casually. Neither extreme helps shoppers. The goal is a clean catalog where every visible review still describes the product a customer can actually buy.

• Classify the change: edit, duplicate, successor, archive or permanent deletion.
• Capture the old product identity and what its reviews actually describe.
• Do not assume app-owned reviews transfer to a duplicate or successor.
• Test the retired URL and add a redirect only when Shopify's redirect conditions are met.
• Set up and test fresh review collection on a materially new successor.
• Review Shopify Files separately before removing customer-photo assets.

Recommendation: use Yorum Kiti for the active catalog, and use process for the handoff

Yorum Kiti is a strong fit when your active products need a simple moderated photo-review layer without a current paid plan. Its documented job is clear: collect ratings, written feedback and up to three photos, hold submissions for approval, store photos in Shopify Files and render the approved proof on product pages. That focused scope is useful precisely because you do not need to pretend it is a catalog-migration engine.

For discontinued and replacement products, the merchant still owns the judgment. Archive when reversibility matters, delete only when permanence is intended, treat duplicates as new products unless a review tool explicitly documents transfer behavior, and collect fresh proof whenever the product changed enough that old reviews could mislead. A free review app can remove the subscription bill; a disciplined catalog process keeps the evidence trustworthy.

Apps mentioned in this guide

Frequently asked

What happens when I archive a product in Shopify?

Shopify's current documentation says an archived product is no longer for sale and is hidden from the storefront while remaining in the Archived area of the admin. If you might need the product record again, archiving is safer than permanent deletion.

Does duplicating a Shopify product automatically copy its reviews?

Do not assume it. Shopify says a duplicate is a new product, and Yorum Kiti's current public listing does not advertise automatic review transfer or cloning between products. Verify explicit app support before relying on review continuity.

Should reviews from a discontinued product appear on its replacement?

Only when the evidence genuinely describes the replacement and your review system supports the intended relationship. If dimensions, formulation, compatibility, materials or performance changed materially, fresh reviews are usually the safer shopper-facing proof.

Is Yorum Kiti free with no paid plan?

Yes. The current Shopify App Store listing shows Free pricing, and the owner confirms Yorum Kiti has no paid plan. Treat that as current product information and re-check the live listing before future budget decisions.

Is Yorum Kiti available in English?

Yes. The owner confirms Yorum Kiti is available in English. ShopRadar uses the authentic App Store slug with locale=en for promotional CTAs; that selects the English listing locale and does not change the installed app's language settings.

Can I redirect an old Shopify product URL to its replacement?

Yes when the source URL is broken and eligible for a redirect. Shopify's current guidance says redirects work from broken URLs and gives deleted products as a common use case. Test the old URL first, then point it to the closest useful replacement or category.