Feedback Loop in ecommerce
Next principle →A tap with no visible response leaves shoppers wondering if it worked.
Shoppers tap Add to Bag and look for a sign. If the button stays the same, they may tap again, open the bag to check or give up.
A feedback loop, also called system feedback, is the back and forth between a shopper and your store: they do something, the store shows what happened, and that tells them what to do next.
Go through your store and tap every button as a shopper would. Each one should answer right away with a change the shopper can see. Start with Add to Bag, filters and form errors, where silence is most confusing.
Feedback loop example: a button that says Added to Bag on a $120 jacket
Someone on a phone taps Add to Bag on a $120 wool jacket. The button looks exactly as it did before, so they wonder, “Did it work?” At this made-up store, 3 of 10 shoppers buy the jacket, which makes $360. The owner changes one thing: after the tap, the button turns teal and reads Added to Bag with a check mark. Now 8 of 10 buy, which makes $960. Every tap deserves an answer the shopper can see.
How the feedback loop works with other principles: 4 store examples
A tap and its answer sit next to several other ideas. Two of these pairs often get confused with feedback and two show what good feedback makes possible. Every store below is made up to show the idea.
Feedback loop vs feedforward
Often confused with: Feedforward tells shoppers what will happen before they tap, and feedback confirms what happened after, so each one answers a different moment.
Illustrative store example: A meal kit store's button reads Skip this week, no charge, and that is feedforward. The line that appears after the tap, Week skipped, is feedback, and a store that drops either one leaves the shopper guessing at that moment.
Feedforward: how to tell shoppers what a button will do →Feedback loop vs signifiers
Often confused with: A signifier invites the tap by showing where to press, and feedback answers the tap by showing what happened.
Illustrative store example: A toy store's quantity box has clear plus and minus buttons, so shoppers know where to tap. When the number stays at 1 after a tap, the signifier did its job and the feedback is missing, so change the number the moment they press.
Signifiers: why some buttons get missed →Feedback loop and chronoception
Works with: Chronoception is how long time feels, and feedback during a wait can make the same seconds feel shorter than a still, silent screen.
Illustrative store example: A photo print store makes shoppers wait while a large picture uploads, and on a still screen those seconds feel long and the page looks broken. A progress bar showing how much is done can make the wait feel shorter, even though the upload takes the same time.
Chronoception: why some waits feel longer than others →Feedback loop and flow state
Works with: Flow state is being so absorbed in a task that it feels easy, and quick feedback helps keep it going because shoppers don't have to stop and check.
Illustrative store example: A grocery store shopper adds 20 items to a weekly order, one after another. If each tap updates the button and the cart count right away they keep moving, and if it doesn't they stop to open the cart and check.
Flow state: how a smooth path keeps shoppers moving →Put it into practice
How fast should a button respond to a tap?
Right away, even if the work behind it takes longer. Change the button the moment the tap lands, show Adding... while the bag updates, then show Added to Bag when it's done. If something takes more than a second or two, show progress so nobody thinks the store froze. Only say Added once it's true, and if it fails, say so plainly.
How should checkout forms give feedback?
Put the message next to the field, as soon as the shopper leaves it, and say how to fix the problem: “Zip code needs 5 digits.” Wait until they finish typing, since an error that appears mid-word feels like nagging. A list of errors only at the top, after they press Pay, makes them hunt for each one. Keep what they typed when the page reloads.
How much feedback is too much?
Too much is anything that stops a shopper who wanted to carry on. A full-screen popup after every add to cart does that, and so do sounds, confetti and long messages. Match the response to the size of the action: a small check mark for a small action, a clear confirmation page for a paid order. If people have to dismiss your feedback, it has become an obstacle.
Is this the same as collecting customer feedback?
The name gets used for both. Marketers often say feedback loop for asking customers what they think, acting on it and telling them what changed, which can take weeks. This page is about the quick version that takes a moment: shopper taps, store answers. Both fit the broad meaning of the term: the result of one action shapes the next one.
How do I find the places where my store stays silent?
Put your phone on a slow connection and tap every main button. Anything that looks unchanged for a moment is a gap. Next, watch a few session recordings, which are videos of real visits, for repeat taps on one button and for shoppers opening the bag to check. After a fix, you should see less of both, and fewer duplicate items in carts.