A2P 10DLC for retail stores, in plain English

If you text customers from a regular 10-digit number, US carriers require your business to be registered under a framework called A2P 10DLC — “application-to-person, 10-digit long code.” Skip it and your messages get throttled hard or filtered outright. Here's the whole thing in plain English, from having filed it for our own stores and now for every store we onboard.

Why this exists

Carriers spent years drowning in spam from anonymous local numbers. Their answer: if software sends texts on a business's behalf, the business must be registered — who you are, what you send, and how people opted in. Registered traffic gets real throughput and better deliverability; unregistered traffic gets treated as spam. It's paperwork, but it's paperwork that decides whether your win-back campaign arrives.

The two registrations

1. Brand registration — who you are

Your legal business identity: legal name, EIN, address, website. The single most common failure is trivial: the legal name not matching your EIN paperwork. “Peak Nutrition” might be the sign on the door while the IRS knows you as “PN Retail Holdings LLC.” Register the legal entity exactly as the IRS knows it, DBA in the DBA field. Sole props without an EIN can register in a limited tier, but expect lower throughput — worth getting the EIN.

2. Campaign registration — what you send

This is where a human or a vetting system reads what you submit. Carriers check:

• Use case. A supplement store's loyalty texting is typically marketing/promotional, sometimes mixed with account notifications. Register what you'll actually send — a “customer care” registration sending promo blasts reads as deception and gets filtered.
• Sample messages. Two to five realistic examples. Include your brand name and the opt-out line (“Reply STOP to opt out”) in the samples, because your real messages will include them. Right?
• Opt-in description. How a customer consents — e.g., “customers opt in via a checkbox on the in-store check-in kiosk.” This must be a real, provable flow. Purchased lists and assumed consent are rejection material and legal exposure.
• Consistency. Website live, brand name in samples matching the registered brand, use case matching content.

Timelines and costs (set expectations now)

• Brand registration: often quick — days, sometimes hours.
• Campaign review: the long pole. Days to a few weeks; plan for about two weeks and be pleasantly surprised.
• Fees: small one-time registration/vetting fees and a modest monthly per-campaign carrier fee — typically a few dollars a month, varying by use case. Plus per-message carrier surcharges on top of your platform's rate.

After approval: registration is necessary, not sufficient

10DLC gets you in the door with a throughput tier tied to your brand's trust score. Filtering still applies — burst sending, link shorteners, and complaint-heavy lists get clipped even when fully registered. The operating discipline (drip sending, quiet hours, clean consent, no shared shorteners) is the other half; we covered it in the filtering post.

Who should do the filing

You can file it yourself through your SMS provider's console. But the form asks questions in carrier-speak, and a rejected campaign costs you weeks. This is exactly the kind of thing a platform should own: on Eco Systems CRM, we collect your business info during the setup wizard and file the registration for you — it's included, because a loyalty platform whose texts don't deliver isn't a loyalty platform.

The rejection reasons we actually see (and the fixes)

Campaign reviews fail for boring, fixable reasons. If yours bounces, it's almost certainly one of these:

• Legal name mismatch. The brand's legal name doesn't match IRS/EIN records character-for-character. Fix: register the entity exactly as it appears on your EIN letter (CP 575), DBA in the DBA field.
• Dead or thin website. The URL you listed 404s, or is a single page with no mention of the store. Fix: a live site with your store name, address, and a privacy policy that mentions SMS.
• Sample messages without opt-out language. Reviewers want to see “Reply STOP to opt out” in the samples because it must be in the real messages. Fix: include it, verbatim.
• Vague opt-in description. “Customers sign up in store” fails; “customers check an SMS-consent checkbox on the self-serve check-in kiosk; consent is logged with timestamp and source” passes. Specific, provable, honest.
• Use-case mismatch. Registered as account notifications, samples read like promos. Fix: register marketing (or mixed) if you send marketing. The honest registration is also the durable one.

Quick answers

Do I need this for a toll-free number instead? Toll-free has its own separate verification process — different form, same idea: unverified traffic gets filtered. Does registration cover multiple locations? One brand can run one campaign across locations if the messaging program is the same; separate legal entities need separate brands. Can I text while review is pending? Technically some traffic may pass; practically, don't — unregistered sends filter heavily and complaints during the window hurt the brand you're trying to establish. Launch points and kiosk first, texting after approval — the sequencing is built into our migration process for exactly this reason.