
AI Use Case Discovery Across Loyalty, Pickup and Returns for a Department Store Chain
Let's Connect
Overview
What we built
A 33-store department store chain wanted one AI answer for loyalty, pickup and returns, but ideas were arriving from every department with no shared way to judge them. A structured discovery programme turned that noise into a small set of costed, ranked initiatives.
In plain terms: this mid-market department store chain runs 33 stores, and its board had decided it wanted an AI answer for three things at once, its popular loyalty programme, its in-store pickup service and its busy returns operation. The trouble was that ideas were arriving from every department with no shared way to judge them, the underlying data sat in four separate systems, and two early vendor demos had already stalled because nobody could actually define the problem being solved.
We led a structured AI use case discovery programme built around nine cross-functional workshops across merchandising, loyalty, stores and operations, data walkthroughs of the four core systems, and opportunity sizing against two years of transaction history. Every candidate use case was scored on value, feasibility and data readiness, then shortlisted into costed business cases with a recommended delivery order. From 44 candidate use cases captured across the nine workshops, 12 were shortlisted with full business cases, and the executive committee approved 3 funded builds within a month of the final prioritisation readout.
The Problem
AI ambition without direction
The chain's board had set a clear ambition: an AI answer for the loyalty programme, in-store pickup and the returns operation, all three at once. What arrived instead was noise. Ideas came in from every department, each convinced its problem was the priority, with no shared method for weighing a loyalty idea against a returns idea or a pickup idea.
The data underneath those ideas was just as scattered. Information relevant to loyalty, pickup and returns sat in four separate systems, so even a well-formed idea could not easily be checked against the data it would need. Two early vendor demos had already stalled for exactly this reason: nobody could define, in terms the data could answer, what problem the demo was actually meant to solve.
Without a shared evaluation method, the loudest department tended to win the argument rather than the strongest idea, and the board's ambition for loyalty, pickup and returns stayed exactly that, an ambition, while two stalled vendor demos left staff wary of the next pitch.
Ideas without evaluation
Ideas arrived from every department with no shared method for scoring them, so decisions defaulted to whichever team argued loudest rather than the strongest case.
Four separate systems
Data relevant to loyalty, pickup and returns sat in four separate systems, making it hard to check even a well-formed idea against real evidence.
Stalled vendor demos
Two early vendor demos stalled because nobody could define the problem being solved, leaving staff wary of the next pitch before discovery even began.
Three priorities, no order
The board wanted an AI answer across loyalty, pickup and returns at once, with no agreed order for which to tackle first.
What it was costing them
Every idea debated without a shared evaluation method was staff time spent arguing rather than building, and every stalled vendor demo left the returns, pickup and loyalty teams a little more sceptical of the next one. With relevant data spread across four separate systems, even the strongest idea could not be quickly checked, so the chain risked funding whichever pitch was loudest rather than the one the transaction history actually supported.
The Solution
Workshop-driven use case discovery
We designed the discovery programme to replace department-by-department pitching with one shared process. Nine cross-functional workshops brought merchandising, loyalty, stores and operations into the same room, so a loyalty idea and a returns idea were finally being compared on the same terms.
Alongside the workshops, data walkthroughs of the four core systems established what the underlying data could actually support, closing the gap that had stalled the two earlier vendor demos. Opportunity sizing against two years of transaction history then let every candidate use case be checked against real evidence rather than assumption.
Each candidate use case was scored on value, feasibility and data readiness using the same criteria, then shortlisted into costed business cases with a recommended delivery order, so the executive committee could fund a sequence rather than argue over which department went first.
Key decisions
Bring departments into one room
Nine cross-functional workshops across merchandising, loyalty, stores and operations replaced separate department pitches with one shared discovery process.
Check data before scoring ideas
Data walkthroughs of the four core systems established what the data could support, addressing the exact gap that had stalled two earlier vendor demos.
Size opportunity against real history
Opportunity sizing against two years of transaction history meant every use case was checked against evidence rather than a department's assumption.
Score on three consistent criteria
Value, feasibility and data readiness scored every candidate use case the same way, regardless of which department proposed it.
Recommend a delivery order
The shortlist of costed business cases came with a recommended delivery order, so the executive committee could fund a sequence, not just a list.
Measurable Impact
What changed after launch
The programme turned scattered pitching into a ranked, evidence-based shortlist. From 44 candidate use cases captured across the nine workshops, 12 were shortlisted with full costed business cases, giving the board the loyalty, pickup and returns answer it had originally asked for, but now backed by two years of transaction history.
The top-ranked initiative, loyalty-offer targeting, carried a projected 3.1% incremental margin on promoted categories, while returns-fraud screening ranked second with an estimated 15% reduction in fraudulent refund value at pilot scale. The executive committee approved 3 funded builds within a month of the final prioritisation readout, a decision speed the department-by-department pitching had never achieved.
Idea evaluation
Department pitches with no shared evaluation method
44 use cases scored, 12 shortlisted with business cases
Data visibility
Relevant data scattered across four separate systems
Walkthroughs of all four systems inform every business case
Top initiatives
No ranked view of loyalty, pickup or returns ideas
Loyalty targeting projected at 3.1% incremental margin
Funding decisions
Two vendor demos stalled with no clear problem defined
3 funded builds approved within a month of readout
Headline results
44 candidate use cases captured from 9 workshops, shortlisted to 12 with full business cases
Top-ranked initiative, loyalty-offer targeting, sized against 2 years of transaction data with a projected 3.1% incremental margin on promoted categories
Returns-fraud screening ranked second with an estimated 15% reduction in fraudulent refund value at pilot scale
Executive committee approved 3 funded builds within a month of the final prioritisation readout
Tech & Tools Used
What powered the build
Every tool below earned its place in this engagement. Here is the part each one played.
Python (pandas)
Profiled transaction and returns data during opportunity sizing, quantifying the two years of history behind the top-ranked use cases.
Snowflake
Held the two years of transaction history and the walkthrough extracts from the four core systems, giving the programme one place to size every idea.
dbt
Modelled the shared metrics behind the value, feasibility and data-readiness scores, keeping the candidate use cases comparable.
Fivetran
Replicated data out of the four core systems without custom pipeline work, so the data walkthroughs could start quickly.
Power BI
Powered the opportunity-sizing dashboards used to project the loyalty-offer targeting margin and the returns-fraud screening impact.
Excel
Tracked the costed business cases and recommended delivery order shared with the executive committee for the final prioritisation readout.
Miro
Hosted the nine cross-functional workshops where merchandising, loyalty, stores and operations scored the candidate use cases together.
Notion
Holds the shortlisted business cases and delivery order, so every shortlisted use case stays traceable from workshop to funding decision.
Jira
Carries the backlog for the funded builds approved by the executive committee, with owners attached to each initiative.
Ready to Build your Retail & E-Commerce Business with AI Use Case Discovery
Ask Byte
Ask Byte
Typically replies instantly
just Now
Hi! I'm OrganByte's assistant. How can I help you today?
AI-generated content may be incorrect

