Hey Shopifolk!
A thought come up as I am working on copying things from a Production store to a Staging (dev) store.
It would be great if we could have the ability for the notification email templates to utilize Shop metafields (at least).
In this particular instance, we have separate images meant for certain bundle products and we need to use the absolute URL of the image there, which is fine but because we cannot use a Shop metafield for the URL we need to adjust it for each affected template between the stores manually rather than just copying-and-pasting-and-saving the template itself.
(To be clear, I am fine with doing that, but for me it’s more of a reusability/reducing room for user error sort of feature request. Also, yes I could duplicate the templates and do a find-and-replace-all for them, then copy them over, but this is more for reusability without needing to do something like that — especially when thinking about using even more similar customizations among the majority of notification templates.)
Thanks in advance! (Personally hoping this sort of feature could make its way in before the Winter Editions 2026.)
(P.S. when originally modifying the default templates a few months ago, I noticed several things that did not seem to be part of the documentation within the help center. I also guessed as to some undocumented functionality that could help with replacing the images like I did and it worked. It would also be nice if the documentation could be revised to include those sorts of details too rather than having us guess & check and hope it continues to work…)
1 Like
Hey Rob, interesting idea that makes swapping between prod and staging easier. I assume you want to do something like Metafield shop value = <some constant in the domain/path> and then allow you to prefix a URL with that value across Shops.
I may need a bit more context to fully understand what you have in mind for practical implementation. Can you provide some sample code or some examples of the workflow that you had in mind that will help me understand your proposed solution?
Hey James,
Upfront, it is meant more for having the same Shop metafields on both shops but being able to use the values of them within the notification email templates directly. Something like shop.metafields.custom.white_glove_bundle_image (or as _image_url instead if the object itself would not be usable there) within the code of the notification template.
In my case, I needed to loop through the components of a bundle and check for the tags of the product to contain a certain tag (which I believe was undocumented functionality) such as “White Glove” to denote that the type of bundle is a “White Glove” bundle and therefore use the associated image instead of whatever image may have been default.
Currently I needed to hard-code in the image URLs, tags, and bundle types. When added separately to 20 different templates it means that if any needed to be changed it would need to happen across all 20 templates, something where dynamic values you only update once via a Shop metafield would be beneficial (especially being able to use list metafields enabling nice looping within the template).
Totally dig the feature, who doesn’t love more metafield/metaobject support hehe
On another note, in the meantime, you could leverage the theme locales to store the CDN media URLs, that would still be hardcoding but with Github integratio, at least it would be shared between stores. Just food for thought !