Select individual products when your announcement must follow an agreed list. Choose a collection when its current membership should decide the release. Both can work, but saving a drop does not freeze its product details or guarantee that every item will be announced.
Choose who controls the release list.
Start by writing down the products you intend to announce and who can change that list. In MemberPort’s current implementation, a drop uses either selected products or one collection. It does not combine the two modes or provide its own collection-rule editor.
The MemberPort details in this article were checked against committed early-access code on September 28, 2026. The app service was unavailable during that review, so these are implementation details, not a live delivery test. Confirm early-access availability before planning a launch that depends on the app.
| Your release | Starting choice | What to check |
|---|---|---|
| One hero product or an agreed list of up to 50 products | Select products | Save the intended product IDs; recheck their current details and eligibility before launch. |
| A release managed together in Shopify, with at most 250 total products | Use a collection | Review its membership and coordinate edits until delivery starts. |
| A broad collection that includes products outside this release | Select the intended products, within the 50-product limit | Do not rely on product status to substitute for a deliberate release list. |
| A collection with more than 250 total products | Narrow the release before scheduling | MemberPort rejects an oversized collection; it does not take the first 250 eligible products. |
| An announcement for one exact variant | Check a different workflow | Current MemberPort cards link to products; variant-specific targeting is not verified. |
Know what stays fixed and what is read again.
Selecting products saves their IDs. Preview and initial delivery preparation fetch current Shopify information for those IDs. A title or image can change after you save; a deleted or ineligible product can disappear from the announcement. Fixed selection therefore means fixed intended identities, not frozen cards.
Collection mode saves the collection reference. Its products are resolved again for preview and when delivery is first prepared. Saving or previewing does not lock membership. Once delivery has prepared its messages, retries reuse those prepared parts rather than fetching a new collection list on every attempt.
A collection drop still produces individual product cards and product-page links. It does not send one collection landing-page button. Up to five eligible products fit in each message, so check the preview’s message count as well as its product count. Later collection edits do not automatically create another announcement.
Check the collection your store actually uses.
Shopify’s current collection guidance describes a new model rolling out in place of legacy manual and smart collections. Sources can include products, variants, other collections, and apps. Your admin may still show the older model. Review the actual included products and the conditions or manual edits that can change them; do not assume a collection name defines its contents.
The June 17 API announcement makes collections using new sources visible from API version 2026-07. MemberPort uses that version, but reads product-level collection results. That does not establish support for every variant-only or app-source configuration. Shopify’s July 16 announcement describes Shopify capabilities, not additional MemberPort controls. For a tightly specified launch, individual product selection is easier to audit.
Review activation before using a mixed-status collection.
Without activation, MemberPort’s formatter requires Active products with valid handles and usable product links. The collection size limit is checked before this eligibility filtering. A 260-product collection with only ten Active items still exceeds the 250-product limit.
The activation option deserves a separate decision: delivery attempts to set every resolved non-Active product to Active. It is not restricted to Draft products; Archived and Unlisted products can also be affected. Preview only simulates that change and does not update Shopify. Leave activation off unless you intend the status change for every product included at delivery.
Shopify notes that archiving does not remove a product from its collections. Review the actual roster rather than assuming archived items are absent. Active status also does not prove Online Store publication or a working purchase path. Follow the Active versus published checklist for those separate checks.
Use a release roster to catch changes after preview.
Keep a short record outside the app: product ID, name, intended inclusion, current status, customer-facing link, and person responsible. Record the preview time and counts alongside it. This is a manual planning aid, not a MemberPort approval or locking feature.
Fictional example: a release should contain a cap and a tote. Its collection also contains an archived sticker. With activation off, the sticker is excluded; with activation on, the current implementation can reactivate and include it. Selecting just the cap and tote makes the intended list explicit. Both still need a fresh link and status check before delivery.
- Record the agreed product IDs and decide whether the selection or collection controls inclusion.
- For collection mode, count all products before eligibility filtering and identify who can change membership.
- Decide explicitly whether any included non-Active product should become Active. Review every affected item.
- Refresh the preview after Shopify edits. Compare names, links, product count, excluded count, and message count with the roster.
- Resolve unexpected additions or omissions before enabling a scheduled launch. Record the last review time and responsible person.
Sources & further reading
MAKE YOUR NEXT DROP A MOMENT
A product launch
your community can find.
Plan selected Shopify products, the Discord channel, and the announcement time with MemberPort.
Request early access