The new membership processing feature is great, but needs more development on second cardholder processing: since the only option is to add ALL individual relationships as Joint Members, it creates a duplicate cardholder if the relationship is already a joint member, or adds an additional joint member even if it exceeds the maximum number of members allowed in the membership setup.

Ideally, the import process would first look at existing cardholders on the membership, and if the relationship already exists on the record and is already a joint member, ignore the relationship and update the settings on the joint member card as defined in the import [expiry date, card not printed, etc]; if the joint member information has changed, give the option to 1) import the new relationship, change the relationship type for the previous joint member [defined in configuration, e.g., “former second card holder”], add the new joint member, and delete the existing one, or 2) ignore the new data, probably with the option of writing the relationship to the record with a defined relationship type.