AIToday
AI Safety & AlignmentAI Business & IndustryAmazon AI BlogPublished: Jul 25, 2026, 01:00 JST

AWS blog: next-best-product recommendation system for banking using deep learning

AWS blog: next-best-product recommendation system for banking using deep learning

3 Key Points

  1. What happened

    AWS published an architectural overview of a Next-Best-Product (NBP) recommendation system for banking, built on Amazon SageMaker AI and PyTorch. The system uses a multi-tower neural network with four specialized towers (Sequence, Transaction, Customer, and Behavioral) that process different types of customer data, fused via learned attention to provide both accuracy and per-customer explainability.

  2. Why it matters

    Banks struggle to translate customer data—transaction histories, product ownership, demographics, behavioral patterns—into actionable personalized product recommendations; traditional rule-based systems and collaborative filtering fail to capture complex temporal patterns in how customers adopt products. This architecture addresses that gap while satisfying regulatory requirements for explainable predictions, making it relevant for financial institutions managing heterogeneous customer data.

  3. What to watch

    The solution requires ml.g5.12xlarge GPU instances (192 GB RAM, 4× NVIDIA A10G GPUs) for training, uses Snappy-compressed Parquet on Amazon S3 for storage, and orchestrates the full pipeline via Amazon SageMaker Pipelines. AWS warns that deploying this creates billable resources; users must follow cleanup instructions to avoid ongoing charges.

Ask the AI about this article →

Summaries like this, in your inbox every morning.

Context & Analysis

Banks have long struggled to convert their rich internal datasets into actionable product recommendations. The article identifies a specific gap: traditional rule-based systems and collaborative filtering approaches cannot capture the temporal order in which customers adopt products—they see only a static list of what each customer owns, not the journey of how they acquired those products. The multi-tower architecture addresses this by assigning different neural network towers to different data modalities (sequences, transactions, demographics, behavior), each optimized for its data type, rather than forcing all data through a single generic pathway. This specialization both improves model capacity utilization and creates a clearer path to explainability: the learned attention mechanism that fuses the towers can show, per customer, which towers (and therefore which aspects of their profile) most influenced the recommendation.

The technology choices reflect production considerations for financial services. AWS Glue provides serverless ETL for normalizing data arriving from multiple banking systems with inconsistent schemas—a universal challenge in banking. The use of Parquet with Snappy compression on S3 offers both cost efficiency (3–5× compression over CSV) and performance gains (column pruning, predicate pushdown). PyTorch was selected for its dynamic computation graphs, which the article notes are necessary to handle variable-length customer sequences via pack_padded_sequence, and for its native SageMaker AI integration. The data pipeline is split into two stages: AWS Glue for schema unification and temporal feature engineering, then Amazon SageMaker Processing for ML-specific operations like sequence padding and windowed aggregations across 7-, 30-, 60-, 180-, and 365-day windows.

FAQ
What are the four towers in this recommendation system?
The Sequence Tower processes product adoption history using a 2-layer GRU to capture temporal patterns; the Transaction Tower processes time-windowed transaction features with a 2-layer MLP; the Customer Tower handles demographics, income, family, and account features with a 2-layer MLP; and the Behavioral Tower processes segmentation codes, loyalty, and usage patterns with a 2-layer MLP. All towers output 64-dimensional vectors that are fused via learned attention.
What AWS services does this solution require?
The solution uses Amazon SageMaker AI (for training and inference), Amazon S3 (for data storage in Snappy-compressed Parquet format), AWS Glue (for serverless ETL with PySpark), Amazon SageMaker Processing (for ML-specific feature engineering), SageMaker Pipelines (for orchestration), and CloudWatch (for monitoring training metrics, inference latency, and model drift).
What are the software and compute requirements?
The solution requires Python 3.11+, PyTorch 2.9+, Pandas 2.3+, NumPy 2.3+, scikit-learn 1.7+, and Dask 2025.11+. Training uses ml.g5.12xlarge GPU instances (192 GB RAM, 4× NVIDIA A10G GPUs). An AWS account with appropriate IAM permissions for SageMaker AI, S3, AWS Glue, and CloudWatch is required.
Amazon AI BlogRead Original Article

Get the latest AI Safety & Alignment news every morning

For example, today's edition would include:

  • Beijing warns of six AI risks, rejects US slowdown callsSemafor Tech · 2h ago
  • US House takes up data center bill as AI rules push growsSemafor Tech · 2h ago
  • Jacob Coxon's AI doom warning goes mainstream after Anthropic exitFortune AI · 2h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleGoogle raises capex outlook to $195–205B as AI compute demand stays tight