E-commerce
June 28, 2026
"Are you going to put serum no. 3 back on sale?" "I've been repurchasing it for two years, why is the page showing out of stock?" "My subscription says product not found." Three customers, the same SKU removed from the catalog, three different responses if your team does not have a playbook.
Ecommerce Circle recalls that a clean discontinuation includes a 301 redirect, removal from ads feeds, and a honest macro support with alternatives (Ecommerce Circle, SOP discontinuation 2026). EcomHint distinguishes between temporary out-of-stock (keep the page, back-in-stock alert) and permanent discontinuation (redirect to the closest substitute or 410 page if there is no SEO value) (EcomHint, out of stock 2026).
This guide #243 covers customer support for discontinued products: alternatives, future availability, subscriptions. Subject missing from the existing backlog. Distinct from restocking delays (#167) (temporary out-of-stock with ETA) and the future alternatives bot (#245): here, ops + CS macros when the product is not coming back.
Summary
Why do discontinued products generate tickets?
A discontinued product ticket mixes customer disappointment, fear of a permanent stockout, and sometimes anger if no one gave warning.
Three customer profiles
Loyal repurchaser: has been buying the same SKU for months
Active subscriber: next delivery blocked on a retired product
New visitor: arrives via Google or a bookmark on a dead page
Support cost
Without macros or alternative product databases, each ticket requires manual catalog research + merchandising validation. Ilana Davis estimates that abruptly deleting the product page creates 404 errors and avoidable "where did my product go?" tickets by keeping the page active with alternatives (Ilana Davis, discontinued Shopify 2025).
DTC skincare example
Discontinuation of a reformulated serum, 340 subscribed customers + 28 tickets/week "when is No. 3 coming back?". Without SOP: agents promise an uncertain return. With DISC macro + redirect to No. 3 v2: tickets −72% in 30 days, alternative acceptance rate 41%.
How does it differ from temporary out-of-stock items and limited editions?
Four stock situations, four distinct support responses.
Temporary out of stock (#167)
Restocking delays (#167): product will return, ETA to be communicated, back-in-stock alert. Never say "discontinued" if restocking is confirmed.
Back-in-stock alert (#48)
Back-in-stock notifications (#48): captures demand on temporary OOS. Useless if the product is permanently discontinued: switch the waitlist to an alternative or range newsletter.
Limited edition (#222)
Limited editions (#222): finite stock announced at launch, no surprises. Classic discontinuation: customers used to a permanent SKU, stronger shock.
Range migration (#244, upcoming)
The future range migration guide will cover the official v1 → v2 replacement with compatibility. Guide #243 covers pure stoppage or withdrawal without a structured migration campaign.
Promise #243
Discontinuation typology, ops SOPs, PDP/SEO, macros, alternatives, subscriptions, KPIs, playbooks.
Which type of discontinuation should be mapped?
Name the catalog discontinuation type before replying to the customer. The tone and offer change.
Six ops scenarios
disc_reformulation: same product, new formula (SKU v2 exists)
disc_replacement: product replaced by another reference in the range
disc_supplier_eol: supplier end of life, no exact substitute
disc_rationalisation: removal due to low margin/volume
disc_seasonal_retire: seasonal not renewed (vs paused)
disc_variant_only: one color/size removed, parent product remains
Gorgias tags
product_discontinued, sub-tags disc_reformulation, disc_subscriber, disc_no_replacement, disc_404_arrival.
Quick response matrix
Reformulation → redirect v2 + explain changes. Replacement → 2 alternatives + discovery code. EOL without substitute → honesty + products for same use. Variant only → other options still available on parent PDP.
How to prepare for the discontinuation before the first ticket?
The Shopify SOP discontinuation is played out before stock hits zero, not after the complaint.
7 ops steps (adapted from Ecommerce Circle)
Exhaust inventory: stop supplier reorders, sell remaining stock
Document substitute(s): SKU replacement_primary, replacement_secondary, note differences
301 Redirect: old URL → replacement PDP or collection (Shop Circle, redirect 2026)
Remove feeds: Google Merchant, Meta catalog, Klaviyo product feeds
Swap subscriptions: bulk swap before SKU deletion (Skio, discontinue 2026)
Support brief: DISC macro + internal alternatives sheet + gesture code if applicable
Log SKU register: date, reason, redirect target, owner
Internal DISC-SKU sheet
Fields: removed SKU, disc_* type, replacement URLs, key differences (formula, size, price), merchandising-approved customer message, DISC10 promo code if policy, effective date, supplier contact if quality dispute.
Proactive communication
Email segment 12-month buyers + subscribers 14 days before effective removal. Moosend recommends alternatives + visible support channel in the notification email (Moosend, emails OOS 2026).
What should be done with the PDP and the SEO of discontinued products?
The discontinued product PDP protects SEO and guides toward the substitute without frustration.
Three strategies based on SEO traffic
Live page + banner: strong organic traffic, keep 200 URL, “Retired product” banner, alternative suggestions block (EcomHint, Baymard)
301 redirect: clear substitute exists, transfer SEO equity
410 / 404: low traffic, no replacement, no backlinks
Do not delete blindly
Shopify Community: deleting the page = dead URL + lost history. Prefer unlisted status + “discontinued” template with purchasing disabled (Shopify Community, SEO discontinued).
Single variant retired
Keep the parent product live. Hide the variant or mark it as unavailable. Redirect the variant URL, if indexed, to a similar in-stock variant.
PDP alternative block
2-4 products: replacement_primary first, same category/use, customer reviews if possible. Baymard recommends visible cross-sells on unavailable pages, especially for permanent discontinuation.
How to structure customer support answers by scenario?
The discontinued customer service decision tree avoids imaginary restock promises.
5-step agent workflow
Identify requested SKU (past order, link, product name)
Lookup DISC-SKU sheet: type of discontinuation + substitutes
Active subscriber customer? → subscription branch section 9
Choice: alternative + code, refund last order if not shipped, or simple information
Shopify tag + note: discontinued_inquiry | SKU-X | offered : SKU-Y | outcome
Honesty rule
If no_restock confirmed by ops: never say "back soon". Ecommerce Circle: the honest macro with alternatives converts better than vagueness that generates a second ticket.
Commercial gesture
Typical thresholds: -10% on first substitute order for loyal repeat buyer (3+ purchases), free exchange if recent order not shipped, no gesture for simple curiosity without history.
What macros for each type of discontinuation?
Gorgias-ready DISC-* macros, variables {SKU}, {replacement}, {code}, {diff}.
DISC-REFORM-01 (reformulation v2)
"The {SKU} has been replaced by {replacement}, new formula {diff}. Same use, available here: {lien}. Code {code} -10% to try the current version."
DISC-REPLACE-01 (range substitute)
"We have discontinued {SKU}. Recommended alternative: {replacement} ({raison}). Second choice: {replacement_secondary}. Need help choosing?"
DISC-EOL-01 (discontinued without equivalent)
"{SKU} will unfortunately not be brought back to sale ({raison fournisseur/rationalisation}). Similar products: {liens}. We understand the disappointment and remain available."
DISC-SUB-01 (impacted subscriber)
"Your {SKU} subscription has been migrated to {replacement}. Next delivery: {date}. Modify or cancel: {portail}. Differences: {diff}."
DISC-404-01 (dead page landing)
"This product is no longer available. Here is the official replacement: {replacement}. If you were looking for something else, describe what you need and we will guide you."
How to recommend alternatives without over-selling?
The discontinued alternative recommendation must be factual, not an aggressive upsell.
Matching grid (4 criteria)
Identical use: same customer problem solved
Consistent range: same line or price tier ±20%
Confirmed stock: inventory API before sending macro
Explicit differences: format, scent, compatibility noted
Maximum of 2 alternatives
Flodesk recommends 2-3 targeted suggestions rather than an entire catalog (Flodesk, email alternatives 2026). Chat support: 1 primary + 1 secondary is enough.
Honest comparison
If the substitute is less concentrated or more expensive: say so. See chatbot product comparison for the "v1 vs v2" template.
Future availability
Only promise a return if ops has scheduled a seasonal relaunch. Otherwise: "No scheduled return date" + range newsletter alert if the customer insists.
How to manage subscriptions and recurring customers?
Discontinued product subscribers generate the most urgent tickets and potential chargebacks.
Skio Order (non-negotiable)
Identify active subscriptions on the SKU via Recharge/Skio/Appstle
Bulk swap to replacement_primary before Shopify removal
Remove SKU from selling plans
Proactive email DISC-SUB-01 with free modification grace period
Only then: draft/archive Shopify product
If product was already deleted by mistake
Bulk swap to ghost variant via subscription tool. Emergency macro: apology + immediate swap + shipping credit if delay > 7 days. See subscription restocking support and subscription support.
Repurchase customers without subscription
Klaviyo segment "purchased SKU X 2× in 12 months": D-14 discontinuation email + DISC10 code. Reduces D-day tickets by 40% to 60% on shops that apply it.
Which anti-patterns degrade trust?
Five discontinued support errors turn disappointment into churn.
Ghost restock promise
Agent says "come back in 2 weeks" without ops validation. Second ticket. more hostile.
Deletion without redirect
404 + customer bookmark = ticket + bad SEO signal.
Off-topic alternative
Proposing shampoo when the customer was looking for a mask from the same range. Validate the DISC-SKU sheet.
Subscriber discovers upon charge
Silent swap without email. Always notify before the next billing cycle.
Active ad feeds post-removal
Meta/Google still serving the SKU: paid traffic to a dead page, tickets + wasted budget.
How does Qstomy answer questions about discontinued products?
Qstomy reads the DISC-SKU database and responds with verified stock substitutes.
Discontinued Features
Intent product_discontinued: SKU lookup + disc_* type
DISC-SKU Corpus: v1/v2 differences, replacement links
Live stock alternatives: primary + secondary Shopify API
Subscriber branch: Recharge/Skio status + portal link
Auto calculated gesture code: if repurchase LTV > threshold
Quantified DTC Scenario
Supplements brand, removal of 4 SKUs due to rationalization, 890 active repurchasers, 0 DISC product sheets, 52 tickets/week post-removal. Deployment of DISC product sheets + bot corpus + proactive email + subscription swap. After 6 weeks: discontinued tickets −68%, bot alternative acceptance 38%, churn of impacted subscribers −22 pts vs. previous removal without SOP, segment CSAT +1.1 pt.
Explore Shopify integration, AI customer support, request a demo.
Which operational playbooks should be launched this quarter?
Playbook 1: DISC-SKU Registry (1 day)
List SKUs retired in last 12 months + planned for Q+3 months. Create section 4 sheet per SKU. Assign merchandising owner.
Playbook 2: Discontinuation SOP (half-day)
Document 7 steps in section 4. Proactive email template. Validate with ops + support + subscriptions.
Playbook 3: DISC-* Macros (2 hrs)
Draft 5 macros in section 7. Gorgias variables. Test 10 historical tickets.
Playbook 4: PDP + Redirect (1 day / SKU)
Discontinued banner, alternative block, 301 if strong SEO. Remove from ad feeds. Mobile QA.
Playbook 5: Quarterly Review (30 min)
KPI tickets disc_* / retail SKU, alternative acceptance rate, subscriber churn. Adjust substitutes if stock out.
Useful Linking
Removing a product from the catalog is a commercial act. Treating it as a non-event on the support side costs loyal customers. When every SKU discontinuation includes a substitute, macro, and transparency, discontinuation becomes a transition, not a disruption.
Enzo
June 28, 2026
