77.1% Conversion Surge: Stewart & James Bespoke's Bespoke AI Revolution

The Limits of Manual Curation
Context: For Stewart & James Bespoke, scaling to $2.4M monthly GMV brought a critical challenge: Body measurement data accuracy for remote customers without in-person fittings.
At this stage, standard rules failed. The Professional men aged 28-55, executives, and groom-to-bes seeking premium custom-tailored suits and accessories demanded relevance. The self-developed system couldn’t handle complex fabric texture visualization or accessory coordination, leading to 15% return rates from fit issues and missed cross-selling opportunities.
From Rules to Deep Learning
To solve this, Stewart & James Bespoke deployed WooRec.
Note: Depending on their scale, they leveraged WooRec Private Deployment for the perfect balance of speed and control.
The transformation wasn’t instant. We architected a phased evolution of their recommendation engine:
Phase 1: Expanding the Candidate Pool
Powered by WooRec Strategy Module
We needed to move beyond simple keyword matching. We implemented a Hybrid Recall strategy:
- Foundation: We started by ensuring popular items were visible via Hot Retrieval, solving the Cold Start problem.
- Advanced: Vector Retrieval (Embedding)
- The Logic: We mapped users and items into a high-dimensional vector space using FAISS/Graph Embedding.
- The Result: This allowed us to capture “latent interests”—finding items that are semantically related, not just textually similar.
Phase 2: The Model Evolution (LR to Deep Learning)
Powered by WooRec Model Serving
This is the core of the engine. To achieve the target Conversion Rate, we iterated through three stages:
- The Baseline (Logistic Regression): Initially, we used linear models. While fast, they failed to capture complex feature interactions.
- The Upgrade (DeepFM): We introduced Deep Factorization Machines to learn high-order feature interactions, significantly improving accuracy on sparse data.
- The Final State (ESSM):
- Why this model?: To solve the CVR estimation bias and balance CTR & CVR goals, we deployed Entire Space Multi-Task Model (ESSM). This model is designed to handle the entire sample space, correcting the bias in CVR estimation that occurs when only the clicked samples are used.
Phase 3: Traffic Control & Business Logic
Powered by WooRec Rule Engine
Raw scores are just probability predictions. To align with business goals, we applied a Traffic Control Layer:
- Diversity (Scatter/Shuffle): We implemented a sliding window rule—no more than 2 items from the same category in a row—to prevent visual fatigue.
- Business Injection (Hard Insertion): Specific slots (e.g., Position 4 and 10) were reserved for
Stewart & James Bespoke’s strategic partners or high-margin house brands. - Dynamic Weighting: We boosted items based on Profit Margin, ensuring the AI drives not just clicks, but sustainable revenue.
The Seamless Frontend Experience
Here is how these intelligent recommendations appear on the Stewart & James Bespoke storefront:
*Figure 1: The result of WooRec's engine—hyper-relevant product recommendations displayed to the user.*The Impact: 77.1% Growth
The speed of deployment meant faster results. By toggling on these strategies, Stewart & James Bespoke achieved:
- AOV (Average Order Value): Increased by 37.5% (from $1200 to $1650).
- Return Rate due to fit issues: Improved by 66.7% (reduced from 15% to 5%).
- LTV (Lifetime Value) through accessory cross-selling: Increased by 50% (from $2800 to $4200).
- Conversion Rate: Increased by 77.1% (from 3.5% to 6.2%).
- Customer Acquisition Cost: Reduced by 33.3% (from $180 to $120).
- Repeat Purchase Rate: Increased by 52% (from 25% to 38%).
Customer Voice
“Moving from manual rules to ESSM was a turning point. The system now balances user intent with our business inventory logic perfectly. The 77.1% lift in Conversion Rate speaks for itself.” — Michael Chen, CTO at Stewart & James Bespoke
Ready to Configure Your Growth?
You don’t need a team of data scientists to build a world-class recommendation engine. With WooRec, it’s just a matter of configuration.