Fileflare sends three different email templates — fulfillment, file update, and pre-order release. The fulfillment email is easy to test (place any test order). The other two are harder because they only fire on specific actions. Here’s the workflow to preview them safely.
Available on all paid plans (file update on Basic+, pre-order release on Premium). The trick is creating a dummy product so test triggers don’t accidentally email your real customers.
When you’d use this
- You’re customizing the file-update or pre-order email template and want to preview the rendered output.
- You changed the email language, signature, or button styling and want to verify before going live.
- You set up SMTP and want to confirm the non-fulfillment email types deliver correctly.
Test the file-update email
The file-update email fires when you replace an asset and choose to notify past buyers. To test without spamming real customers:
- In Shopify, create a test product (e.g., “Email Test Product”). Doesn’t need to be live on the storefront.
- In Fileflare, upload a test file and attach it only to that test product. Don’t reuse a file already attached to real products.
- Place a test order for the test product, using your own email address.
- In Fileflare, go to the asset and click Replace asset. Upload any file (a different test file).
- On step 4 of the replace flow, choose Yes, notify past buyers.
- You’ll receive the file-update email at the address used on the test order.
Test the pre-order release email
The release email fires when an asset’s release date is reached. Same setup pattern:
- Create a test product in Shopify.
- In Fileflare, upload a file and attach it only to that test product.
- Set a release date on the asset for ~5 minutes from now.
- Place a test order for the product, using your own email address.
- Wait. When the release date passes, the email fires.
Common issues
- Email never arrived — check the order is in Paid status; the test asset is attached to the test product (not a real one); and the asset wasn’t already updated/released before the order. See email troubleshooting if it’s a delivery issue.
- I accidentally sent to real customers — make sure the asset is only attached to a test-only product. If a release email or update email goes to real buyers, there’s no recall.
- The email looks broken in Outlook / Gmail — different clients render HTML differently. Test in your top 2-3 customer email clients, not just one. Tools like Mail Tester show how a message renders across clients.