See all services → Shopify Plus Partner
Admin Global

Add Submission Times to Shopify Request Received Emails

Shopify added two Liquid variables, return.requested_at and requested_edit.requested_at, to the Request received notification. The timestamp reflects when the customer submitted, not when the email was sent, so resends stay accurate. You have to edit the template to use it.

Executive summary

What changed

The Request received notification fires when a customer submits a return request or an order cancellation request through a self-serve flow. Until now the template had no dependable way to state when that request was made. Shopify has added two variables for exactly that: return.requested_at for return requests and requested_edit.requested_at for cancellation requests. Both resolve to a timestamp fixed at submission. The default template was not modified, so nothing appears in customer email until someone edits the template and renders the variable. Formatting runs through the standard Liquid date filter, which leaves display format and time zone presentation entirely under your control.

Why it matters

Post-purchase communication is where enterprise support cost concentrates. A return acknowledgement that says only that the request was received invites a follow-up ticket the moment the customer loses track of the date, and the problem compounds when an agent resends that email a week later and the customer reads the resend date as the submission date. A stable submission timestamp removes the ambiguity inside the one message every requester already gets.

It also gives your returns policy a visible anchor. If your window is 14 days from request, the acknowledgement itself now evidences that the clock started on time, which matters when a dispute turns on a single day. Merchants running self-serve returns across several markets gain a second benefit: a consistent timestamp makes it easier to reconcile customer expectations against market-specific rules. If your requests originate in new customer accounts, our guide to new customer accounts versus classic covers how those self-serve flows reach the customer in the first place.

Role-specific impact

Use-case example

Real-world scenario

A home goods brand on Shopify Plus processes roughly 4,000 self-serve return requests a month against a 14 day request window. Support logs showed that about 6 percent of those requests generated a follow-up contact asking whether the request had landed and when. The team rendered return.requested_at in the acknowledgement with an explicit date, time and time zone, then re-ran the same report the following month. The contact rate on acknowledged returns fell to roughly 3.5 percent, which is close to 100 tickets a month that no longer reach an agent. The quieter win was dispute handling: agents could resend the acknowledgement mid-case without generating a new and misleading date.

Implementation checklist

  1. Open Settings, Notifications, Customer notifications, Request received, then click Edit code.
  2. Identify the branches of the template that handle return requests and cancellation requests separately.
  3. Render return.requested_at in the return branch and requested_edit.requested_at in the cancellation branch.
  4. Apply the Liquid date filter and include a time zone token so the value is unambiguous, for example date: "%B %-d, %Y %H:%M %Z".
  5. Review your translated template versions if you sell in multiple languages, because the format string itself is not translated for you.
  6. Send a test notification, then submit a real request in a staging context and resend the email to confirm the timestamp does not move.
  7. Tell your support team the date is now in the email so agents can point customers at it rather than looking it up.

FAQ

Q: Does the timestamp change if we resend the notification?

A: No. The value is the moment the customer submitted the request, not the send time of the message. That is precisely what makes it safe to cite during a dispute.

Q: Will our existing templates pick this up automatically?

A: No. The default template was left unchanged. The variables are available to you, but nothing renders until you add them to your own template code.

Resources

Shopify Help Center: Customizing email notification templates

Need guidance? Talk to Makro.