I Gave a Grocery Store a Memory. Here’s What Changed.

Ishwarya Kota — Tue, 29 Sep 2026 10:32:57 +0000

I Gave a Grocery Store a Memory. Here’s What Changed.

A grocery store normally remembers inventory.

A customer remembers preferences.

An AI assistant remembers a conversation—until that conversation disappears.

I wanted to build something different: a grocery store that could remember both its customers and its own experiences, then use those memories to make better decisions later.

That became GrocerAI, a self-adaptive grocery store built around two cooperating agents: a Customer Agent that understands individual shoppers and a **Store Agent **that understands what is happening across the store.

The part that made this interesting was not the number of features. It was giving both agents persistent memory with Hindsight and making that memory influence future behavior.

Why I Needed Two Agents

A grocery store has two very different perspectives.

From the customer's perspective:

"What do I need, where can I find it, and what should I buy?"

From the store's perspective:

"What are customers asking for, what is selling, what is unavailable, and what should I do next?"

Trying to answer both with one generic assistant made the responsibilities unclear.

So I separated them.

The Customer Agent handles individual shopping experiences: product discovery, availability, missions, cart interactions, recommendations, substitutions, navigation, and personalized assistance.

The Store Agent handles operational intelligence: inventory signals, demand, stockouts, checkout activity, unmet demand, restocking recommendations, and store-level learning.

Both agents use the same fundamental loop:

OBSERVE
↓
RECALL
↓
REASON
↓
ACT
↓
RE-OBSERVE
↓
REMEMBER

The difference is what each agent is remembering.

Structured State vs. Memory

One of my biggest architectural decisions was keeping current state separate from past experience.

The structured backend stores facts that need to be deterministic:

Customer
Product
Inventory
Mission
Cart
Order
Store state

Hindsight stores experiences that can become useful later.

That gives the system two different questions:

Structured database:
"What is true right now?"

Hindsight:
"What happened before that might matter now?"

I integrated Hindsight through retain(), recall(), and reflect().

Hindsight GitHub

Hindsight Documentation

Vectorize Agent Memory

This distinction prevented the memory layer from becoming a second database.

Giving Customers Their Own Memory

The Customer Agent needs to remember things that matter to a specific shopper.

For example, a customer might say:

"Naku brown bread ante chala istam,
white bread vaddu."

Later, they might ask in English:

"Which bread should I buy?"

The useful behavior isn't simply remembering the previous sentence.

The useful behavior is connecting the previous preference to the new request.

That is where Hindsight becomes part of the reasoning loop:

Customer interaction
↓
retain()
↓
Future interaction
↓
recall()
↓
Personalized reasoning
↓
Relevant response

I also separated customer memory by customer identity:

grocerai-customer-USER00001
grocerai-customer-USER00002
grocerai-customer-USER00003

This matters because a memory system that mixes customers would be worse than having no memory at all.

I explicitly tested customer isolation so that one customer's preferences could not be recalled from another customer's memory bank.

The Customer Agent Is More Than a Chatbot

The Customer Agent uses an LLM for reasoning, but it doesn't directly invent store state.

It can call backend tools such as:

text
searchProducts()
getProductDetails()
checkAvailability()
getShelfLocation()
getStoreMapRoute()
getCustomerMission()
updateMission()
getCart()
addToCart()
removeFromCart()
getRecommendations()
checkSubstitution()
sendNotification()

For example, a request such as:

"Do you have brown bread?"

can become:

text
Customer
↓
Customer Agent
↓
searchProducts()
↓
checkAvailability()
↓
getShelfLocation()
↓
Response

This separation is important.

The model reasons about what it needs.

The backend supplies the actual product, inventory, cart, and location information.

The Customer Agent also supports multilingual interaction, including English, Telugu, Hindi, and mixed-language conversations.

That becomes particularly useful when memory survives language changes.

A preference expressed in Telugu can still influence a later English interaction because the system is retrieving the underlying experience rather than relying only on literal conversation history.

The Store Agent Remembers Something Completely Different

Customer memory answers:

"What matters to this shopper?"

Store memory answers:

"What has happened in this store before?"

The Store Agent watches operational signals such as:

product searches

product views

cart additions

checkout activity

successful purchases

stock availability

unmet demand

stockouts

checkout queues

restocking outcomes

One important design decision was to distinguish interest from actual purchase.

For example:

100 searches
↓
60 product views
↓
30 cart additions
↓
20 checkout attempts
↓
15 successful purchases

The store should not treat all 100 searches as 100 sales.

GrocerAI therefore separates different stages of demand, including search demand, shopping intent, checkout intent, confirmed demand, and unfulfilled demand.

That gives the Store Agent better information to reason about inventory decisions.

When the Store Actually Learns

The most interesting test for the Store Agent was a restocking scenario.

Suppose the store previously restocked 30 units of a product before a busy period.

The stock was depleted within roughly 2.5 hours.

That outcome becomes an experience.

Later, when similar demand signals appear, the Store Agent can recall the previous outcome rather than treating the situation as completely new.

The learning loop becomes:

