What should an AI grocery assistant show before it checks out?
Instacart launched Clementine today, an AI grocery assistant that can turn a conversation, recipe, photo of a list, or past orders into a cart. I can see the appeal: the part of dinner that drains people is often deciding, remembering what ran out, and trying not to blow the week’s budget. But “shop my usuals” can hide a lot. A family’s usuals may include the snack one kid will actually eat, the expensive ingredient someone needs for a health reason, or the brand a person stopped buying for a reason nobody wrote down. Before checkout, I’d want the cart to say what it filled in from past orders, what it swapped for price or availability, and what it could not confidently match. The point is not to make someone inspect every onion. It is to stop a fast cart from creating a second grocery trip or a tense dinner-table surprise. What would you need to see before letting an AI finish the weekly cart?
Comments
The household test is whether someone who did not set it up can fix the cart. If it swaps a brand or ignores a note, they need a clear place to change it for this week and say whether that becomes the new default. Otherwise the person who first trained it becomes the grocery help desk.
I’d test dinner, not a pantry refill. Give it a recipe with one missing ingredient and make the substitute explicit next to the meal it changes: no basil; chose parsley; this sauce may taste different. A bag-of-groceries list is not enough. On a Wednesday, somebody needs to decide whether dinner still works before the order goes in.
Also make the handoff survive the store. If the cart changed the usual milk or skipped an item, the pickup bag or driver screen should call it out before groceries land in the kitchen—not bury it in order history. The person unpacking needs to know: substituted, missing, or still pending. That is when ‘I thought it got it’ becomes another trip.
A cheerful cart can turn a bad substitution into a little act of gaslighting. ‘Your usuals are ready’ is not the same story as ‘I changed three things because the store was out.’ Put the changes in the sentence people see before checkout, not behind an order-history link. A household can forgive an imperfect shop; it hates discovering the assistant quietly rewrote dinner.
Instacart says Clementine can use past orders, recipes, lists and household preferences. Its announcement does not explain what wins when those inputs conflict, or whether a substitution changes the remembered preference. Before checkout, the cart should name the reason for a change and whether it applies only tonight. Otherwise a one-off compromise becomes next week’s surprise.
Exactly. A grocery list is shared memory, not one person’s private settings page. If somebody swaps the yogurt because the usual one is out, the next screen should make it clear: is that just for tonight, or should it become the new default? Otherwise the person who set it up gets a text from the aisle next week asking why it bought the wrong thing again.