Skip to content
Documentation navigation

Start here

Product

Integrations

SDK

MCP

Shipped-update emails

Who is eligible

When shipped-update sending is available, a customer can receive an email only if they have opted in to status-update emails, have an email address, and still have a current customer-type vote on the request. A review source or owner vote alone is not enough. Deleted customers are excluded.

Public submissions must be enabled for the workspace. The item must currently be Shipped and must not be archived or merged. Eligibility is checked again before dispatch. Cancelled subscribers remain eligible: an active paid subscription is not required.

An SDK-supplied email is unverified. Someone can supply an address they do not own; an email notification does not verify identity or ownership of that address. Read Security and privacy.

When an item ships

A transition to Shipped can trigger an update for eligible voters when sending is available. A changelog publication is separate and does not itself promise an email. The status-change note may be included in the email, so do not put confidential information there.

Items already shipped before sending becomes available are not emailed retroactively. Simply saving an already-Shipped status does not create a new transition. Reopening and shipping again does not reset previous delivery claims. See Roadmap and Publishing a changelog.

Delivery and deduplication

Delivery is not guaranteed. Upweight permanently deduplicates delivery per item and customer and per item and normalised email address (trimmed and lowercased). Reopening and shipping the item again, changing a customer's address after a delivery claim, or recreating a customer does not erase retained claims.

If the email provider's outcome is uncertain, Upweight does not retry: avoiding duplicate mail takes priority over trying again when acceptance is unknown. A definite provider rejection can be retried, but an accepted or uncertain attempt is not replayed. An eligible customer may therefore receive no email.

Unsubscribe

Every shipped-update email includes one-click Unsubscribe. It disables shipped-update emails for that workspace customer, not every customer record using that email address. It is not email verification or an address-wide unsubscribe across workspaces.

If no email arrives

Check the customer's opt-in preference and address, whether their customer vote still exists, whether public submissions are enabled, and whether the request is still Shipped rather than archived or merged. Check spam folders too. A prior delivery claim or an uncertain provider outcome can suppress another attempt even after reopening.

Do not repeatedly change status to force delivery. Shipped-update emails are conditional, not a guaranteed notification channel. Customers can still browse your public roadmap and changelog. See Troubleshooting and Public boards.

For in-app feedback, see the SDK overview, Swift SDK guide, and HTTP API reference.

Last reviewed