01 · Four years of transactions
AWS Glue and Amazon EMR prepared about 20 GB of transactions spanning four years in Amazon S3.
Customer work · Distribution
A distributor wanted to improve product discovery across a 16,000-dealer network. BluePi prepared catalogue, dealer, purchase, and SKU data on AWS and built recommendation paths for related products, similar-dealer behavior, and seasonal stocking.
The distributor served 16,000 dealers through app and web portals, but personalization was limited and behavioral data covered purchases without navigation events. BluePi prepared catalogue, user demographic, dealer, SKU, and purchase-history data on AWS and built recommendation paths for product discovery and stocking needs.
01 · Four years of transactions
AWS Glue and Amazon EMR prepared about 20 GB of transactions spanning four years in Amazon S3.
02 · Three discovery routes
Recommendations used related and frequently co-purchased products, similar-dealer purchases, and seasonal demand for the next two months.
03 · Ordering portal delivery
Recommendation sets reached the dealer app and web experience and increased click-through rate by 15 percent.
Catalogue, user demographic, dealer, SKU, and purchase-history data landed in Amazon S3. AWS Glue and Amazon EMR prepared the transaction record for modelling, and recommendation logic used HRNN, collaborative filtering, SIMS, and time-series forecasting. A separate documented variant used Amazon Personalize.
Catalogue, dealer, user, SKU, and purchase records were transformed into model-ready inputs on AWS.
Related products, similar-dealer behavior, and seasonal stocking addressed distinct discovery needs.
Recommendation sets were delivered through the dealer app and web experience.
Where this pattern fits
This case is relevant when a distribution network has purchase history and catalogue data but limited product discovery or behavioral context.
Use these prompts to decide whether the case fits your operating problem and what a first deployment should prove.
A first engagement can prepare one catalogue and dealer segment, build one recommendation path, deliver it through a controlled portal experience, and compare click behavior against the existing discovery route.
Open a section to review the customer problem, implementation, business change, and architecture.
Dealers placed category orders through app and web portals, but the experience offered limited personalization. Behavioral data covered purchase history without navigation or exploration events, constraining how the system could understand current interest.
Product catalogue, user demographic, dealer, SKU, and purchase-history data was staged in Amazon S3 and prepared for recommendation modelling. The system produced three recommendation sets.
A second implementation path prepared the same source data in Amazon Personalize format and built content, category, and seasonal recommendation use cases with Amazon Personalize.
The recommendation experience increased click-through rate by 15%.