Back-in-Stock Emails for Fashion Brands: Size, Colour and Inventory Rules

By Trayan Hristov · Thrivelia · 21 October 2026

A customer asked for the black trousers in medium. Your email says they are back, but the link opens a page with only extra-small available. The automation sent successfully. The customer still reached a dead end.

A useful back-in-stock programme connects the requested variant, sellable inventory, the notification and the buying destination. For fashion and footwear, that means checking size, colour and market availability together.

Start with the exact item the customer requested

Treat a restock request as a specific shopping intention. Someone waiting for a wide-fit shoe in their size has told you more than a generic product-page visitor. Preserve that distinction through the form, catalogue and message.

Write down the product identifier, variant identifier, selected size and colour, market, request time and notification channel. Check which information the integration actually provides. A size someone requested for one purchase is useful context for that request; it is not proof of their size across every product or that they were shopping for themselves.

Klaviyo's back-in-stock flow documentation describes a dedicated subscription event and stock-waiting step. The customer enters when they request an alert and waits for the relevant inventory to return. An ordinary delay after a product view does not establish that an item has restocked.

Agree what counts as available

Before changing the email, trace one variant from inventory to checkout. Ask the merchandising or operations owner to confirm where stock is held, which locations fulfil online orders and whether the destination can sell to the customer's market.

Klaviyo notes that its Shopify back-in-stock flow counts physical-store inventory alongside warehouse inventory. That makes location checks important for retailers. A unit sitting in a shop is not necessarily available for the online purchase your email proposes. Verify the actual configuration and fulfilment behaviour before relying on an account-level stock total.

Also check what happens to a returned unit before inspection, a cancelled reservation and an item allowed to sell below zero stock. Those are different operational states. Agree which one should make the alert eligible rather than assuming that every positive quantity is equally useful.

Match notification volume to stock depth

Klaviyo provides a minimum-stock threshold and notification batching controls. These settings are shared across back-in-stock flows in the account. Review the existing configuration before changing it for a single collection.

An illustrative example: a variant receives 20 sellable units and has 60 waiting subscribers. A setting of two subscribers notified per restocked unit would initially notify 40 people. The next batch depends on the configured interval and remaining stock. Those numbers illustrate the mechanics; they are not recommended settings for every store.

Choose settings using your own demand, typical conversion, stock depth and customer experience. Alerting everyone immediately may suit a deep restock. A small return of a popular size deserves a different decision. No notification allocation reserves an item for the recipient unless a separate reservation system actually does so.

An annotated restock email example

The following is illustrative copy for a fictional apparel store, not a client campaign or a performance claim.

Subject: The black Everyday Trouser is back in medium You asked us to let you know when this size returned. Medium in black is available again. See the current fit details and availability before choosing your pair. Button: View medium in black

The subject identifies the requested variant. The opening explains why this person received the message. The button leads to that variant where the storefront supports it. Each part helps the customer resume the decision they were already making.

Avoid claims that a size is reserved, that only a particular number remains or that the reader must order today unless the system and commercial facts support them. Useful specificity is stronger than invented urgency.

Klaviyo's alert-email configuration guide explains how product and variant data populate the message. Preview using a real test subscription, then open the delivered link on a phone. A correct-looking editor preview is only one part of that check.

Coordinate the alert with the rest of the programme

A requested restock, a general launch and a checkout reminder can reach the same person close together. Give the restock a clear job and review competing sends. An SMS may be useful for an eligible subscriber who specifically requested that channel, but duplicating every email through SMS should be a deliberate choice.

If you add a reminder, define what makes it appropriate: the item remains available, the customer has not already completed the intended purchase and the extra message still helps. Validate how that logic works with the dedicated back-in-stock mechanism instead of copying filters from an unrelated flow.

Keep unavailable products out of other recovery messages too. Klaviyo's Shopify out-of-stock guidance describes catalogue-aware template checks and notes that behaviour depends on whether the store permits purchases when inventory runs out. Test your own product settings.

A release checklist for the team

• Subscribe to two different sizes of the same product and verify that each request retains the intended variant.

• Restock only one size and confirm the other request does not receive a misleading alert.

• Check a market or inventory location that should not be eligible for the proposed online purchase.

• Open the delivered email and product link on desktop and mobile; confirm size, colour, price and availability.

• Inspect the account's minimum-stock and batching settings, including their effect on other flows.

• Trace the experience after purchase and after the item sells out again.

• Name an owner for catalogue changes, form changes and recurring checks.

Measure whether people can complete the intended purchase

Track requests by variant, waiting time, alerts delivered, stock available at notification and resulting orders. Review cancelled and returned orders when the data is mature enough. A high click rate can coexist with poor availability, while a small restock may sell through without producing a large attributed-revenue total.

Use the results to diagnose the constraint. Many requests with few restocks is a merchandising question. Many clicks with unavailable sizes is a stock or destination problem. Customers purchasing and returning the item may need better fit information. Rewriting the subject line will not resolve every one of those situations.

Questions teams ask

Should every restock get a campaign as well as a flow?

Decide from the audience and stock. A requested-variant alert serves people already waiting. A broader campaign needs an additional merchandising reason and enough relevant availability. Check overlap before sending both.

How many reminders should we send?

Begin with the requested alert. Add a reminder only when availability and customer behaviour justify it, and evaluate complaints, unsubscribes, purchases and contribution alongside credited sales.

Build the wider fashion programme

Use our fashion and apparel lifecycle guide to connect restocks with discovery, fit confidence and repeat purchase. For the implementation foundations, see the Klaviyo flow guide.

Thrivelia's fashion email marketing service connects merchandising, customer journeys, creative and measurement. Bring one restock example, its variant data and the actual buying destination to the first review.