How to Recommend Alternatives When a Product Is Out of Stock

You will recommend alternatives when a Shopify product is out of stock without lying about inventory. First choose an ops rule (keep selling, pause the PDP, or point to waitlists). Then prepare similar in-stock products with clear “same job” copy. Then let chat or page modules suggest those real catalog items. This reduces dead ends. It does not guarantee a sale.

Out-of-stock (OOS) here means the shopper cannot buy the variant they want right now. Your tools may still show the product if it stays published. Treat stock signals carefully. For how chat suggestions work in general, see How AI Product Recommendations Work in Shopify Chat. For compare data quality, see Product Comparison in Chat: What Data Makes Answers Useful?.

When this applies

Use this guide if:

• A hero SKU or popular variant sells out and shoppers ask “what else is like this?”
• You sell substitutes that share a use case (same category, similar fit, backup model)
• You can edit product descriptions and keep inventory reasonably fresh

Pause aggressive auto-alternatives if:

• You have no true substitute (custom, one-off, or regulated item)
• Inventory in Admin is often wrong for days
• You would rather take waitlist emails than push another product

What you need first

1. A list of OOS-prone products and 1 to 3 approved substitutes each.
2. Honest inventory practices in Shopify (track quantity, continue selling settings you intend).
3. Distinct titles and “same job / different because…” lines on substitute PDPs.
4. A re-sync habit if your chat tool reads synced catalog inventory (not a live warehouse API).
5. A human path for “notify me,” custom orders, or “I’ll wait.”

Step 1: Choose the ops rule before chat speaks

Chat should follow store policy, not invent one.

Ops choice in Shopify	Shopper-facing meaning	Chat should…
Published + continue selling when out of stock	Preorder / oversell allowed	Say lead time or policy; do not pretend it ships today
Published + do not continue selling	Buy button blocked; page may still be visible	Admit unavailable; offer substitutes or waitlist
Unpublish / draft	Not on the storefront	Not recommend that SKU; suggest published alternatives only
Waitlist / back-in-stock app	Capture intent	Explain how to join; still offer an alternative if you have one

Expected result: One written rule per OOS-prone product. Support and chat use the same rule.

Step 2: Map each OOS SKU to approved alternatives

Use a simple sheet:

OOS product (exact title)	Shopper job	Approved alternative(s)	Why it substitutes	Do not suggest
Trail Pack 20L	Day hike, wet weather	City Pack 20L + rain cover bundle; Trail Pack 28L	Same hike job; note capacity/weather differences	Random fashion tote

Rules:

• Prefer published, active substitutes shoppers can open now
• Match the job (hiking, iPhone 15 case, gift under $50), not only the collection
• Write one honest limit (“not waterproof,” “larger,” “different color only”)
• Skip substitutes that are also OOS if you know they are

Expected result: Chat and humans are not guessing under pressure.

Step 3: Put substitute signals in catalog text

Retrieval and cards work best when alternatives are easy to find in product text.

On the OOS (or often-OOS) PDP:

• Add a short line: “If this size is gone, many shoppers choose [Exact Alternative Title] for [same job].”
• State restock policy if you have one (“We restock Fridays” only if true).

On each alternative PDP:

• “Alternative to [Exact OOS Title] when you need [job].”
• Specs that prove it is a fair swap (size, compatibility, what’s included).

Data checklist: Product Comparison in Chat: What Data Makes Answers Useful?. Pair positioning: How to Help Shoppers Choose Between Similar Shopify Products.

Expected result: A substitute is discoverable from text, not only from staff memory.

Step 4: Use a safe chat reply pattern for OOS

When a shopper names a sold-out item:

1. Acknowledge the product they want (exact title).
2. State availability carefully using the data you trust (synced stock, PDP buy button, or Admin).
3. Offer 1 to 3 approved alternatives with one difference each.
4. Offer a non-purchase path (waitlist, notify, talk to human) when that is your policy.
5. Do not invent a restock date or a product you do not sell.

Example (honest, sync-aware)

The Trail Pack 20L looks unavailable in the size you asked for. For the same day-hike job, two published options are “Trail Pack 28L” (more capacity) and “City Pack 20L” (lighter; add a rain cover if you need weather protection). I can share more detail on either, or connect you with our team for restock timing.

What not to say

• “It’s in stock” when the buy button is blocked
• “Ships tomorrow” with no policy support
• “Everyone buys X instead” with no approved map
• Recommending a draft or unpublished SKU

Step 5: Know how inventory data usually reaches chat

