The local print shop that produces your exhibit signage is also a corporate member. The farm that sells you animal feed buys a table at the gala every year. Sooner or later, someone in merchandise or finance needs to set one of these organizations up as a vendor, opens Altru, and finds that the organization is already there as a constituent. The obvious question is whether you can flag that existing record as a vendor rather than creating a second one.
Here is what we know, what we don’t, and how to keep the two sides of the relationship from drifting apart.
How vendors and constituents relate in Altru
In Altru, vendors belong mainly to the merchandise side of the system: purchasing and receiving inventory. Constituents belong to the fundraising, membership, and sales side. The two areas were built for different staff with different jobs, and in practice many organizations find that a vendor and a constituent for the same company end up as separate records, with no button that converts one into the other.
We are deliberately not giving you a click-path here. The exact behavior depends on your Altru version and on how your merchandise module is set up, and Blackbaud does change things over time. Before you plan around either answer, confirm it:
- Test in a sandbox or training database if you have one. Try to add a vendor and see whether Altru lets you search for and select an existing organization constituent, or only lets you enter a new name.
- Open a case with Blackbaud support and ask directly: “Can an existing organization constituent be designated as a merchandise vendor, and if not, what is the recommended way to link them?” Save the answer in your internal documentation.
- Check the Altru Knowledgebase for vendor setup articles that match your current release.
If you can’t convert the record: link the two instead
Assuming you end up with two records for one organization, the goal is that anyone looking at either one can tell the other exists. A few low-effort ways to do that:
Use an identical name
Spell the vendor name exactly as the constituent name appears, including “Inc.” or “LLC.” It sounds minor, but it is what makes the two show up together when someone searches, and it keeps any reconciliation query you build later from missing a match because of a stray comma.
Mark the constituent record
Add a constituent attribute such as “Also a merchandise vendor” (yes/no), or a note that records the vendor name and when it was set up. Development staff calling on a corporate member should know you also buy from them. That context matters when you’re asking a supplier for a sponsorship.
Put a reference on the vendor side
If the vendor record has a notes or comments area, record the constituent’s lookup ID there. Then the merchandise team can find the giving and membership history without guessing at name variants.
Decide who owns contact details
Addresses and contact people are where two records cause real trouble. The vendor record usually carries the billing or remit-to address and a sales rep; the constituent record carries the marketing contact or the executive you steward. Write down which record is authoritative for which kind of contact, so nobody “fixes” the vendor address using the membership mailing address.
Don’t let deduplication undo your work
Duplicate-cleanup routines tend to look at constituents. If someone previously created a constituent just so the organization would appear on the merchandise side, or added the vendor’s sales rep as an individual constituent, those records may get flagged and merged without anyone realizing what they were for. Before any cleanup, pull a list of constituents carrying your vendor attribute and review them by hand.
The reverse risk is also real: never create an extra constituent purely to make an organization “show up” as a vendor. That gives you three records instead of two.
A simple reconciliation habit
Once or twice a year, compare your active vendor list with your organization constituents. A constituent query filtered on the vendor attribute, exported next to a vendor list, is usually enough. You are looking for:
- Vendors with no matching constituent who also give, sponsor, or hold a membership.
- Constituents flagged as vendors whose vendor record has been closed or inactivated.
- Name mismatches that have crept in since the last check.
It takes less than an hour for most organizations, and it stops the two lists from quietly diverging.
Quick answers
Will merging records solve this?
Constituent merge tools work on constituents. Don’t assume they can absorb a vendor record; check with Blackbaud support before attempting anything that combines the two.
Should we track vendor spend on the constituent record?
Generally no. Purchasing totals belong with merchandise or your accounting system. A yes/no flag and a note are enough to give development staff the context they need without mixing expenses into giving history.
