MEMBERPORT — DROP REHEARSAL RECORD
Reviewed: October 5, 2026
Guide: https://memberport.io/blog/test-shopify-discord-product-drop/

Manual merchant worksheet, not an app test mode or an automatic approval.
A rehearsal sends a real Discord message. Record actual observations; leave
unknown results as incomplete. The public app service was suspended during the
October 5 review; confirm restored access before following these steps. They
describe committed early-access code. No messages were sent for this guide.

1. BEFORE THE CHANNEL SWITCH
Normal announcement allowance checked for rehearsal plus real release:
Reviewer / launch owner:
Original connected server and announcement channel:
Rehearsal channel:
Pending real drops, owners, saved times and current states:
Pending launches paused/coordinated by / at:
Any delivery already underway or partially sent? If yes, resolve before switch:
Rehearsal destination saved and rechecked by / at:

2. PRODUCT AND AUDIENCE
One selected product ID and name:
Current status (choose an already-Active product):
Public product URL:
Link checked without Shopify Admin session by / at:
Product safe for connected-server discovery through /drops? Yes / No
Activation left OFF? Yes / No
Reviewers and relevant channel/command permissions:
Latest preview time and product/message/excluded counts:
Unexpected preview result and resolution:

3. MANUAL RUN — use a new drop
Internal drop name / ID (not outgoing promotional text):
Saved as Manual, enabled, activation off:
Announce now action time (include date and zone):
App status observed:
Discord message time and message link:
Ordinary reviewer could open the product link? Observation:
Intended product, image and destination? Observation:
Any failure or partial delivery? Owner and resolution:
Completed rehearsal drop paused by / at:

4. SCHEDULED RUN — separate new drop, if scheduling is being checked
Internal drop name / ID:
Saved future launch date/time and displayed IANA zone:
Saved as Scheduled, enabled, activation off:
Did anyone use Announce now or Check launches? If yes, this did not establish
normal background-worker delivery. Check launches runs all due enabled drops:
App status observed and observation time:
Actual message arrival time and message link:
Ordinary reviewer’s product-link observation:
Unresolved issue and owner:
Completed rehearsal drop paused by / at:

5. RESTORE AND HAND OFF
[ ] No rehearsal delivery remains unresolved.
[ ] Completed rehearsal drops paused; posted messages may remain.
[ ] Fresh /drops result reviewed under intended reviewer permissions.
    The product can still appear through another enabled, announced drop.
[ ] Original announcement channel restored, saved, and rechecked.
[ ] Each pending real drop reviewed before resuming.
    A past-due unannounced drop can become eligible immediately on Resume.
    Agree on a new future time while paused if an immediate send is unwanted.
[ ] Remaining issues have an owner and next check time.

RESULT
Manual path: Pass / Incomplete / Not run
Scheduled path: Pass / Incomplete / Not run
Audience and product-link check: Pass / Incomplete
Restoration: Complete / Incomplete
Overall release decision: Proceed / Hold
Evidence supporting that decision:
Responsible person and time:

READ THIS RESULT NARROWLY
Preview is not delivery evidence. A manual send does not prove the scheduled
worker path. A scheduled time is not an exact-second delivery promise. Pause
does not retract an in-flight or posted message. This record neither freezes
product details nor establishes future service availability.

PRIMARY REFERENCES
https://support.discord.com/hc/en-us/articles/10543994968087-Channel-Permissions-Settings-101
https://support-apps.discord.com/hc/en-us/articles/26501869403159-Command-Permissions
https://help.shopify.com/en/manual/products/details/product-details-page