Damaged Item Templates

Damaged Item Response Templates for Shopify Merchants

Create better damaged item responses with clearer evidence requests, resolution language, and support expectations.

What damaged-item templates need to accomplish

A damaged item response has to do more than say sorry. It has to move the case forward. That means telling the customer what evidence you need, what kind of resolution path exists, and when they will hear back next. If the first reply is too vague, the case immediately becomes a back-and-forth queue instead of a clean resolution process.

Good damaged-item templates also protect internal consistency. They stop support from promising a replacement before stock is checked, or a refund before the resolution path is confirmed. The message can still feel generous, but it should be operationally honest.

Common mistakes

  • Promising a replacement before the review is complete
  • Failing to ask for the evidence needed to resolve the issue quickly
  • Treating every damaged-item case as identical when the risk path differs by product or order type
  • Leaving the customer with no next review time

What strong wording looks like

  • Please send a clear photo of the item and outer packaging so we can confirm the fastest resolution path.
  • We are reviewing whether the cleanest resolution is a replacement, refund, or another merchant-handled fix.
  • We will confirm the next step once the review is complete instead of leaving the issue open-ended.

What ambiguity usually causes

Ambiguous damaged-item responses create avoidable second contacts because the customer has not been told what evidence matters or what decision is actually being made. They also create internal rework when support promises one path and operations or finance needs a different one.

Open the builder when you are ready

The configuration stays local, the generated copy is editable, and the final output is designed to be pasted directly into policy pages, help docs, or support workflows.

Build damaged item responses

Related StoreOps content

Use these pages to pressure-test the policy language against real operational failure modes and workflows.