Search blocks by description or jump to a page.
One handover question with four chips, where the answer goes, and why it never touches the driver.
The source for every Ecommerce block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Delivery Feedback Card asks one question after arrival: how was the handover, with four chips: Perfect, Left in the rain, Wrong spot, Late. Below the card two icon rows explain the consequence and the boundary. The consequence: “we move volume between our three carriers quarterly on this data, so a wet parcel in June means fewer wet parcels by October.” The boundary: “answers attach to routes and carriers, never to a name. Routes get fixed and depots hear patterns, people do not get punished off the back of one bad afternoon.”
Chips live in one array, destinations in a second. The ethics boundary row is what makes the feedback ask trustworthy, most delivery surveys omit it entirely.
Place this block in the post purchase email or confirmation page, triggered after the carrier scan that marks delivery. The quarterly volume rebalancing detail must describe a real routing practice or the consequence row is fiction.
A natural flow around it on an Ecommerce Pro page:
Before
After
One strong use is the four chip handover question. Other delivery feedback variants:
Tip: stating where the data never goes earns more honest responses than any privacy policy; the boundary sentence should stay even if the rest of the card changes.