Fileflare lets you bulk-send download emails to customers who already purchased — typically when you’ve updated a file, set a release date, or want to point customers to their customer accounts. There are three methods, each suited to a different scenario.
Specific methods require specific plan tiers — file replacement on Basic+, release dates on Premium, and the customer-account method on Basic and above. Make sure past orders are imported before sending — see Method prerequisites below.
When you’d use this
- You updated a file (typo fix, new chapter, software patch) and want to notify all past buyers.
- You’re releasing a new file (next month’s content, the next chapter) to existing subscribers.
- You’re announcing customer-account access to existing customers.
- You migrated to Fileflare and want to deliver fresh download emails to historical customers.
Before you start: import past orders
Bulk-send only reaches orders Fileflare knows about. If you installed Fileflare after most of your orders were placed, import historical orders first:
- In Fileflare, go to Settings.
- Find Import all previous orders.
- Click Import.
See Import past orders for limits and timing.
Method 1: replace asset (best for file updates)
When you replace an asset and choose to notify, Fileflare sends a “file update” email to every past customer who ordered a product the asset was attached to. One asset at a time.
Plan: Basic and above for the replace function; Growth+ to customize the email template.
Steps
- Customize the File replace email template if needed (Settings → Edit email templates).
- Open the asset in Fileflare and click Replace asset.
- Re-upload the same file (or a new version of it).
- On the final step, choose Yes, notify past buyers. Fileflare sends the file-update email to everyone who ordered a product this asset is attached to.
Method 2: release date (best for next-installment delivery)
Set a release date on an asset. When that date arrives, Fileflare sends the pre-order/release email to every past buyer of products the asset is attached to. Useful for “May’s PDF” or “Chapter 3” deliveries.
Plan: Premium.
Steps
- Customize the Pre-order email template (Settings → Edit email templates).
- Attach the asset to the relevant Shopify product (so past buyers get linked).
- Open the asset and set a release date — choose any future date and time.
- On release, Fileflare sends the email to all past buyers of the product.
Method 3: customer-account announcement (best for one-off broadcasts)
Doesn’t actually use Fileflare’s email — instead, you enable customer account downloads, then use your own email tool (Klaviyo, Shopify Email, etc.) to tell customers to log into their account.
Plan: Basic and above. Works with New Customer Accounts through Fileflare app blocks, and with Classic Customer Accounts through the theme integration.
Steps
- Enable customer account downloads.
- Make sure the asset is attached to the right product so all past buyers see it in their account.
- Send a campaign in your marketing email tool telling customers to log in. If they didn’t create an account at checkout, mention they can sign up using the same email they used.
What about email tracking?
File-update and release emails appear in email tracking on each order page.
Note on the order list view: the “email dispatched” column only shows whether the standard fulfillment email was sent. It doesn’t update when you send file-update or release emails — those only show in the per-order tracking. Don’t be alarmed by the X in the column.
Common issues
- Bulk-send didn’t reach old customers — past orders weren’t imported. Run the import first.
- I want to send to all customers regardless of which products they bought — Fileflare’s bulk methods are scoped to product-attached assets. For broader announcements, use your email marketing tool with Method 3.
- Replace asset emails customers I didn’t want — the email goes to everyone who ordered a product the asset is attached to. Detach the asset from products you don’t want notified before clicking Replace.
- I can only send one asset at a time — yes, by design. Both Methods 1 and 2 work asset-by-asset to keep customer mailboxes from getting blasted with multiple emails per asset.