Active is not the same as available: check your Shopify links before a drop

Write the launch outcome in one sentence.

For a straightforward release, try: “At the launch time, these products should be available on our Online Store, and this Discord channel should receive their names and links.” That gives the person preparing the store and the person arranging the announcement the same target.

Use an explicit list of products. “The collection is ready” is harder to verify than a short list of customer-facing links, especially if collection membership changes during launch preparation. Keep a named owner beside the final check.

Check status and publication separately.

Shopify product status and the Publishing section answer different questions. The first describes the product’s state; the second controls where it is available. An Active label alone does not establish that the product is published to the sales channel your audience will visit.

MemberPort’s optional product-activation step sets selected products Active. It does not configure their Online Store publication settings. Review that option deliberately and prepare the destination in Shopify. The API’s productUpdate operation and publication operations are distinct.

Put both schedules into the same launch brief.

Shopify supports future publishing to the Online Store and supported channels. Its guidance says the product must be Active at the publication time and calls attention to the store’s time zone. Compare that schedule with the time zone displayed for your MemberPort drop.

For a first important launch, publish, verify the public links, and then announce. Once the process has been proven, decide how closely to schedule later releases. This is an operating recommendation, not a guarantee that two services deliver at exactly the same second.

A useful brief has a line for the store publication time and another for the community announcement time. Include the date and zone in both. If a teammate works elsewhere, use the shared brief to confirm the moment instead of sending “six o’clock” in a message.

Check the product as a shopper.

Use the final product URL rather than a Shopify Admin preview. Open it without a staff session. Check the item name, the options being offered, and the market you intend to reach. A visible page and a successful buying path are related checks, not interchangeable proof.

If you manage variant publication, review it too. Shopify explains that both the parent product and the variant need publication to the channel for the variant to display there. Check the actual option your announcement is about.

If a link fails, fix the storefront before treating Discord as the problem. A message can be delivered successfully while still pointing to an unavailable destination. Reposting the same link will not change product availability.

Save a preflight you can repeat.

Use one row per item and record a result rather than a checkmark from memory. Mark an unresolved exception clearly and decide whether to delay the announcement. The worksheet below is a blank operating aid; it does not inspect your store automatically.

• Confirm the final products or collection contents.
• Review the product status and sales-channel publication.
• Open each product link as a customer.
• Check the options shoppers are expected to buy.
• Compare publication and announcement times, including zones.
• Confirm the selected Discord server and channel.
• Preview the intended names and links in the app.
• Assign one person to the final launch decision.
• After delivery, open a link from the actual Discord message.