The goal of this page is to remove friction, not to repeat the whole product page. Keep answers short, direct, and operationally honest.
No. The app is meant to be installed without turning rollout into a storefront rebuild. The first launch should stay lightweight, controlled, and easy for a merchant to reverse if the catalog is not a fit.
No. It works best for apparel merchants where adjacent inventory can realistically support a missing size and where the operations team already understands the fulfillment reality behind that decision.
With conservative thresholds, max-share controls, and narrow rollout rules. Virtual size recovery should stop before source stock becomes risky, not after the team is forced into manual cleanup.
A recovered size is a size state that becomes sellable because real source inventory in another valid size is allowed to support it under the merchant’s rules. It is not meant to represent unlimited availability.
A focused first rollout can typically be configured in under 30 minutes when the merchant starts with one category, one mapping model, and one clear downstream workflow.
Yes. That is the recommended path. Start where the size logic is operationally strong, validate the workflow, and only then decide whether broader rollout is justified.
Usage should be tied to orders influenced by recovered size availability, where CutSizeGenie kept an eligible size visible and purchasable under the merchant’s configured rules.
That is the intended commercial model. The website and app listing should stay aligned so merchants understand pricing, billing path, and usage logic before they install.
Recovered availability should stop once the configured safety level is reached. That is the point of the safeguard system: preserve operational trust before the source size becomes constrained.
They should. The product story only works if the downstream team can understand why a recovered order was allowed and what source inventory logic sits behind it.
Yes. Merchants should feel comfortable testing fit on a narrow rollout before making the product part of a broader merchandising workflow.
A high-intent apparel category with clear size-run gaps, real demand on the PDP, and a team that already has confidence in the category’s size substitution or cut-size workflow.
Yes. Rollout should stay selective. Start with the product groups where the size relationship is operationally proven, and leave the rest of the catalog untouched until the model is validated.
That depends on the merchant’s merchandising policy, which is why rollout should only happen where the size relationship is already believable to the business. The app should support a valid selling path, not create confusion that support has to clean up later.
It can be a fit when the business already has a disciplined downstream process for those orders. The right question is not whether the app can technically switch on a size, but whether fulfillment, support, and returns policies are already clear enough to support that decision.
Use a narrow rollout and measure influenced orders, PDP conversion behavior on affected products, support friction, and source-stock safety. If the commercial upside improves while the downstream workflow stays clean, the rollout is earning expansion.