Case Study | Implementation Strategy
A $100M Clothing Brand Picked Two Categories and Ignored the Rest. Here's Why.
Thousands of SKUs across multiple brands. They picked dresses and denim, launched in 12 weeks. Everything else could wait.
Published February 2, 2026 · 7 min read
TL;DR
- 1. A major clothing retailer narrowed to two categories instead of optimizing their entire catalog
- 2. Leadership quote: "You don't want to tackle everything out of the gate"
- 3. Nexus Apparel migrated platforms because their legacy system was too slow for AI agents
- 4. Phased approach beats perfection—Weeks 1-4 audit, Weeks 5-12 launch
- 5. 75% of NRF 2026 attendees are implementing or planning agentic commerce right now
The Mistake Most Mid-Market Merchants Make
You have 3,000 SKUs. Your competitor just went live on ChatGPT. Your impulse is to get every product ready before you launch.
That's how you end up launching in Q4 instead of Q2. By then, your competitor has six months of conversion data and knows exactly which product attributes AI agents care about. You're starting from zero.
A $100M+ clothing brand looked at their catalog—thousands of products across multiple retail chains—and made a different call. They picked two categories and launched. Everything else could wait.
This isn't about being cautious. It's about being strategic when you don't have infinite engineering resources.
What They Actually Did
At NRF 2026, URBN's leadership (Urban Outfitters, Anthropologie, Free People) walked through their approach. Instead of making their entire catalog AI-ready, they focused on where impact would be highest.
Their criteria:
- High search volume in AI interfaces
- Strong margins
- Clear differentiation from competitors
- Products where conversational discovery adds value
Dresses and denim fit. Accessories, home goods, and basics didn't make the first wave.
"You don't want to tackle everything out of the gate."
— URBN Leadership, Stripe NRF 2026 Roundtable
This came from a company with significant technical resources. If they're being selective, what does that tell you about trying to do everything at once?
The Nexus Apparel Case: When Your Platform Can't Keep Up
Nexus Apparel is a mid-market retailer selling across multiple channels. Their problem wasn't strategy. It was infrastructure.
Their legacy system couldn't serve product data fast enough for AI agent queries. API response times were over 500ms. They lacked the structured metadata agents need to make recommendations. They couldn't capture traffic from AI shopping devices like Rabbit R1 or Humane AI Pin.
Their decision: Migrate to headless Shopify with UCP-compliant APIs.
Their timeline:
- Weeks 1-4: Audit existing catalog, identify data gaps, map migration requirements
- Weeks 5-12: Technical integration, product data optimization, testing, soft launch
They went live in under three months. Not with their entire catalog—with their top 500 SKUs. The rest followed over the next quarter as they validated what worked.
The lesson: If your platform can't respond to agent queries in under 300 milliseconds, you're not competing. You're invisible.
The Phased Approach That Actually Works
Both URBN and Nexus Apparel used the same framework. It works for merchants with 1,000 to 10,000 SKUs who can't dedicate a full engineering team to agentic commerce.
Phase 1: Pick Your Battleground (Week 1)
Don't optimize everything. Pick 2-3 categories where:
- You have clear product differentiation
- Conversational discovery adds value
- Margins support the 4% transaction fee
- You can win against competitors
For URBN: Dresses and denim
For automotive parts merchants: Performance upgrades and compatibility-sensitive components
For electronics retailers: Products with complex specs where AI agents add value
Phase 2: Audit What You Actually Have (Weeks 1-4)
Run through your top categories and check:
- Do products have valid GTINs?
- Are titles and descriptions written for semantic search?
- Is inventory data real-time accurate?
- Do you have complete attribute data (dimensions, materials, compatibility)?
- Can your APIs respond in under 300ms?
Most mid-market catalogs fail this audit. That's fine. You're not trying to be perfect. You're trying to identify the gaps that block you from going live.
Phase 3: Fix What's Broken (Weeks 5-8)
Focus on data quality for your selected categories:
- Add missing GTINs
- Rewrite product titles for AI discoverability (semantic clarity, not keyword stuffing)
- Complete attribute data
- Implement real-time inventory sync
- Optimize API response times
Don't touch the rest of your catalog yet.
Get 200-500 SKUs ready. That's enough to go live and start learning.
Phase 4: Go Live and Learn (Weeks 9-12)
Launch with your optimized subset. Monitor:
- Which products AI agents recommend most frequently
- Which attributes drive conversions
- Where your data is still insufficient
- What your competitors are doing
Use that data to inform Phase 2 of your rollout.
Who's Already Doing This
At NRF 2026, 75% of retailer attendees said they're either implementing or actively planning agentic commerce. That's not "evaluating." That's committed.
Early adopters include:
- Petco
- e.l.f. Cosmetics
- Samsonite
- Rugs USA
- Glossier
- SKIMS
These aren't all Shopify merchants. Some are on custom platforms. Some are on Adobe Commerce. They're moving because they can't afford to wait for their platform to figure this out.
The pattern: Launch narrow, learn fast, expand based on data.
What This Means for Adobe Commerce, Miva, and NetSuite Merchants
Some platforms have native agentic commerce support. If yours does, your challenge is optimizing product data.
If you're on Adobe Commerce, Miva, or NetSuite, you have a different problem. Your platform doesn't have a native path to ACP or UCP. You need infrastructure before you can even think about data optimization.
Your options:
Option 1: Build It In-House
- Timeline: 6-12 months
- Cost: $75,000-$200,000+
- Risk: Protocol evolution requires rebuilds
- Result: You go live in Q4 while competitors learned all year
Option 2: Wait for Your Platform
- Adobe Commerce 2026 roadmap includes agentic features, but native protocol support isn't confirmed
- Miva has no publicized agentic commerce strategy
- NetSuite offers indirect access via MCP connectors (requires translation layers)
- Timeline: Unknown
- Cost: Unknown (likely significant when available)
Option 3: Use Middleware
- Timeline: 4-8 weeks to production
- Setup cost: Varies by provider and requirements
- Protocol updates: Handled automatically
- Result: You're live in Q1, learning alongside early movers
The phased approach works best when you have infrastructure that can actually support it. If your platform can't, the choice is migrate or use middleware.
The 12-Week Advantage
URBN and Nexus Apparel both went live in roughly 12 weeks. Not with everything. With enough to start competing.
By the time their competitors finish evaluating options, they'll have:
- Real conversion data from AI channels
- Product data optimized based on agent behavior
- Operational experience handling AI-driven orders
- Six months of learning that can't be purchased
The question isn't whether to do a phased launch. It's whether you can afford to launch at all with your current infrastructure.
Stop Optimizing. Start Shipping.
You don't need 3,000 SKUs ready. You need 300 SKUs live.
Pick your categories. Audit your data. Fix what's broken. Go live.
URBN picked dresses and denim. What are you picking?
12 Weeks
From audit to launch
URBN and Nexus Apparel both launched in under 3 months. Not with everything—with enough to compete.
Related Articles
Strategy
The Hidden Advantage: Why Your Messy Data Is Actually an Opportunity
Your "messy" catalog contains years of tribal knowledge. Here's how to turn it into your competitive moat.
Getting Started
Getting Started with ACP
A practical guide to connecting your catalog to OpenAI's Agent Commerce Protocol.
Performance
Sub-100ms Speed: Why API Response Time Matters for AI Commerce
If your platform can't respond in under 300ms, you're invisible to AI agents.
Your Platform Won't Do This For You
URBN had resources. Nexus Apparel had urgency. Both made the same call: narrow focus, fast execution. See where your store stands today.