1. Industries
  2. Retail and consumer

Retail and consumer

Your competitor's AI knows what the customer wants before your batch job runs.

Customers in India pay by UPI in seconds and expect delivery within the day, while inventory still updates in batches. We rebuild the data layer on Google Cloud so retail AI can act on live signals, inside controls you can show.

Updated October 19, 2026

Illustrative exampleOne inventory event.
  • Last unit sold onlineOrder recorded
  • Stock event publishedWeb and store updated together
  • Supplier signalMatched to the open purchase order
  • Replenishment draftHeld for buyer approval

Retail AI is only as good as the minute its data was last true.

Where you are

The assortment, the stores and the site are working. Somewhere a team is trialing personalization, availability promises or a service assistant, and each one is waiting on data that arrives late. For consumer brands selling direct, the same delay sits between the storefront, the marketplaces and the warehouse.

Inventory blind spots

Quick commerce has reset what customers expect.

A shopper who gets groceries within the hour expects every retailer's stock count to be true. A number that updates overnight sells what is gone and hides what is there.

What waiting costs: margin lost on both sides of the same number.

Consent

Personalization now runs on permission.

The DPDP Act makes consent and purpose binding for loyalty and marketing data, and the RBI's card-on-file rules mean merchants may no longer store card details. A personalization model built on old data habits fails both.

What waiting costs: a program rebuilt after the consent review, and a season of offers you cannot send.

Online selling

Your storefront has its own rulebook.

The Consumer Protection (E-Commerce) Rules require clear seller and price disclosures, and the Central Consumer Protection Authority's 2023 guidelines ban dark patterns such as false urgency and drip pricing. An agent that writes offers inherits both.

What waiting costs: a consumer authority notice over a pattern nobody reviewed.

Rulebook, India

Regulator or lawWhat it asksWhat it means for an agent
Consumer Protection (E-Commerce) Rules, 2020Disclosure of seller, price and return terms, a grievance officer, and no manipulation of prices.Offers an agent makes show the same price and terms as the catalog, and each one is logged.
Central Consumer Protection Authority, Guidelines for Prevention and Regulation of Dark Patterns, 2023A list of banned patterns, including false urgency, basket sneaking and drip pricing.Personalization and service agents are tested against the listed patterns before release and monitored after it.
RBI rules on card-on-file tokenizationMerchants and their partners may not store customer card data; tokens replace it.Agents never see card numbers. Payment calls go through tokenized APIs behind the gateway.
Digital Personal Data Protection Act 2023 and DPDP Rules 2025Consent and notice for personal data, purpose limits and breach notice.Recommendations and offers run only on data the customer agreed to, with the consent reference in the log.
CERT-In directions (April 2022)Cyber incidents reported within six hours; ICT logs kept for 180 days in India.Agent and API logs stay in India and feed the incident process.

What is in the way

The data exists. It arrives late, in batches, through point-to-point links nobody can trace, so every AI project starts by waiting for the nightly job. Each new agent that touches customer data or payment pages also lands inside payment card and privacy rules.

If a customer buys the last unit at 2:14 p.m., when do your site, your store and your supplier find out?

2:14 p.m., the last unit

Batch world

Site still shows one in stockStore shelf count unchangedSupplier has not been toldNightly job runs after midnight

The item keeps selling until the nightly job.

Event world

2:14 p.m.Last unit sold online
Same secondSite shows none left
Same secondStore count updated
Same secondSupplier signal sent

Site, store and supplier update in the same second.

Batch data sells things you no longer have.

How we clear it

Retailers that move their data from batch to events first can let AI act while the customer is still on the page.

  1. 01

    Events instead of batches.

    Inventory, order and supplier events on one governed stream, built as event streams on Google Cloud with Pub/Sub.

    You hold: real-time stock and order events reaching every channel together.

    Vertex AI, BigQuery and data
  2. 02

    Governed APIs between systems.

    Apigee between the store, the site, suppliers and marketplaces, replacing point-to-point links.

    You hold: one API layer with an owner and a policy for each connection.

    Apigee and APIs
  3. 03

    Agents that act on live signals.

    Models on Vertex AI and BigQuery and agents on Gemini Enterprise for replenishment, service and personalization, inside spend and action limits.

    You hold: one agent in production on live data with a decision log.

    Vertex AI, BigQuery and data

Easy to start

Start with one workflow, not a program.

You

Choose one workflow, name one owner, and give us time with the people who sign it off.

Us

We bring engineers and the gateway design, we work inside your environment under your security rules, and we write the review pack alongside the build.

A good first workflow is availability across channels for one product family. See the fixed-price ways to start.

What the work feels like

What the first month looks like from your side.

  1. The first week

    One workflow is chosen and one person owns it. The questions your reviewers will ask are written down before any build starts. Your merchandising team sees live availability in the first sprint demo.

  2. The first sprint

    Governance goes in before the first agent does: the gateway, the audit trail and the access rules. Your risk team sees them working.

  3. Every week

    A working demo you can show your own review board, not a status slide.

  4. The sign-off

    A decision log that can rebuild any action, and a go-live date that was agreed at the start.

Production readiness check

Test one workflow against the five questions.

A short readiness check on a live or planned agent workflow. You get a score and the principles worth another look.

Take the readiness check

Questions we are asked before the first conversation

Do we have to replace our commerce platform?

No. We work in the integration and data layer around it.

What stops an agent ordering stock it should not?

Spend and action limits at the gateway, and a buyer approval step for anything above them.

How do you move retail data in real time?

With event streams on Google Cloud, built on Pub/Sub, so inventory and order events reach the site, the stores and BigQuery together. If you already run another streaming platform, we connect to it instead of replacing it.

Can an agent personalize offers without breaching the dark patterns guidelines?

Yes, if the patterns are designed out before release. We test every offer flow against the patterns the 2023 guidelines list, and log what each customer was shown so it can be checked later.

Do your agents ever handle card details?

No. Under the RBI's tokenization rules card data stays with the card network and the payment partner. Agents work with tokens through the gateway and never see a card number.

Show us the number that is always wrong by the time it reaches the customer.

Talk to an architect

Tell us what you are working on. Our Customer Partnership Team will reply to arrange a conversation.

Contact us

Get answers to your questions

    Upload file

    File requirements: pdf, ppt, jpeg, jpg, png; Max size:10mb