Client case study · E-commerce and retail technology platform · Agentic commerceDeployed on AWS AgentCore

From first message to confirmed order.

An agentic shopping assistant that understands what a customer needs, finds the right handful of products, and carries them all the way to checkout in one conversation.

  • Understands intent: trip, group size, season and budget, picked up from plain words.
  • Recommends, not lists: two strong options, with the better pick flagged.
  • Transacts: cart, budget tracking, discounts and checkout, all in the chat.
ClientE-commerce and retail technology platform
EngagementParamount engagement
Built onClaude · Bedrock AgentCore
Context
Live catalogevery product
Garmin Tent 327
Garmin Tent 327Backpacking · 4.6★$215.79
Best pickThe North Face Tent 777
The North Face Tent 777Family trips · 4.2★$281.65

Meet our client

Client
E-commerce and retail technology platform
Industry
Ecommerce & Retail Technology
Market
AI-powered & agentic commerce

In a nutshell

An e-commerce and retail technology platform engaged Paramount to design and build a production-grade shopping assistant as part of an agentic ecommerce initiative on AWS Bedrock AgentCore, focused on camping and outdoor gear. Customers describe what they need in their own words; the multi-agent assistant searches a live catalog, compares with context, manages the cart and checks out, with memory that persists across every turn and every visit.

01 · The problem

Browse, hesitate, leave.

Customers know the goal, not the product. Keyword search only hears a word or two of what they say.

Industry figure
70%+

of online carts are abandoned. This assistant works on one part of the problem: helping customers find and choose the right product.

What was going wrong
  • They know the goal, not the product: customers arrive to solve something (a trip, a home office) without knowing what to buy.
  • Search returns a wall of options: one keyword brings back hundreds of results, with no guidance on which is right.
  • Keyword search can't converse: it can't take in context or guide a customer from a need to a decision.
  • Assistants forgot everything: existing chat tools lost context between steps and couldn't run a cart or a checkout.
The needGuide each customer from “I have a need” to “I have the right product”, in their own words.
02 · The complication

A conversation that never loses its place

AgentCore can route turns of the same conversation to different runtime containers. State kept only in one container's memory is not there when a turn lands in another.

Five turns, three containers
Container A
Container B
Container C
Persistent state, outside the containersNot used
S3Conversation history
DynamoDBSession: trip, budget, results
DynamoDBCart
DynamoDBCustomer profile

Illustration. When a turn lands on a different container, only state stored outside it carries over.

What had to hold in production
  • State outside the process: session, cart, history and profile persist in DynamoDB and S3, so any container can pick up a turn, and the conversation carries over through recovery and later visits.
  • Structured output for the screen: every reply carries text plus signals that tell the React UI which panel to draw.
  • Relevant retrieval: catalog search had to stay accurate across very different ways of asking, with a Knowledge Base fallback.
  • Deterministic money moves: cart and checkout run through tools with fixed contracts, not free-form model output.
03 · The resolution

An agent, not a widget

One orchestrating agent that reasons with Claude and acts through tools. Tap any part to see its job.

Specialists and tools
Memory
Claude SonnetReasoning engine
Bedrock AgentCoreAgent runtime
Strands SDKOrchestration
FastAPIAPI layer
React + WebSocketReal-time UI
DynamoDB + S3State & memory
How it's put together
  • One orchestrator, many tools: Claude decides what to do each turn and calls research, profile, cart and panel tools.
  • Retrieval-augmented search: a Bedrock Knowledge Base with Titan embeddings and S3 Vectors backs up catalog search.
  • Text plus structure: each reply is a ChatResponse with the message, the panel to show, products, cart and context pills.
  • Not a recommendation widget, not a scripted bot: it reasons, searches, compares, carts and checks out, across any catalog.
04 · How it works

From hello to checkout, one conversation

A returning customer plans a rainy August trip to Yellowstone with a $2,000 budget. Step through each turn and see what the agent shows, thinks and sends.

