# BRD-186 — Some providers lock a verified brand entirely

> On at least one provider, a brand's details become uneditable once it is verified.

- **Rule ID:** BRD-186
- **Layer:** Brand (`BRAND`)
- **Checks:** `the brand record after verification`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Wait on an external system or a required interval
- **Required by:** SignalWire
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-186/

## Why this rule exists

Where the lock applies there is no correction path at all — a typo discovered after verification means a new brand and a new campaign, which is a very different plan from an edit. Teams assume the usual re-verification cost (BRD-044) applies and find the field simply will not take a new value.

## How to fix it

Check the brand carefully before it verifies, not after. Where an edit is required on a locked brand, plan a new registration and the migration of the campaigns under it, and keep the old brand live until the new one is verified.

## Check this yourself

**Does your provider lock a brand's details once it verifies?**

1. Ask the provider, or check its documentation, before the brand verifies — the answer decides whether a late correction costs a re-verification or a full rebuild.
2. Where the lock applies, check the record carefully before verification and keep the old brand live if a replacement becomes necessary.

*What wrong looks like:* A team assumes the usual re-verification cost and finds the field simply will not take a new value. A typo means a new brand and a new campaign.

## Notes

Conditional on the submission target, and not tagged with `providers` — the tag budget is reserved for baseline divergences and this is checkable from the operation itself. What the user has to establish is whether their own provider locks verified brands: the answer decides whether a late correction costs a re-verification or a rebuild.