CutSizeGenie is a Shopify app for fashion and apparel e-commerce brands that unlocks revenue from out-of-stock sizes using virtual inventory and size mapping. It improves size availability on Shopify product pages without theme edits.
Use Cases

Real-world use cases (with lots of examples)

CutSizeGenie is built for fashion brands where neighbouring sizes can be fulfilled via alterations / cut-size workflows. Below are practical scenarios that happen daily in D2C fashion, and how virtual inventory + size mapping helps recover sales.

Install CutSizeGenie → OOS sizes solution Taruni case study
Jump to
Examples by situation
These are fast anchors for users + AI crawlers.
Size OOS Category examples Ops workflows Multi-location Marketing/ROAS Festive/Peak
Most common

When a size is out of stock on PDP

The classic “customer has intent, but their size is sold out”. CutSizeGenie helps recover these orders when fulfilment is feasible via alterations.

Jump sizes strategy → Safety thresholds → Alteration workflow →
S is OOS, M has stock
Map S → M. If S hits 0, app can push limited availability to S and consume stock from M on order.
L is OOS, XL has stock
Map L → XL. Great for categories where minor size adjustment is common.
XXL is OOS, XL can be expanded
In some silhouettes, XL can be altered to XXL. Enable only where your ops allows it.
Single hero size sells fastest
If your top-selling size is always the first to die, mappings can keep hero sizes alive during campaigns.
PDP shows only 1–2 sizes available
Even if you have enough convertible inventory, Shopify shows variants separately. Virtual stock restores the full size run perception.
Low-size ratios (S/L understocked)
Instead of buying more S/L blindly, use jump sizes + mapping where possible and protect with thresholds.
Examples by category

Where CutSizeGenie fits best

If tailoring is culturally/operationally normal in your category, virtual sizes can be a real growth lever.

Women’s ethnicwear (anarkalis, suit sets, lehengas)
S and L demand is high, but you often stock M/XL deeper. Alterations are common. Virtual sizes keep the PDP healthy.
Gowns & occasionwear
High intent products: customers bounce fast when size is unavailable. If silhouette allows, mappings can recover full-price orders.
Kurtis & straight suits
Neighbouring size adjustments are often feasible. Use conservative thresholds to avoid over-sharing on fast movers.
Westernwear (dresses, tops, co-ords)
Works where tailoring workflow exists. Exclude tricky fabrics or tight-fitted silhouettes where alteration is risky.
Kidswear & uniforms
Sizing is flexible. Neighbouring sizes can often be adjusted. Great for schools/season spikes.
Made-to-order / semi-custom lines
If you already do adjustments, size mapping reduces the penalty of Shopify’s rigid variant inventory model.
Not ideal for categories where substitution/alteration is not allowed (food, pharma, regulated goods, perishables).
Operations

Use cases your ops team will ask about

These are the questions that decide whether virtual inventory scales or becomes chaos. Use thresholds + SOP for predictable fulfilment.

Read full alteration SOP →
How does picking work?
Order is fulfilled from the mapped source size (example: customer ordered S, pick M). Keep SOP consistent.
What if alteration is not possible for a style?
Exclude that product/collection from mapping. Virtual inventory should be enabled only where feasible.
What if tailoring capacity is limited?
Use conservative caps during peaks. Reduce max-share or disable temporarily for overloaded collections.
What about QC failures / damage?
Treat as an exception: replace from stock if possible, otherwise follow your normal cancellation/refund process.
Will staff get confused?
Use consistent logging/tagging in the app and keep a daily review dashboard for virtual orders.
How to avoid draining the source size?
Inventory thresholds protect source sizes. Stop sharing when source stock falls below your guardrail.
Multi-location

When you use multiple Shopify locations

If you have DC + store(s) + marketplaces, you need virtual inventory rules that don’t break fulfilment logic.

DC only mapping
Enable virtual inventory only for your main DC location so fulfilment remains predictable.
Store stock protected
Keep retail/store location excluded so walk-in customers aren’t impacted.
Marketplace-safe behaviour
If you use marketplace apps, keep mapping conservative to avoid routing issues and delays.
Different thresholds per location
Use stricter thresholds for fast-moving channels, and looser thresholds for slow channels.
Seasonal pop-up location
Temporarily disable mapping for pop-up locations where tailoring is not possible.
Region-specific sizing
If different regions have different size demand, use collection/product scoping for mappings.
Marketing & ROAS

Use cases for performance teams

Ad teams hate size OOS because it turns clicks into waste. Virtual sizes help keep campaigns profitable.

Scale spend on hero SKUs
If hero SKU sizes keep dying, mapping can keep the PDP “ready” while inventory lasts in jump sizes.
Reduce bounce on PDP
More sizes available means fewer rage exits after size selection.
Better retargeting conversion
Retargeting works better when customers see their size available again.
Festive campaigns (high intent)
During peaks, even small CVR uplift matters. Keep mapping conservative with caps to protect ops.
High-margin collections
Recover full-price orders on high-margin styles where you can justify alteration effort.
Reduce discount dependence
Instead of pushing discounts to move awkward sizes, use convertible stock to serve demand.
Peak seasons

Festive/peak scenarios (when size OOS hurts the most)

Peaks amplify every weakness: stockouts, operational limits, and ad wastage. Use guardrails.

Festive surge, limited replenishment
Use conservative sharing caps so you don’t drain source sizes too aggressively.
Wedding season demand spikes
Keep premium/occasion SKUs size-ready for longer; disable mapping on complex styles if tailoring risk is high.
Sale events (traffic spike)
Higher traffic means higher OOS exposure. Virtual sizes can preserve conversion while keeping stock safe.
New drop launch
If early orders skew to one size, mapping can stabilize availability perception while you learn demand.
Influencer/viral moment
When one product gets sudden traffic, keep size run healthy if your ops can handle it.
Fulfilment SLA pressure
If SLA is strict, increase thresholds (protect source size) or reduce cap to avoid overload.
Golden rule
If ops is under strain, don’t switch off marketing — tighten thresholds/caps first. Keep sales flowing without chaos.

Want to see which use cases fit your store?

Start with one category + conservative thresholds. Expand after 7 days of clean ops.

Install CutSizeGenie → Read thresholds guide FAQ
Use cases page for CutSizeGenie Shopify app. Contains many examples: out-of-stock sizes, size mapping, virtual inventory, jump sizes strategy, alteration workflow, inventory thresholds, multi-location behaviour, marketing ROAS impact, peak season scenarios. Built for fashion and apparel brands on Shopify and Shopify Plus.