# BRD-050 — A stock symbol may back only one brand

> A stock symbol already registered against another brand cannot be used again.

- **Rule ID:** BRD-050
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.stock_symbol`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Twilio, TCR
- **Applies:** Applies when the brand is a public company.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-050/

## Why this rule exists

The ticker is treated as an identity key, so two brands claiming the same symbol is read as one of them being wrong. Large groups hit this legitimately: a subsidiary registering under the parent's ticker collides with the parent's own brand, and the subsidiary has no visibility of it.

## How to fix it

Register the subsidiary under its own entity type and identifier rather than the listed parent's ticker. Where the listed entity itself is being registered twice, share or transfer the existing brand instead of creating a second one.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30703` | yes |

## Check this yourself

**Has anyone else in your group, or a former vendor, already registered a brand under this ticker?**

1. Ask the parent company's messaging or IT owner whether a 10DLC brand already exists for the listed entity.
2. Where one does, route this traffic through the existing brand rather than creating a second one; a subsidiary registers under its own entity and identifier, not the listed parent's ticker.

*What wrong looks like:* A subsidiary registers under the parent's ticker and collides with the parent's own brand — a record it has no visibility of and cannot query.

## Notes

The collision is against every brand in the registry, which we cannot see. The user has to establish whether anyone in their group — or a former vendor — has already registered a brand under this ticker, and if so route the traffic through that brand rather than duplicating it.