Answers.Body: <p>The logic behind the behaviour you're observing is that most of the time when a contact is paying for a different membership type than their existing one, they are upgrading or changing that membership. Whereas an administrator is doing it, they can be trusted to differentiate between an update/change vs. a new one.</p>
  <p>The link you provided suggests that if you create membership type A and B associated with different organizations, then the system knows not to change a membership, but to create a new one. That seems like a good idea, but it depends on your own details - the membership model in civicrm has trouble capturing all the possible nuances of memberships in real life.</p>
  <p>Here's a link to one of my recent projects that provides support for multiple memberships:</p>
  <p><a href="https://socius.cpha.ca/civicrm/contribute/transact?reset=1&amp;id=2" rel="nofollow noreferrer">https://socius.cpha.ca/civicrm/contribute/transact?reset=1&amp;id=2</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-12T16:19:35.467Z
Answers.Text: Great example !!! thanks for a elaborate explanation !!!
Answers.UserDisplayName: harshal
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-05T17:20:18.503Z
Answers.LastActivityDate: 2021-02-05T17:20:18.503Z
Answers.UserDisplayName: Alan Dixon
Body: <p>There are two scenarios <br>
  <strong>First</strong><br>
  a. I create contribution page with membership types A, B, C, D and then user goes to the contribution page and purchases membership type A<br>
  b. I again go to the contribution page and this time purchase membership type B<br>
  <strong>Result</strong> --&gt;  Membership Type - B<br>
  i.e. At first my membership type was A but after purchased membership type B, I have Membership Type B<br>
  <strong>Second</strong><br>
  a. I go to contact dashboard , open membership tab and click on + Add Membership --&gt; select membership type A <br><br>
  b. I again to contact dashboard open membership tab and click on + Add membership --&gt; select membership type B <br><br></p>
  <p><strong>Result</strong> --&gt; ** Membership Type A and Membership Type B both<br><br>
  i.e. I have two memberships A and B<br><br>
  I know since all membership type belongs to one organisation , we maybe getting the above issue, is there any chance we can implement scenario second with  contribution pages ?<br><br></p>
  <p>is there any better solution than as provided in the old post here : <br><br><a href="https://forum.civicrm.org/index.php%3Ftopic=31251.0.html" rel="nofollow noreferrer">https://forum.civicrm.org/index.php%3Ftopic=31251.0.html</a> <br><br></p>
  
Tags: <civimember>
Title: How can I allow multiple memberships for a single contact under one organisation?
ThreadText: # How can I allow multiple memberships for a single contact under one organisation?
  
  (Asked by: username_0 on 2021-02-02)
  
  There are two scenarios   
  **First**  
  a. I create contribution page with membership types A, B, C, D and then user goes to the contribution page and purchases membership type A  
  b. I again go to the contribution page and this time purchase membership type B  
  **Result** --> Membership Type - B  
  i.e. At first my membership type was A but after purchased membership type B, I have Membership Type B  
  **Second**  
  a. I go to contact dashboard , open membership tab and click on + Add Membership --> select membership type A   
    
  b. I again to contact dashboard open membership tab and click on + Add membership --> select membership type B
  
  **Result** --> \*\* Membership Type A and Membership Type B both  
    
  i.e. I have two memberships A and B  
    
  I know since all membership type belongs to one organisation , we maybe getting the above issue, is there any chance we can implement scenario second with contribution pages ?
  
  is there any better solution than as provided in the old post here :   
    
  <https://forum.civicrm.org/index.php%3Ftopic=31251.0.html>
  
  **Tags:** civimember
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-02-05. Score: 1
  
  The logic behind the behaviour you're observing is that most of the time when a contact is paying for a different membership type than their existing one, they are upgrading or changing that membership. Whereas an administrator is doing it, they can be trusted to differentiate between an update/change vs. a new one.
  
  The link you provided suggests that if you create membership type A and B associated with different organizations, then the system knows not to change a membership, but to create a new one. That seems like a good idea, but it depends on your own details - the membership model in civicrm has trouble capturing all the possible nuances of memberships in real life.
  
  Here's a link to one of my recent projects that provides support for multiple memberships:
  
  <https://socius.cpha.ca/civicrm/contribute/transact?reset=1&id=2>
  
  > **Comments:**
  > **username_0**: Great example !!! thanks for a elaborate explanation !!!  
  
  ---
  
  