Previous demand
↓
Restock 30 units
↓
Stock depleted quickly
↓
retain(outcome)
↓
Future demand pattern
↓
recall(previous outcome)
↓
Adapt recommendation
↓
Recommend ≥50 units
↓
Manager approval
↓
Observe outcome
↓
retain(new outcome)

The important part is not the number 50 by itself.

The important part is that the previous outcome changes the next recommendation.

That is the behavior I wanted from a self-adaptive system.

Two Memory Scopes, One Store

The two agents therefore use Hindsight at different scopes.

                   GROCERAI
                        |
         +--------------+--------------+
         |                             |
  CUSTOMER AGENT                 STORE AGENT
         |                             |
  Customer Memory                Store Memory
         |                             |
customer-{id}                  grocerai-store-main

The Customer Agent learns about individuals.

The Store Agent learns about operations.

The store can aggregate experiences across customers for operational decisions without overwriting individual customer memory.

This separation also makes the architecture easier to reason about: personal memory stays personal, operational memory stays operational.

What Changed After Adding Memory?

Without persistent memory, both agents behave mostly from the current state.

The Customer Agent sees:

Current conversation
+
Current cart
+
Current mission
+
Current inventory

The Store Agent sees:

Current inventory
+
Current demand
+
Current transactions

After adding Hindsight, both agents gain another dimension:

Current state
+
Relevant past experience

That changes the decision process.

For the customer:

"I need milk."
↓
Recall previous preference
↓
Personalized recommendation

For the store:

"Demand is increasing."
↓
Recall previous stockout outcome
↓
Adapt restocking recommendation

The system is no longer only reacting to the present.

It can use what happened before.

Building the Memory Loop

The most useful mental model I ended up with was:

          ┌───────────────┐
          │    OBSERVE    │
          └───────┬───────┘
                  ↓
          ┌───────────────┐
          │    RECALL     │
          └───────┬───────┘
                  ↓
          ┌───────────────┐
          │    REASON     │
          └───────┬───────┘
                  ↓
          ┌───────────────┐
          │     ACT       │
          └───────┬───────┘
                  ↓
          ┌───────────────┐
          │ RE-OBSERVE    │
          └───────┬───────┘
                  ↓
          ┌───────────────┐
          │   REMEMBER    │
          └───────┬───────┘
                  │
                  └──────→ next interaction

This is the part of the architecture I found most important.

Memory isn't just something that sits beside an agent.

It becomes part of the agent's decision cycle.

What I Learned
**

Memory should change behavior**

A memory dashboard full of stored information isn't enough.

The real test is:

Did recalling something change what the agent did next?

For GrocerAI, that meant testing both personalized customer decisions and adaptive store decisions.

2. One memory store isn't enough

Customer experiences and store experiences have different scopes.

Keeping them separate made the system safer and easier to reason about.

3. Structured data and semantic memory solve different problems

I wouldn't want Hindsight to replace inventory or order storage.

The database is responsible for current facts.

Memory is responsible for experiences that can influence future reasoning.

4. Learning requires an outcome

The Store Agent doesn't become adaptive simply because it can recommend a restock.

It becomes adaptive when it can remember the outcome of that decision and use it later.

*5. Graceful degradation matters
*
Memory introduces another service dependency.

During local development, Hindsight can be connected directly. In production, a reachable Hindsight endpoint is required for live memory operations.

If memory isn't available, the application should clearly degrade rather than pretending that a recall happened.

The Bigger Idea

The most interesting part of GrocerAI isn't that it can search for products.

It isn't that it has voice interaction.

It isn't even that it has two agents.

It's that the system can connect what is happening now with what happened before.

A customer can become more understandable over time.

The store can become more informed by its own operational history.

And the two forms of learning can coexist without mixing their memory scopes.

That is what I wanted when I started building GrocerAI:

[not a grocery chatbot, but a grocery store that remembers, learns, and adapts.]

GrocerAI main interface — a unified grocery experience connecting conversational customer assistance, personalized shopping, store navigation, and adaptive store intelligence.

GrocerAI system architecture — connecting the shared store display, Customer Agent, Store Agent, structured operational state, and Hindsight persistent memory.

Conversational Customer Agent — handling natural-language shopping requests, product discovery, aisle navigation, recommendations, and follow-up interactions.

Persistent memory view — showing how customer and store experiences are retained as reusable knowledge rather than disappearing after a session.

Closed-loop adaptation — the Store Agent records an action, observes the resulting store outcome, and uses that experience to improve future decisions.

Personalized mobile companion — synchronizing the shopper's mission, cart, Customer Agent assistance, and in-store shopping context with the shared store experience.

Store collective memory — surfacing recurring stockout, demand, rush-hour, and operational patterns learned from previous store experiences.

Adaptive restocking recommendation — Hindsight connects a previous stockout outcome with a new replenishment decision, increasing the recommended quantity from 30 to 50 units.

Demand funnel — separating searches, product views, cart intent, checkout attempts, confirmed purchases, and unfulfilled demand so the Store Agent can distinguish interest from actual sales.

Manager-in-the-loop execution — allowing a store manager to review and modify an AI-generated replenishment recommendation before executing the action.

DEV Community: Ishwarya Kota

I Gave a Grocery Store a Memory. Here’s What Changed.