How to rehearse a Shopify product drop in Discord

Choose a small rehearsal with a clear purpose.

Use one already-Active product with a working customer-facing page and an image you are happy to show. Select it individually and leave Activate products in Shopify off. This tests the announcement path without deliberately changing product status. Shopify treats product status and sales-channel publishing as separate settings; verify the public link before starting.

MemberPort has no separate sandbox delivery mode. A rehearsal announcement is a real Discord message. Its internal drop name does not add a TEST label to the outgoing card, so explain the exercise to your reviewers beforehand. Do not use an unreleased secret product. Rehearsal deliveries count toward the normal announcement allowance; check that your available allowance covers the rehearsal and the real release.

Availability note — October 5, 2026: MemberPort’s public app service was suspended during this review. These steps describe its committed early-access implementation for use after access is restored and confirmed. No live announcement was sent to prepare this guide.

Record the original channel before changing anything.

MemberPort’s destination is store-wide. Write down the connected server and current announcement channel, then review pending drops with their owners. An unstarted announcement uses the selected destination when it is processed. Switching to a rehearsal channel can therefore redirect another release.

Pause or coordinate pending launches before the switch, and confirm no delivery is underway. Do not treat Pause as a way to retract a send already in progress. If a drop has begun delivery, resolve its state first: a retry requires the channel where that delivery began.

Choose an ordinary text channel for the exercise and save it in Setup. Use the existing channel-setup guide for the full permissions walkthrough. For product cards the bot needs View Channel, Send Messages, and Embed Links; reviewers need appropriate channel access. Discord’s channel-permissions reference explains those separate controls.

Treat command discovery as a separate audience check.

A restricted rehearsal channel does not make the announced product private. MemberPort’s /drops command can retrieve products from enabled, announced drops elsewhere in the connected server where the command is allowed. Its reply being visible only to the person invoking it does not restrict which eligible products that person can retrieve.

Review the app under Server Settings → Integrations on desktop to understand who can use its commands and in which channels. Discord documents these controls in Command Permissions. Choose a product safe for the connected community to discover even if someone invokes /drops outside the rehearsal channel. This check does not require loosening your existing command permissions.

Run the manual and scheduled checks separately.

For the manual check, create a new drop, select Manual, choose the product, keep activation off, and refresh Preview. Resolve unexpected products or exclusions. Enable and save the drop; saving a manual drop does not send it. Select Announce now only when reviewers are ready for the real message.

Record the action time, the app’s resulting status, the observed Discord message time and a message link. Have an ordinary reviewer open the Shop button without a Shopify Admin session. If the app reports a problem, check the channel before attempting another send; a partial delivery is different from no delivery.

To check scheduling, create a separate drop after finishing the manual check. Select Scheduled and a future time in the zone displayed by the app, leaving enough time to review it. Record that saved time, refresh Preview, then enable and save. Wait for processing without using Announce now or Check launches. Announce now bypasses the schedule; Check launches manually processes all due, enabled drops for the store. Either action would prevent this run from proving normal background-worker delivery.

Record when the message actually arrives and the status you observe. A saved time is the start of eligibility for background processing, not a delivery deadline. If the announcement remains unresolved, mark the check incomplete and investigate before planning the real launch.

Close the rehearsal before restoring pending launches.

Pause each completed rehearsal drop to remove that drop from subsequent /drops results. This does not delete posted Discord messages, and the same product may still appear through another enabled, announced drop. Check a fresh command result rather than assuming the product has become private.

Once deliveries are resolved, restore and save the original announcement channel in Setup. Recheck each paused real launch before resuming it. Pause preserves its saved schedule: an unannounced drop whose time has passed can become eligible as soon as it is resumed. Agree on a new future time while paused when an immediate send is not intended.

Keep the message links and observations in the downloadable record. A pass needs observed delivery, the intended link and audience, and completed restoration. If any item is uncertain, write down the issue, owner, and next check. One successful rehearsal is evidence about that run, not a guarantee for every future launch.