CampGear AgentAI shopping assistant · recreated from the live demoCONNECTED
Context pills appear here as the customer talks
How the agent thinks
  1. 1Understands intentUse case, budget, constraints
  2. 2Searches the live catalogThe right handful, not hundreds
  3. 3Compares with contextOnly the attributes that matter
  4. 4Recommends the best fitFlags the better pick, proactively
  5. 5Carts & checks outConversational and transactional
Memory: DynamoDB + S3 keep the cart, session and profile on every turn.

What the agent sent the screen this turn: a structured ChatResponse alongside the reply text.

What happened in this conversation
  • Context from one sentence: “August” and “Yellowstone” became pills with no form or dropdown, and the agent knew August means afternoon rain.
  • Two options, not hundreds, with the better pick flagged; the comparison used only weight, capacity, season and best use.
  • The cart moved with the conversation: “add two more tents” updated quantity, pricing and the live budget tracker at once.
  • One last useful pick: water purification tablets, flagged as essential for backcountry safety, added with a single “sure”.
Confirmed orderCheckout runs through the deterministic checkout tool, not the model: it totals the cart held in DynamoDB, applies the bundle and loyalty discounts and confirms the order. The purchase is then added to the customer’s profile.
05 · Returning customers

Recognised, not reset.

Most stores greet a loyal customer like a stranger. This agent loads who they are from the first message, and rewards them at checkout.

Second visit, first message
How recognition works
  • A persistent profile: location, group size, season, experience level and past purchases, kept in DynamoDB.
  • Loaded from the first message, so the agent can say “welcome back” and pick up where the last trip left off.
  • Rewarded at checkout: a 10% bundle discount and a 5% loyalty discount appear as clear line items, nothing to ask for.
  • Updated after every order: new purchases are added to the profile, so the next visit starts even further ahead.
Proof

Real screens from the live demo

Tap any screen to see it full size.

06 · What makes it different

Not search. An advisor.

When there's a smarter choice for the customer's situation, the agent says so. It doesn't wait to be asked. Tap a card to flip it.

Why it stands apart
  • Production-grade multi-agent orchestration on AWS Bedrock AgentCore, not a prototype chatbot.
  • Structured UI signals travel with every conversational reply, so the storefront stays rich and in sync.
  • Distributed session resilience: memory survives containers, turns and visits.
  • Deterministic cart and checkout wired into the AI's reasoning, so the money side is always exact.
07 · The result

More carts, bigger baskets

How the basket grew in one conversation

Figures from the live demo conversation above.

Guided to purchase

Fewer abandoned carts

Customers leave with the right product, not a wall of options they scroll past and abandon.

The full solution

Higher order value

The agent guides the whole purchase and adds a final complementary pick at checkout.

Scales without headcount

Always-on associate

Discovery, comparison, cart and checkout, any catalog, any vertical, around the clock.

Associate
Agent
00:0012:0024:00
The resultBetter conversion on the traffic the business already pays to acquire, enterprise-ready on AWS Bedrock, DynamoDB and S3, with no session state ever lost.
AWS Bedrock AgentCoreClaude Sonnet 4.6Strands SDKFastAPIPythonDockerReact + WebSocketDynamoDBAmazon S3Bedrock Knowledge BaseTitan EmbeddingsS3 VectorsAWS CodeBuild
What the engagement delivered
  • A full multi-agent shopping assistant deployed on AWS Bedrock AgentCore.
  • End-to-end conversational shopping, from discovery to order confirmation.
  • Persistent memory and loyalty-aware personalisation across sessions.
  • A reusable architecture for future agentic commerce experiences, in any catalog or vertical.
AI-native ecommerce

Not search. An advisor.

An agent that reasons about what each customer actually needs, from first message to confirmed order.

What a first conversation covers
  1. 01Your business objective
  2. 02The technical context
  3. 03The right next step
Discuss a project View all case studies →