Robert Allen Jr. buys a family membership online. Six months later his father, Robert Allen Sr., buys one too. Without a suffix, those two records look almost identical in Altru: same name, often the same street, sometimes the same phone number. One of three things tends to happen next. The records get merged by mistake, the son’s renewal letter goes to the father, or someone at the desk types “Jr.” into the last name field to tell them apart, which causes its own trouble later.
Name suffixes look like a cosmetic detail until they aren’t. Below is what to check in your membership web forms, the workarounds that hold up, and the shortcuts that create more cleanup than they save.
Start by confirming what your forms can actually do
Altru constituent records have a place for a suffix, and it feeds the name formats you use for addressees and salutations. Whether your membership web forms let the public fill that field in is a separate question. Form options have changed over time and differ by form type, so don’t rely on memory or on what another organization told you.
- Open the membership form in your form designer and look through the available name and contact fields. If suffix is available, turn it on and make it optional.
- Compare with your donation and ticketing forms. Sometimes one form type exposes a field another doesn’t. If suffix appears elsewhere but not on membership, that’s worth noting when you contact support.
- Run a test transaction in a sandbox or with a test constituent, then open the resulting constituent record. Confirm the suffix landed in the suffix field and not appended to the last name or dropped into a comment.
- If you can’t find it, ask Blackbaud support directly whether suffix can be collected on membership web forms in your version, and whether a custom question can map to it.
That last point matters. A custom question can usually collect a value, but collecting it and writing it to the right constituent field are two different things. A suffix stored as a free-text answer won’t show up in your mailing name formats unless someone copies it over.
Workarounds if the form won’t collect it
Ask after the purchase, not during it
Your membership acknowledgment or welcome email can include a short line: “Do you use a suffix such as Jr., Sr., or III? Reply and let us know.” Responses are low volume, and staff can add the suffix to the constituent record directly. It’s manual, but it puts the value in the right field.
Catch it at the desk and on the phone
Members who renew in person or by phone can be asked once. Add it to the script for new memberships and for any renewal where staff are already confirming the mailing address. Keep it optional; most people don’t have a suffix, and the question should take two seconds.
Use a custom question as a holding area
If your form supports a custom question but can’t map it to the suffix field, you can still collect it there and move it during regular membership processing. Build a query that returns constituents with a non-blank answer and a blank suffix field, and work that list on a schedule. The risk is that the step gets skipped when the membership team is short-staffed, so assign it to a person.
What not to do
- Don’t tell people to put the suffix in the last name field. “Allen Jr” as a last name breaks alphabetical lists, throws off duplicate matching, and produces salutations like “Dear Mr. Allen Jr.”
- Don’t put it in the first or middle name field. Same problem, different spot on the envelope.
- Don’t merge two matching names at the same address without checking. Father and son, or mother and daughter with the same name, are common. Look at birth dates, email addresses, and membership history before you combine anything.
Clean up what’s already there
If online forms have been running without a suffix for years, some members have almost certainly worked around it themselves. A constituent query can show you how much of this exists. Filter last names and first names that end in common suffix strings: “Jr”, “Jr.”, “Sr”, “Sr.”, “II”, “III”, “IV”. Expect a few false positives (some surnames legitimately end in those letters), so review the list rather than updating it in bulk.
For each real match, move the suffix into the suffix field, correct the last name, and check whether a near-duplicate record exists for a relative. Then spot-check a few addressee and salutation outputs to make sure the name formats read correctly.
Replacing the membership form entirely
Some organizations reach the point where several fields they want are hard to collect on the standard forms, and suffix is one item on a longer list. Social Good’s Checkouts is a branded, mobile-friendly checkout that replaces Altru web forms for memberships, tickets, and donations, with the data written back to Altru. If you’re evaluating it, bring your list of required fields, suffix included, and confirm how each one maps to the constituent record before you switch.
Quick answers
Does a suffix change how Altru matches duplicates?
It can help staff tell two similar records apart, but don’t assume any automatic matching rule treats suffix as a deciding factor. Test with two sample records if it matters to your process.
Should suffix be required on the form?
No. Make it optional. A required suffix field gets filled with “N/A” or a period, and then you have a different cleanup job.
