An unsubscribed customer still needs an order update

Establish what the customer actually opted out of

Open the suppression record in your authorized system and read what it covers. A marketing-list unsubscribe, an account-level communication preference, and a do-not-contact instruction are different states with different scopes. Record the recorded action, its date, and the wording the customer saw when the choice was made, where that record exists. A suppression entry with no associated wording leaves the scope uncertain; note that uncertainty rather than assuming it covers everything or nothing.

Also confirm the update is real. Identify the order number, the event that requires the update (a delay, an address problem, a shipment change), and why this customer needs it now. A general announcement dressed up as an order message is not an order update, and neither is a win-back message referencing an old order. If no current order event exists, there is nothing to send and the question dissolves.

Classify the message by its primary purpose and content

Under US CAN-SPAM guidance, whether an email is treated as commercial or as falling within the narrow transactional category depends on the message's primary purpose and content. An existing customer relationship is not, by itself, enough to move a promotional message into the transactional category. That is a US email framework; other jurisdictions and other channels apply their own rules, and this page does not decide them.

Read the actual draft. A message that tells the customer their order status changed, asks for an address correction, or confirms a refund is anchored to the order. A message that adds a discount code, a new-product line, or a browse-again prompt has mixed purposes, and mixed messages deserve the stricter treatment. Strip promotional content out of the transactional draft rather than arguing the promotion is minor. When the purpose genuinely cannot be classified, the decision belongs to the policy owner with qualified advice, not to the person holding the send button.

Choose the delivery route, not just the wording

Order communications should travel the route your store uses for order notifications, and promotional content should travel the marketing platform that honors suppression lists. These routes are frequently separate systems with separate subscription states. Sending a transactional message through the marketing platform risks it being suppressed or misclassified; sending a promotional message through the order route bypasses the suppression the customer recorded. Verify which system will actually send before sending.

Check that the transactional route does not append marketing templates, promotional footers, or cross-sell blocks by default. If it does, that template behavior is itself a finding to correct with the template owner. Record the route used, the template applied, and the send date against the order, so a later question about this message can be answered from records rather than memory.

Record the decision and hand unresolved cases up

For each message, log the suppression record consulted, the order event, the final content's purpose, the route, and who approved the send. Where classification was straightforward, that log closes the question for this order. Where it was not, name the policy owner who will decide, with qualified counsel where legal classification is at stake, and hold the send until that decision exists. Do not send first and classify afterward.

A pattern of uncertain cases usually means the store lacks a written rule for transactional content. That is a policy gap for the owner to close, not a case-by-case improvisation for staff. If you want a structured look at how your order emails and policies describe this boundary, a Prism website-review consultation can examine the public representations involved; agree the pages, scope, fees and terms before any work begins.

Message-purpose and delivery-route sheet

Complete one copy per order update before sending. The point is a documented purpose, an authorized route, and a named owner for anything unresolved. Keep the message body and customer contact details in your authorized systems, not in this sheet.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.