# A concierge chatbot that checks orders and fills carts: why sign-in comes first

> A store asked whether a concierge chatbot could check orders and add to cart. Why we start with proper sign-in, and what Gydr 4.2 does for shoppers.

Source: https://news.gydr.ai/concierge-chatbot-orders-and-cart
Published: 2026-11-08

"Can Gydr help my users check their orders and add items to their cart?" The question came from a store owner who already knew what they wanted. Not a chatbot that recites the returns policy, but a concierge chatbot: the online version of the person behind the counter who finds your parcel, remembers what you were looking at, and slips the right size into your basket while you are still deciding.

We said yes. Then we went away and worked out what that yes would have to mean, because the honest answer turned out to be less about orders and carts than about something underneath them: knowing, beyond doubt, who is asking.

## The question behind the question

Most of what a store's chatbot does is public. "Do you have this in blue?" has the same answer for everyone who asks it. The moment a shopper says "my", everything changes. "Where is my order?" is about one person's private record. "Put two of those in my cart" changes something that belongs to them and to nobody else.

Think of a hotel concierge. They can pull up your booking in a moment, but only because you checked in at the front desk first. They never take your word for which room is yours. A chat window has no front desk. Anyone can type anything into it, and "I'm the customer who placed order 1042" costs exactly as much to type as "hello".

So the store owner's real question was not whether a chatbot can look up an order. Looking up an order is the easy part. The real question was whether a chatbot can be certain, every single time, whose order it is looking at, and whether it has been allowed to touch it.

## Three easy answers, and why we turned them down

There are quick ways to build this. We looked at each of them and walked away.

1.  **Ask for an order number and an email address.** It feels secure, but both are easy to guess, share or find in a forwarded receipt. The likely outcome is a stranger reading someone else's delivery details.
2.  **Give the chatbot a master key to the store.** Then the chatbot can see every order the store has ever taken, and the only thing standing between one shopper and another's data is a cleverly worded message.
3.  **Check identity inside the chat with a one-time code.** A chatbot that asks people to type codes into a chat box teaches them a habit that scammers are very glad to see.

Each of these makes a demo look good and leaves the business holding the risk. We did not want to ship any of them.

## What we believe: borrow permission, never assume it

Our answer is a principle before it is a feature. A chatbot should never be able to do more than the person it is talking to, and it should get even that the proper way: borrowed from a sign-in the shopper has already completed, and checked against whoever issued it.

None of this is new to the internet. It is how you let a calendar app read your inbox without telling it your password. You sign in with your email provider, approve exactly what the app may do, and the app receives a narrow permission that you can take back at any time. That arrangement, known as OAuth, is why an AI assistant can work inside your tools without holding the keys to your house. We built Gydr's own connections for AI assistants on it, and we think every chatbot that acts for people should live by the same idea.

It matters more with every new skill. A chatbot that only answers questions can embarrass a business. A chatbot that can act can hurt a customer. Every new thing a concierge can do for a shopper is also a new thing it must refuse to do for anyone else.

## Starting from a sign-in the store already trusts

In most cases the shopper has already proved who they are: they logged in to the store. So we do not ask them again. The business's website tells the chat who is signed in, and Gydr checks that against the system that issued the sign-in, in whichever of three ways the business picks.

![The Add sign-in source panel in the Gydr Console, offering WordPress or WooCommerce, Your keys for an identity provider such as Supabase, and Your backend, with Shopify marked as coming soon.](/images/sign-in-methods.webp)

Three ways for Gydr to check who a visitor is.

A WordPress or WooCommerce store installs the Gydr plugin and is done, with no code to write. A business that already uses a sign-in provider such as Auth0, Clerk, Firebase or, as of this release, Supabase, lets Gydr check the provider's own signature. Anyone else can have Gydr ask their own server, politely and in a way that cannot be forged, who a visitor is.

What the chat itself never does is ask a shopper to prove who they are. There are no codes and no magic links typed into the conversation. Identity comes only from the sign-in the store already trusts, never from what someone types.

## Orders: their own, or a polite "please sign in"

On a WooCommerce store, a signed-in shopper who asks "where is my order?" gets their own recent orders, with the status, the items and how the delivery is going, read through the sign-in their store issued. A guest who asks the same question gets one plain sentence asking them to sign in first. Nothing is looked up, and nobody is asked for an order number.

![The order settings preview in the Gydr Console, showing a signed-in shopper told their order shipped yesterday, and a guest asked to sign in first.](/images/order-answers-signed-in-vs-guest.webp)

The same question, asked by a signed-in shopper and by a guest.

A few rules sit underneath. Order answers never include the address, phone number or email on the order. Gydr holds no key of its own to the store's orders; it can only see what the shopper's own sign-in lets it see. And order answers stay switched off until the business decides to turn them on. On a Shopify storefront that signs shoppers in to their customer account and passes that sign-in to the chat, the chatbot can list the shopper's own past orders in the same way.

