OpenClaw Grocery Order Mistake: Unit Confusion with MCP Server

An OpenClaw user shared a cautionary tale about letting an AI agent manage grocery shopping using an MCP server. For three months, the setup worked perfectly: every Sunday, the agent placed a normal basket at a normal price, picking items the user actually eats. But yesterday, the user discovered that OpenClaw had ordered 2 kg of garlic instead of the intended 2 heads. The kilogram unit was the default on that product page, and the agent didn't notice the discrepancy. Neither did the user, because over the previous months the agent had never made a mistake.

What Happened

• The user gave OpenClaw their credit card details several months ago to automate weekly grocery runs through an MCP server.
• For about three months, the agent consistently placed correct orders: Sunday baskets with normal items and prices that matched the user's preferences.
• Yesterday's order deviated: the agent selected 2 kg of garlic instead of 2 heads. The product page defaulted the unit to kilograms, and the agent failed to catch that. The user also missed the error because they had become complacent after months of reliable behavior.
• The user now has an excess of garlic and shared the story on r/openclaw, asking if others have had similar experiences with AI grocery shopping agents.

Takeaway

This incident highlights a classic failure mode for autonomous agents: unexpected default values in external systems (e.g., e-commerce product pages). The agent's logic assumed the unit would be correct based on previous orders, but the product's unit default changed. Developers building shopping agents should consider adding explicit unit validation against expected quantities or price checks to catch such anomalies.