Surface Organization Field as Part of Checkout

🔍 Problem Statement

As an Pelcro user, organizations cannot self identify as an organization in checkout, which results in unnecessary labor for me and confusion for my customers.

💡 User Story

• As a Pelcro user, I want the organization system to be self serve, so that my clients are able to correctly purchase and establish organizations for themselves.

• As a membership owner buying a multi-seat plan, I want to enter my organization name at checkout, so that my membership is tied to that organization.

• As a publisher admin, I want members added to a membership linked to the owner's organization, so that support can find any seat by organization.

• As a publisher admin, I want to require the organization field on membership plans, so that institutional purchases never land without one.

🎯 Definition of Done (DoD)

A feature is done when:

✔ Given a membership plan with organization capture enabled, when a customer chooses a multi-user plan, then a mandatory free-text organization input is shown at checkout.

✔ Given a membership plan is purchased by an organization owner, then the membership is registered as an organization and the purchaser is the organization's owner.

✔ Given an organization name is submitted, when the membership subscription is created, then a new organization record is created and linked to the owner and membership.

✔ Given the purchaser already has an organization on their profile, when the membership is created, then their profile organization is kept (only filled in when empty), and the new organization is still linked to the membership with the purchaser as owner.

✔ Given a member accepts an invite to that membership, when their seat activates, then the member is linked to the membership's organization.

✔ Given the member already has an organization on their profile, when their seat activates, then their profile organization is kept (only filled in when empty), and they are still linked to the membership's organization.

✔ Given an organization owner or member is logged in, when the customer views their subscription, then their current organization is displayed and named as part of their subscription.

✔ Given the organization input is shown, when the customer types, then no existing organization names are suggested or shown.

✔ Given the organization input is shown, when the customer types, Pelcro does not check the organization name against existing organizations or indicate that a matching organization already exists.

✔ Given the organization input is shown, when the customer types in an organization that already exists, Pelcro creates a new separated organization. Organization names are not unique; the organization record is the identifier.