Many Shopify AI chats (including Appifire) learn variant quantities from product sync, then may show lines like “In stock: N” in knowledge chunks. That is not the same as live order lookup.

Signal	Typical meaning	Safe merchant action
Synced inventoryQuantity	Last sync snapshot	Re-sync after big stock changes; avoid second-by-second promises
Published + qty 0	May still appear in catalog knowledge	Unpublish if you do not want it suggested; or write OOS + alternative lines
Continue selling	Oversell / preorder path	Put lead-time text on the PDP and in knowledge
Live order API	Post-purchase status	Do not use it as your OOS alternative engine

Appifire-specific confirmation: product RAG and product cards include published, active products even when inventory is zero. Stock level alone does not remove a product from knowledge. If you do not want an OOS item suggested, unpublish it or make alternatives louder in the copy, and keep sync fresh.

Expected result: You stop treating chat stock lines as a warehouse control tower.

Step 6: Verify with three tests

1. OOS named product: Ask chat for that exact title. Confirm it does not invent a restock date.
2. Alternative quality: Ask “what’s like [OOS title]?” Confirm only approved, published substitutes appear.
3. Fresh sync: Change inventory or publish state in Admin, sync/refresh, re-ask. Confirm the story matches the storefront buy button.

Also click View Product on any cards and confirm the PDP matches the claim.

Common failures

• Leaving OOS heroes published with no alternative copy
• Suggesting another sold-out twin
• Trusting stale synced qty during a flash sale
• Pushing a higher-priced substitute without stating the difference
• Hiding waitlist options when that is what loyal buyers want
• Claiming conversion lift from alternatives alone

How Appifire AI Chat solves this

Appifire can help with OOS moments by answering from synced published catalog text, naming real alternative products, and showing product cards when titles match. It is a catalog-grounded assistant, not a dedicated back-in-stock or live inventory routing engine.

Shopper problem	What Appifire can do
“Is X in stock?”	Use synced variant inventory context when present; still verify against your sell settings
“What’s like X?”	Retrieve similar published products from store knowledge and suggest real titles
“Tell me more about that alternative”	Get More Info focuses the next reply on the selected card
Restock date / special hold	Escalate via talk-to-human; do not invent dates

What Appifire provides for this topic

• Published/active product knowledge with variant price and inventory quantity in sync chunks
• Conversational suggestions grounded in your catalog
• Product cards (up to 6) with View Product and Get More Info
• Website knowledge for shared shipping/preorder policy lines you publish

How this differs from common alternatives

Approach	Fit for OOS alternatives
Unpublish only	Stops wrong buys; offers no substitute path
Recommendation widgets	Can show similar items on the PDP; weak at explaining “why this instead”
Back-in-stock apps	Best for waitlists; not a full compare conversation
Appifire chat	Strong when substitutes are published and described; shopper can ask follow-ups
Human DMs only	Best for VIPs and true one-offs; slow at peak sellouts

Honest limits

• Zero inventory does not remove a published product from Appifire product RAG/cards. Manage publish state and copy deliberately.
• Inventory in product knowledge follows product sync, not a live warehouse tick.
• No built-in “always hide OOS + auto-pick substitutes” merchandising engine.
• No metafields in the current product sync/chunk path; put alternative tips in the description.
• No add-to-cart on cards; no guaranteed conversion from alternatives.

Next product steps: How Appifire Uses Shopify Product Information to Answer Questions · Getting Started With Appifire AI Chat on Shopify · Try Appifire

Related reading

• How AI Product Recommendations Work in Shopify Chat
• How to Help Shoppers Choose Between Similar Shopify Products
• Product Comparison in Chat: What Data Makes Answers Useful?
• Conversational Recommendations vs Recommendation Widgets

FAQ

How should a Shopify store recommend alternatives when a product is out of stock?

Pick an ops rule, map approved substitutes, put “same job” copy on the PDPs, then let chat or page modules suggest those published products without inventing restock dates.

Can chat see live inventory?

Often it sees last-synced variant quantities. Re-sync after big changes, and match wording to your Shopify “continue selling” settings.

Will Appifire hide out-of-stock products automatically?

No. Published active products can remain in product knowledge even at zero inventory. Unpublish if you do not want them suggested.

What if I have no good substitute?

Say so. Offer waitlist or human help. A bad substitute creates returns and chargebacks.

Should I unpublish or keep the PDP up?

Keep it up if you want waitlists, preorders, or SEO landing traffic with clear OOS messaging. Unpublish if you only want shoppers to see buyable items.