All applications

Shopping Assistance

Shop by chat.Run your store.

A storefront with AI from ECV Enterprise Assistance to help shoppers choose products and add them to a cart, with sales, orders, inventory and campaign planning in one workspace.

  • ECV Enterprise Assistance
  • Store API

Connect what shoppers need with the work behind the store: product discovery, order information, inventory and the next relevant offer.

Help shoppers. Equip the store.

A shopping assistant for customers, with a workspace for the teams managing the store.

Say what you need.Let AI help you choose.

An assistant powered by ECV Enterprise Assistance helps shoppers choose products and add them to a cart through conversation, connecting their needs with the store catalog.

  • Storefront, categories, prices and search controls
  • Store API grounding for price and stock is documented
  • AI/cart support is owner-confirmed; the complete flow has not been independently tested
Your shopping assistant

Example conversation · No live AI call or purchase

I need a bag for a short trip. A bag for short trips. Review it, then confirm your selection. An everyday travel bag. Added to the example cart. Ready for your review.
Example cart · 1 item1
AI shopping · Cart actions

See sales beforeplanning the next move.

Sales pulse presents paid-order revenue, order count, units and average order value, alongside daily trends and top products.

  • Monthly/date-range controls and a CSV export entry point
  • The pictured AI business brief is marked Demo estimate
  • Environment figures are not customer outcomes or benchmarks
Sales pulse · Dashboard

Follow the orderfrom both sides.

Store teams can find orders and view fulfilment statuses. Shoppers have Track order to review progress, events and an order summary.

  • Statuses range from Placed to Delivered or Cancelled
  • Status actions were observed, but writes were not tested
  • Paid status does not establish payment-gateway integration
An order’s journey

Example statuses, not an actual order

  1. Placed
  2. Paid
  3. Processing
  4. Shipped
  5. Delivered
Shopper · Track orderStore team · Orders
Orders · Track order

Know what is availablebefore planning stock.

Stock health brings availability, sales coverage and balance together, with inventory management and purchase-order views.

  • Incoming units and received history are separate
  • Coverage and balance need paid-sales history
  • Building baseline is not a demand forecast
Stock health · Inventory

Turn an idea intoa brief worth reviewing.

Start with an example, your own idea or customer history in Campaign studio, choose a product and review the brief before taking it further.

  • Idea → Product → Brief review
  • Example trends are not live TikTok research
  • Your team reviews and decides what to use
Growth · Campaign studio

Find a relevant reasonfor customers to return.

Customer insights groups signed-in customers using paid-order history so CRM teams can prepare follow-up ideas and audience briefs.

  • First-time, repeat and follow-up groups
  • Groups can overlap; rules do not predict churn
  • This page prepares briefs and does not send customer messages
Growth · Customer insights

Give an offer itsproduct and schedule.

Promotion studio provides code, message, discount, product and date fields, with offer statuses for store teams to review.

  • Draft, Paused, Ended and Publish/Pause controls were observed
  • The supplied image is an unsubmitted form
  • Pricing and checkout behavior need evaluation before rollout
Promotion studio

Different teams. Different questions.

Illustrative evaluation scenarios, not customer cases or verified end-to-end results.

“Which products are right for me?”
Shopper · E-commerce

Choose for a specific need

Prepare approved catalog, price and stock data, then demonstrate the conversation-to-selection-to-cart journey in an authorized environment.

“Which orders and stock need attention?”
Operations · Inventory

Prioritize store work

Review orders, availability and incoming stock. Evaluate status changes and receiving separately in the agreed demonstration.

“What could bring customers back?”
Marketing · CRM

Prepare an offer for review

Choose a purchase-history group, prepare a campaign idea, then review the product and offer terms. This example does not automatically send messages.

Shape a demo around your store.

Begin with approved example data and a scope before testing real actions.

  1. Choose a journey

    Identify a shopping, order-management or marketing use case and the shopper/admin roles involved.

  2. Prepare permitted data

    Bring a catalog, prices, stock, licensed images and synthetic orders, plus payment and fulfilment requirements to assess.

  3. Review the results together

    Walk through storefront and operations, then agree on authorized AI/cart and write-action tests with acceptance criteria.

Technical information

Evaluation scope
Intended audienceE-commerce, operations, inventory and marketing/CRM teams
User experiencesShopper storefront and admin console; TH/EN controls observed, not every flow tested
AI and store dataECV Enterprise Assistance + Store API are documented; model, API version and authentication remain unverified
ArchitectureThe 2 October 2026 snapshot describes AWS serverless/CDK in Singapore, not a live deployment verification
Data and accessProduction roles, isolation, AI data policy, retention, deletion and export remain unverified
Capacity and operationsCapacity, rate limits, retry/idempotency, backup/DR and SLA remain unverified
Evidence scopeBrief reviewed 20 October 2026: UI/document reading and owner confirmation for AI/cart; no complete action-flow test

The store and its data flow

Adapted from the 2 October 2026 architecture snapshot. This explains components, not live system health.

On smaller screens, scroll the diagram sideways to follow every connection.

AWSRegional services: Singapore · CloudFront: Global
Customer / AdminWeb browser · HTTPS
Amazon CloudFrontHTTPS · /api/*
Amazon S3Web assets · Private bucket
Amazon API GatewayStore + AI routes
Commerce LambdaProducts · Carts · Orders
Amazon DynamoDBStore data + AI state
Assistant LambdaCustomer + Admin AI
AWS Secrets ManagerResolved at deployment
ECV Enterprise AssistanceExternal AI service
CloudFront branches to web assets and API routes. Commerce and Assistant use DynamoDB; Assistant connects to Store API and ECV, with Secrets Manager supplying deployment configuration.

Connect AI with ECV Enterprise Assistance

Explore embedded storefront chat or a backend connection for a custom shopping experience.

StorefrontThe shopper asks a question
Web WidgetChat embedded in the website
ECV Enterprise AssistanceAI assistant · Responses
Question / requestResponse
Web Widget · Embedded chat

Web Widget is an additional integration approach requested here, not a verified deployment in the reviewed Shopping Assistance. Product data and cart-action scope need team assessment.

Moving connections illustrate communication without making service calls. Field-level AI data, credential handling and log storage remain unverified.

Frequently asked questions

Shopping Assistance

Start with your store’s needs.

Bring a shopping journey and an operations challenge to eCloudvalley so we can agree what to demonstrate and evaluate.

More to explore

MCP StudioAI Lens for Claude EnterpriseAI Lens for Bedrock