Self-service is not the absence of service.
It is service expressed through infrastructure.
That is what makes Amazon’s Dash Cart interesting. The cart is not just a cart. It is identity, payment, item recognition, receipt visibility, exception handling, and trust design wrapped around a grocery basket.
Traditional self-checkout often makes the customer become the cashier. That is why it feels bad. The company removes the human but leaves the customer to operate the workflow. The labor of scanning, bagging, and paying is transferred to the person who just came to buy groceries.
Better self-service does something different. It moves the system closer to the customer’s intent.
The intent gap
In grocery shopping, the customer’s intent is not “use a checkout terminal.” It is “get my groceries and leave.”
The Dash Cart closes the gap between these two things. The transaction disappears into the journey. You grab items, they register. You walk out, you are charged. The system works around your intent, not the other way around.
The adoption question
But the adoption question matters. A human cashier is also infrastructure: scanning, bagging, judgment, exception handling, reassurance, and recovery. A cashier catches the expired coupon, the bruised apple, the customer who looks confused. They provide a social safety net for the transaction.
If self-service removes that layer, the system has to replace the trust and support it provided. That is where most implementations fail. They take away the human but do not build the system-wide capability to absorb the exceptions.
Bad self-service transfers labor to the customer.
Good self-service transfers capability.
Infrastructure as service
The same principle applies far beyond retail.
Customer experience is infrastructure, whether the surface is a help center, an AI answer, a support case, or a shopping cart. Every touchpoint is a system for either absorbing or redirecting the customer’s effort.
A knowledge base that answers the question before it is asked is infrastructure. A chatbot that escalates to the right person without making the customer repeat themselves is infrastructure. A checkout process that does not require a terminal is infrastructure.
The question to ask of any self-service surface is not “did we remove a human?” It is “did we move the system closer to the customer’s intent?”
If the answer is no, you have not built self-service. You have built unpaid labor.