## The cart: helping hands, never the till

New in Gydr 4.2, a WooCommerce store's chatbot can now look after the shopper's cart. It can show what is in it, add something the shopper has chosen, change a quantity or take an item out, whether the shopper is signed in or still browsing as a guest.

![The Cart settings in the Gydr Console, where a store turns on Manage the shopper's cart; the assistant never places an order and the shopper checks out on the store's own checkout page.](/images/woocommerce-cart-setting.webp)

The cart stays off until the store turns it on.

Guests can use it because a cart belongs to a browser, not to an account. When the chat opens on the store's website, the Gydr WordPress plugin hands it a pass to that browser's own cart, and to nothing else. The pass lives only in the open page, travels with one message at a time, goes only to that store, and is never kept.

What the chatbot never does is take payment. It does not place orders. When the shopper is ready, the Checkout button opens the store's own checkout page, where paying works exactly as it always has. The cart also only works on the store's own website, and like order answers it stays off until the business switches it on.

## A chat window with room for a customer

Permission was only half of the problem. The other half was the chat window itself.

A widget built to answer questions shows paragraphs, and an order does not fit in a paragraph. A shopper wants to see at a glance where their parcel is, follow the tracking link, change a quantity without retyping a sentence, and find the way to checkout. So, alongside the work on sign-in, we redesigned how the widget draws a reply, to make room for everything a signed-in shopper might now ask for.

An order now arrives as a card that shows its progress and tracking, with a View order link back to the store. A cart arrives as a card listing each item, its quantity and the total, with a Checkout button. Products the chatbot recommends come with their own detail sheets and can be compared side by side. Every one of these cards is drawn from what the store's own records say, never from the chatbot's wording, so a card cannot misstate a status, a quantity or a price.

![The chat bubble answering "Where is my order?" from a guest with a short notice asking them to sign in on the website and ask again.](/images/bubble-sign-in-notice.webp)

When a guest asks for something private, the chat says so plainly.

When a guest asks for something only a signed-in shopper may see, the widget now shows a short notice instead of a long apology. If the store's website tells the widget how to open its own sign-in page, the notice carries a Sign in button. Once the shopper signs in, the chat starts afresh as them and they simply ask again. The button only ever appears on the store's own website.

Everything new follows the business's own theme, dark mode included. On WhatsApp, Messenger, Instagram and Telegram, the same replies become that app's own buttons or plain text.

## Holding ourselves to the same rule

We are asking businesses to trust a chatbot that acts for their customers, so we hold ourselves to the same standard when an AI acts for them. When a business connects Claude, Codex or another assistant to its Gydr Console, the assistant signs in the OAuth way. It never sees the person's password and never borrows their Console session. It receives a permission that works only for Gydr, only for the accounts the person ticked, and that ends the moment they disconnect it. As of this release, the connect page also warns people when an app has not been verified.

## What it does not do, yet

A signed-in shopper can now ask a WooCommerce store's chatbot where their order is and get the true answer, and any shopper can ask it to put the size they chose into their cart. That is the concierge the store owner asked for, built on the shopper's own permission rather than on whatever they happen to type.

There are limits, and we would rather name them than let them surprise anyone. The cart works on the store's own website only, not in WhatsApp, Messenger, Instagram or Telegram, and not yet on Shopify. Order answers do not appear in messaging apps either, because a messaging app never knows who is signed in to a website. The chatbot cannot edit, cancel or refund an order, and it never takes a payment.

Knowing the person also opens the door to better help: remembering what a returning shopper asked about last time, or suggesting something with their earlier questions in mind. We will keep building in that direction, and only on this foundation, where knowing the person is safe.

## Frequently asked questions

### Can a chatbot check a customer's order status?

Yes, for a shopper who is signed in. On a WooCommerce store the chatbot reads the shopper's own orders through the sign-in their store issued, and a guest is asked to sign in first.

### Can the chatbot add items to a shopper's cart?

On a WooCommerce store, yes, from Gydr 4.2. It can show, add, change and remove items in the shopper's own cart while they chat on the store's website, once the store turns the cart on.

### Does the chatbot ever place an order or take payment?

No. The cart's Checkout button opens the store's own checkout page, and the chatbot cannot edit, cancel or refund an order.

### Why doesn't the chatbot just ask for an order number and email?

Because both are easy to guess or share. Order answers come only from a sign-in the store already trusts, so nobody can read another shopper's order by typing the right details.

The full list of changes is in the [4.2.0 release notes](https://www.gydr.ai/releases#release-4.2.0).

## On gydr.ai

- [A WooCommerce chatbot for orders and the shopper's cart](https://www.gydr.ai/integrations/woocommerce)
- [The WordPress plugin that signs shoppers in to the chat](https://www.gydr.ai/integrations/wordpress)
- [Console MCP](https://www.gydr.ai/features/console-mcp)