Understanding Branch Codes and Numbers
How Sermfy auto-generates identifiers for every branch, and why you can't set them manually.
How a branch code is built
A branch code combines the first letter of your church's member prefix with "B" and a 4-digit number, for example DB0001. Branch number is a separate 2-digit sequential value.
Why this is automatic
Auto-generating these avoids collisions and keeps every branch's identifier consistent with your church's own member-numbering convention, rather than staff needing to invent and remember a unique code for each new location.
You can rename a branch's display name freely, that never changes its underlying code or number, so any reports or member codes already referencing that branch stay stable even after a rename.
Best practice
Don't try to make branch codes "meaningful" by renaming branches to force a particular code, the generated code isn't meant to be read as an abbreviation, your branch's actual name is what staff and reports should rely on for recognition.
Related Articles
Adding a Branch Admin
How to assign someone admin access scoped to a specific branch, including what happens if they don't have a login yet.
Creating a New Branch
What happens automatically when you add a second location to your church.
Switching Between Branches
How the branch switcher works, and why your selection persists across sessions.
Deleting a Branch: What's Blocked and Why
The two situations where Sermfy won't let you delete a branch, and what to do instead.