Skip to content
Case Study

Leading Jewelry Retailer Transforms Its IBM Sterling OMS Support with AI Engineer

We Didn’t Bill for a Bigger Team. We Built One That Pays for Itself

A leading North American specialty jewelry retailer runs one of the industry’s most complex omnichannel fulfillment networks—hundreds of stores, multiple distribution centers, and fulfillment paths spanning vendor drop-ship, ship-from-store, and same-day delivery. As order volume grew, the support operation behind it hadn’t kept pace: engineers were navigating four disconnected systems just to resolve a single incident, driving up resolution times and creating heavy dependency on a handful of senior experts

Nextuple built the answer: the AI Support Engineer, a conversational AI assistant that gives engineers one interface instead of four. It automatically routes every query to the right system—OMS data, database diagnostics, or operational runbooks—so engineers get answers, not a scavenger hunt.

The impact is immediate and compounding. Phase 1 alone cuts incident resolution time by ~30% and delivers a 10% to 15% cost reduction—funding the next phase from day one. By Phase 2, automation coverage reaches ~40% of total support activity, with 24/7 monitoring and no shift constraints. The result: a support team that spends less time hunting for answers and more time driving the business forward.

The customer

One of North America’s Most Complex Omnichannel Jewelry Operations

 

A leading North American specialty jewelry retailer operating one of the most complex omnichannel fulfillment networks in the industry. With hundreds of retail locations, multiple distribution centers, and a rapidly growing professional and commercial customer base, the retailer serves both direct consumers and wholesale clients across in-store, online, and BOPIS channels.

INDUSTRY
Specialty Jewelry Retail & Distribution
CHANNELS
In-store, Online, BOPIS
OMS PLATFORM
IBM Sterling Order Management System
SUPPORT MODEL
Nextuple Managed Services Production Support
THE CHALLENGES

Four Systems. One Incident. Too Much Time in Between

The retailer’s Sterling OMS production support operation had outgrown its tooling. Order exception volumes were growing alongside the business, but the support workflow had not evolved—leaving engineers dependent on a fragmented set of systems with no unified interface.

Support engineers simultaneously navigated Sterling OMS consoles, IBM DB query tools, shared documentation repositories, and ticketing systems to resolve a single incident. This context-switching drove up mean time to resolution (MTTR) and created structural dependency on senior engineer institutional knowledge—making onboarding slow and escalation rates high.

An analysis of support effort revealed the majority of engineer time was consumed by activities directly addressable through automation:

SUPPORT EFFORT ANALYSIS

Share of total engineer time, by activity

Activity & What It Involves
Effort
Issue Resolution
Manual order lookup, triage, and exception
handling across OMS and IBM DB
35 %
System Monitoring
Reactive monitoring: CPU, memory, queue depth,
JVM status, stuck orders, payment failures
25 %
Data Reconciliation
Cross-system data validation, integration issue
resolution, and feed reprocessing
15 %
Reports & Coordination
Health checks, operational and status reporting—
all manual with no automation
15 %
Continuous Improvement
KPI monitoring, runbook updates, and
automation backlog
10 %
* Estimates derived from support task execution data observed in live production environments
THE SOLUTION

One Interface Instead of Four

Nextuple delivered the AI Support Engineer—a purpose-built, multi-turn AI assistant integrated directly into the Sterling OMS production support workflow. Built on Azure OpenAI GPT-4o and deployed via a React-based web interface, it gives engineers a single conversational interface that autonomously routes queries to the right tool: Sterling OMS REST API, IBM DB Query Servlet, or a semantically indexed SOP knowledge base.

Roughly 30% to 40% of total OMS support activities are strong candidates for automation. The AI Support Engineer targets this directly—shifting teams from reactive issue resolution to proactive, strategic value creation. Phase 1 goes live in under four weeks, establishing monitoring and reporting automation before more complex chatbot and order-action capabilities follow.

THREE PHASES TO SMARTER SUPPORT

PHASE ONE • WEEKS 1 TO 4
Alerts & Monitoring
 
Automated proactive
monitoring
AI-powered anomaly
detection
Daily email status reports
Teams channel alert
15%
initial
cost reduction
PHASE TWO • WEEKS 5 TO 8
Act & Remediate
 
Natural language order
lookup & modification
Hold removals, cancellation
analysis
SOP execution with human
approval
10%
additional
cost reduction
ONGOING ENHANCEMENTS
Intelligent Chatbot
 
Context-aware SOP
instructions
Real-time OMS data via API
& DB queries
Faster troubleshooting &
onboarding
Always-on knowledge
companion
Full optimization
run rate

WHAT WE DELIVERED


Capability What It Does
Natural Language Order Inquiry Query order status, line items, and fulfillment state directly from Sterling OMS via conversation
Autonomous Tool Routing AI selects OMS API, IBM DB, or SOP retrieval based on query intent—no manual tool selection required
SOP Knowledge Retrieval Semantic vector search across 40+ indexed operational runbooks with inline document citations
IBM DB Query Support Natural language to IBM DB Query Servlet—raw diagnostics without external dependency
Order Modification with Guardrails Write-back to Sterling OMS with mandatory engineer confirmation; supported via user permissions
Multi-Ticket Session Management Parallel support tickets per tab with independent conversation history
45-Day Audit Trail Full conversation and tool-call log in PostgreSQL—supports compliance and post-incident review
Admin & User Provisioning Self-service user management; Azure AD SSO with role-based access control
THE RESULTS

The Math That Pays for Itself

The AI Support Engineer delivers measurable improvements across cost, speed, and coverage from the first phase of deployment. Figures are based on observed outcomes from live OMS support engagements; actual results will vary based on team size, current FTE mix, and scope of automation.

35% Support activities automatable in OMS operations
15% Cost reduction inphase 1 run rate
30% Cumulative reduction post-phase 2 run rate
30% Faster incident resolution

OUTCOMES

Unified support interface

A single conversational interface replaces context-switching across Sterling OMS consoles, IBM DB tools, and documentation repositories.

Reduced MTTR

Autonomous tool routing delivers cited, actionable responses — engineers get answers without knowing which underlying system holds them.

Faster engineer onboarding

Institutional SOP knowledge is semantically searchable and surfaced on demand, rather than locked in senior engineer expertise.

Guardrails enforced at the AI layer

Write-back actions require explicit confirmation, with a full 45-day audit trail for every interaction and tool call.

Self-financing model

Phase 1 cost reduction funds subsequent phases—the solution operates within the existing support budget.

Scalable across the enterprise

Multi-tenant architecture allows new client onboarding without platform changes, scaling across business units and geographies.

iStock-2013971150

Your OMS Support Team Shouldn’t Need Four Systems to Answer One Question.


See how Nextuple applies AI to IBM Sterling OMS operations, managed services for other order management systems and support modernization.