On this page

A phone number in a Shopify order is a contact detail, not a complete explanation of which text messages the merchant may send. Before adding SMS to a reward journey, identify the proposed message, the responsible sender and the evidence supporting the use. A shipping contact field and a recorded marketing choice answer different questions.

Consider a fictional store that wants to text customers when an approved purchase reward is ready. Its marketing team also proposes a later message inviting the same people to earn another reward on a new purchase. Both messages mention rewards, but they have different purposes. They should not inherit a shared permission label merely because they use the same sending service.

Separate service and marketing message purposes

Describe each proposed message without relying on a template category. “Tell an existing recipient where to access current reward instructions” is a specific purpose. “Encourage another qualifying purchase” is another. A generic label such as “reward updates” conceals the difference the reviewer needs to assess.

The FCC’s consent-revocation order addresses consent and its withdrawal in the context of regulated automated calls and texts. Applying the relevant requirements to a proposed campaign requires review of the sending method, message purpose, current rules and any applicable exceptions. Do not treat that document as evidence that every communication scenario has identical conditions or effective dates.

Create a purpose inventory before composing the final messages:

Proposed text Immediate customer task Evidence requiring review Initial governance decision
Approved reward access notice Reach information about an existing benefit Applicable service purpose, sender and contact permission Review the exact journey before enabling
Reminder about an existing unclaimed award Complete a permitted step already available Current award state and applicable communication basis Assess separately from a new sales invitation
New purchase campaign Consider another order Marketing permission and relevant sending requirements Hold until the necessary basis is documented
Combined access and sales message Access an award and shop again Mixed purpose and promotional conditions Split or obtain review of the full proposed message

This table is a governance screen, not a legal classification engine. Its job is to expose what the merchant must know before a messaging feature is switched on. A service-oriented intention should not be used to hide a new purchase solicitation.

For each journey, locate the evidence that supports the proposed communication. Record the wording presented to the customer, the action they took, the time and source of that action, the party identified as sender and the purpose it covered. If evidence is missing, record the gap rather than infer consent from possession of a phone number.

Suppose the fictional store has three customer records. Record A contains only a shipping phone number. Record B contains a documented choice about the store’s promotional texts. Record C contains an old imported flag called “SMS yes,” with no retained wording or source. These records should not be treated as equivalent.

A practical evidence map might mark A as insufficient by itself to approve the proposed marketing journey, B as ready for review against the actual campaign and sender, and C as unresolved. That approach avoids two errors: assuming every stored number is usable, and assuming that a bare Boolean is enough to explain a permission history.

Identify the sender at each level. The brand visible to the customer, the legal entity responsible for the campaign, the platform coordinating a reward and the messaging vendor may be different parties. Ask the responsible reviewer which parties and purposes the recorded permission covers. Technical access to a sending account does not answer that question.

A difficult case is an agency importing an audience from another campaign. Require the original collection context and the authority to use the information for this proposed journey. Do not rely only on an assurance that the list was collected “with consent.” The scope of that consent is the information the merchant needs to evaluate.

Keep the approved reward path available through permitted channels when SMS cannot be enabled. The choice not to add a particular communication channel should not silently become a new qualification condition for an already earned purchase benefit. Confirm the appropriate alternative with the actual program rather than inventing one in the marketing plan.

Describe how an instruction to stop messages reaches the people and systems that need to act. The record should show the receiving route, interpretation process, affected message purposes, responsible sender and confirmation of the resulting control. Do not reduce the whole process to one keyword without checking the current requirements applicable to the proposed use.

Test the workflow with a clearly synthetic case. A customer revokes permission after the next promotional message is queued. Which owner confirms that the instruction reached the sending process? How are unresolved scope questions escalated? What happens to a separate, existing reward case? The demonstration should distinguish marketing suppression from the status of the customer’s earned benefit.

Record timing requirements only after the qualified reviewer confirms the current rule and the provider’s supported process. FCC developments, court decisions and state requirements can affect the analysis. A historical implementation checklist should not become a permanent assumption that all future campaigns use the same standard.

The approval record should contain a clear disposition: ready under specified conditions, held pending evidence, or outside the permitted scope. For the fictional store, the new purchase invitation remains on hold for records A and C. Record B still requires confirmation that its documented permission matches the actual sender, purpose and delivery method.

Assign a trigger for reassessment. A different sender, new promotional content, imported audience or changed opt-out process can alter the decision. The merchant needs an owner who knows when those changes must return for review, rather than a one-time approval attached to a generic SMS feature.

The completed evidence map should explain why each proposed text may proceed and what would stop it. That is a usable foundation for implementation. A list of phone numbers with unexplained permission flags is not.

Discuss the permitted communication channels and responsibilities for your proposed rebate program.

Discuss program fit

Source references

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.