Write down the launch, not just the date.
Record the products or collection, the intended customer-facing channel, the launch time, and who owns the final check. For a collection, review the membership again close to launch. A newly added or removed product can change what the drop resolves.
Check the time zone displayed by the app rather than assuming a date shown in your browser uses the same zone as your store or another team member. Confirm the intended moment when coordinating across regions or a daylight-saving change.
| Before scheduling | Evidence to keep |
|---|---|
| Products or collection | The items expected in the release |
| Discord destination | The selected server and channel |
| Launch time | Date, time, and displayed time zone |
| Storefront readiness | A working public product URL |
| Launch owner | Who checks the result and handles a problem |
Product activation is one part of readiness.
MemberPort offers an explicit option to set every resolved non-Active product Active when a drop launches. This can affect Archived and Unlisted products as well as Draft products, so review the entire selection first. That action changes a product’s status. It does not by itself publish the product to every sales channel, establish inventory availability, or prove checkout will work for every shopper.
Use Shopify’s publishing settings for the actual channel availability. Test the product link without being signed in to Shopify Admin, including the market you plan to send customers to. Keep the announcement and the storefront release coordinated.
Know what happens after the scheduled time.
A background worker processes scheduled drops. Treat the chosen time as the start of processing, not a promise of delivery at an exact second. Shopify and Discord availability, permissions, and processing can affect when the message appears.
Check the drop’s status and the destination channel before attempting another announcement. If something looks wrong, first establish whether a message already arrived. Recreating the launch without checking can confuse both the operator and the community.
Run a small rehearsal.
Channel selection is store-wide. Review pending announcements before changing to a test channel, coordinate or pause affected releases, and record the original destination so you can restore it. Use a product safe to discover across the server: /drops can return announced products outside the restricted destination. Schedule a near-future drop, check the actual output, open its product link, and try /drops. Pause the completed rehearsal to remove it from future /drops results; existing messages remain. Check pause and resume with care: resuming a past-due unannounced drop can make it eligible immediately.
Bring your planned release to early access. The setup discussion covers the selected products, channel, and launch process. It does not require customer lists, order data, or a paid-membership policy.
Sources & further reading
PLAN YOUR NEXT RELEASE
Bring the drop
to your community.
MemberPort connects selected Shopify products to a Discord announcement channel.
Request early access