How to create a subscription management form for existing customers

Manage subscriptions in one place for your existing customers

In this guide, you’ll create a self-service subscription management portal where existing customers can:

• Log in securely
• See their current subscription details
• Request changes (upgrade, downgrade, pause, cancel, update billing cycle or add-ons)
• Update their own profile information

Behind the scenes, your team can still control what’s editable, track status, and receive notifications when something changes.

📘 Learn more: Create your first form, app, or portal in a flash

Why this helps

• Fewer support tickets – Customers can update subscriptions themselves instead of emailing your team for every minor change.
• Always up-to-date customer data – Profile and subscription details stay current because customers manage their own records.
• Clear status and history – Your team sees a full record of changes per customer, including requested plan changes and cancellations.
• Scalable for growing teams – Add new plans, fields, or pages to the portal as your product or pricing evolves.
• Perfect for SaaS, memberships, or subscriptions – Works well for productized services, online courses, memberships, and recurring billing businesses.

📘 Learn more: Build personalized and time-saving flows with logic, automations, and AI

Step 1 – Create your subscription management form

You can start from scratch or use a template from our Template Gallery (for example, Membership form) and adjust it to your plans and policies.

From your workspace:

Click + New → Form (or create it inside an app that you’ll later turn into a portal).

Add key fields for existing customers, such as:

• Customer identifier fields
  • customer email (Email field – required)
  • customer ID (Short text)
• Current subscription snapshot (often admin-only or read-only in table view)
  • current plan (Dropdown: Basic, Pro, Enterprise, etc.)
  • billing cycle (Dropdown: Monthly, Quarterly, Annual)
  • next renewal date (Date)
• Change request section (customer-facing)
  • requested action (Dropdown: Upgrade, Downgrade, Pause, Cancel, Change billing cycle, Update add-ons, Update address only…)
  • new desired plan (Dropdown, shown only when relevant via logic)
  • new billing cycle (Dropdown, monthly/annual, etc.)
  • add-ons to enable/disable (Multi-choice)
  • notes for your team (Long text)
• Admin-only workflow fields (you’ll mainly use these in the portal table view)
  • internal status (Dropdown: New, In review, Approved, Applied, Rejected)
  • assigned owner (Short text or user lookup field)
  • internal notes (Long text)

💡 Tip: Try Magic Create with a prompt like: “Subscription management form for existing customers, including plan changes, billing cycle updates, and cancellation requests, plus admin-only status fields.”

📘 Learn more: Form editor and field types

Step 2 – Turn your project into a subscription portal

Now you’ll wrap that form (and related views) inside a portal so customers can log in and manage their subscription.

1. Create an app/portal in your workspace, or open an existing app where your form lives.
2. Enable portal mode and configure who can log in (customers via email/password).
3. Add a page like “My subscription” and embed:
   • The subscription management form (for new requests)
   • A table view of subscription records filtered by “logged-in user” (after you set this up in a later step)

Use portal settings to:

• Restrict pages to logged-in users only
• Prepare separate internal pages for your team (e.g., “All subscription changes”)

📘 Learn more: How to create a portal and manage users’ access

Step 3 – Configure the user base so existing customers manage their profile

Your portal includes a user base form that stores each user’s profile (name, email, password, plus your extra fields). For subscription management, it’s useful to store customer-related data there too (company, default plan, etc.).

In your portal:

1. Open the portal and click Edit mode at the top.
2. Click Users → Edit base to open the user base form.
3. Add helpful profile fields, for example:
   • company / organization
   • phone number
   • default subscription plan
   • customer segment (e.g., Starter, Growth, Enterprise)

Customers will be able to click their profile avatar → Edit profile and update these fields after logging in.

💡 Tip: Keep login/signup simple (name, email, password) and capture deeper data inside the profile and subscription forms after users log in.

📘 Learn more: How to add and edit fields in the user base form of your portal

Step 4 – Let customers view and edit their own subscription data

Now you’ll configure the portal so each customer can see and, if you want, edit only their own subscription records.

1. Open your portal app → Edit mode.
2. Go to the Responses page or a page where you’ve added a table block linked to your subscription form.
3. Open the Options of that table.
4. Enable one or both:
   • Allow users to view user data – customers can view their own submissions (e.g., past subscription change requests).
   • Allow users to edit user data – customers can open and update existing records (for example, to correct an address or change an add-on).

Use this combination strategically:

• View-only table for history of changes.
• Editable table or edit form for “active subscription details” that customers can adjust (like address or add-ons).

💡 Tip: If you allow editing, pair it with “On Update” logic (next step) so your team gets notified whenever a record is changed.

📘 Learn more: How to let users view and edit their own data in your portal

Step 5 – Use Memory Forms to auto-fill existing customer details

To make the experience faster for return customers, you can use Memory Forms so fields auto-fill from prior submissions or profile data.

Ideal fields to auto-fill:

• customer email
• customer ID
• current plan
• billing address
• preferred billing cycle

Basic flow:

1. Convert your subscription form into a Memory Form or link it to one.
2. Configure which fields should remember and re-use a customer’s last saved answers.
3. When they log back in and open the form again, those fields will be pre-filled automatically.

This reduces friction and ensures consistency across multiple requests (e.g., no typos in email or ID).

💡 Tip: Use Memory Forms when customers frequently submit forms over time (like upgrade/downgrade requests), but keep “one-time” fields (like a specific change note) non-memory.

📘 Learn more: How to create a Memory Form that auto-fills user details

Step 6 – Add logic and notifications for subscription changes

Now you’ll connect the pieces: when a customer requests a change, logic and emails make sure it reaches the right people and updates status cleanly.

6.1 Add conditional logic on the form

In your subscription management form:

1. Go to Settings → Logic.
2. Add conditional logic such as:
   • If requested action = Upgrade → show new desired plan.
   • If requested action = Cancel → show cancellation reason.
   • If requested action = Change billing cycle → show new billing cycle.

You can also set default values for internal fields, for example:

• On submit, set internal status = New.

📘 Learn more: How to add basic conditional logic

6.2 Use “On Update” logic for portal edits

When customers edit their existing subscription record via the portal, you can trigger On Update logic to:

• Change internal status (e.g., from Active to “Change requested”)
• Send a notification to your billing or success team
• Log the date of last change

In Logic → On Update:

• Add actions like:
  • IF any subscription-related field is changed → set internal status = Change requested.
  • Then trigger an email workflow (see next step).

📘 Learn more: What is “On Update” logic and how it works

6.3 Send email notifications to your team and customers

Set up email notifications so nobody misses important subscription changes.

Common patterns:

• Internal notification:
  • When internal status = New or Change requested → email your billing or customer success team.
• Customer confirmation:
  • When the form is submitted → send a confirmation email summarizing requested changes.

In your form’s Notifications:

• Enable standard notifications to admin emails (for all submissions), or
• Use conditional email notifications to route different actions to different inboxes (e.g., cancellations to Retention, upgrades to Sales).

💡 Tip: Use dynamic fields like @field_ID merge tags in your email templates to pull in plan name, requested action, and effective date.

📘 Learn more: How to send and receive conditional email notifications

Step 7 – Brand and structure your subscription portal pages

Make the experience feel like a native customer account area.

Ideas for portal pages:

• My subscription
  • Embedded subscription form (for new requests)
  • Table listing “Active subscription details”
• Change history
  • Table of past change requests filtered by logged-in user
• Billing & account
  • Link or instructions for updating payments (e.g., via your billing provider)
  • Additional profile fields they can update

To polish the experience:

• Add your logo and brand colors.
• Group content with headings, blocks, and lists.
• Give pages clear titles like “Manage subscription”, not just “Form 01”.

💡 Tip: Use different layouts (tables, galleries, kanban) for internal views where your team tracks approvals or pending changes, but keep the customer-facing pages focused and simple.

📘 Learn more: Customize your form/app layout and design

Pro tips for advanced subscription management

💡 Pro Tip 1 – Use charts to monitor plan shifts over time
Create a dashboard page in the same portal with charts grouped by: current plan, requested action type, cancellations by reason, or upgrades per month. This gives your team quick insight into subscription trends.

📘 Learn more: How to showcase charts based on form responses

💡 Pro Tip 2 – Auto-fill customer details across multiple forms with Memory Forms
If you use separate forms for profile updates, subscription changes, and feedback, connect them all with Memory Forms so customers don’t have to retype basic details every time they interact with your portal.

📘 Learn more: What are Memory Forms

💡 Pro Tip 3 – Connect your subscription form to external tools
If your subscription operations live partly in other systems (e.g., a CRM or billing backend), connect the subscription form responses to Google Sheets or other tools, then sync onward from there.

📘 Learn more: How to connect forms with automatic data transfer

Real-world example (case study)

A B2B SaaS company was handling subscription changes through scattered email threads:

• Customers emailed support to upgrade, downgrade, or cancel.
• Support forwarded messages to billing.
• Updates sometimes took days or got lost.

They built a subscription management portal in Formaloo:

• Customers log in to a “My subscription” page.
• A Memory Form pre-fills their details and current plan.
• Customers select “Upgrade”, “Change billing cycle”, or “Cancel”, and add a note.
• On submit, On Update logic flags the record as “Change requested” and emails the billing team.
• A history table in the portal shows each customer all past changes.

Result:

• Support tickets about “What’s my plan?” and “Can you change X?” dropped significantly.
• Billing always had a structured, timestamped request with all necessary data.
• Customers felt more in control of their subscriptions and less dependent on email exchanges.

📈 See more examples: Formaloo use cases

FAQ –

1. Do I need separate forms for profile updates and subscription changes?

Not necessarily. For many teams, one main subscription management form plus the portal’s user base profile form is enough. Use the user base for core identity data (name, email, company) and your main form for subscription-specific fields and change requests.

❓ Learn more: How to add and edit fields in the user base form of your portal

2. Can customers change their subscription more than once?

Yes. Customers can submit multiple requests and/or edit existing records if you enable editing in the table settings. Each submission will be stored as a record that you can track with statuses, dates, and notes.

🔒 Learn more: How to view your form responses

3. How do I prevent customers from seeing other customers’ data?

Your portal uses user-based permissions. When you enable “Allow users to view/edit user data,” Formaloo automatically restricts access so each logged-in user only sees their own submissions in the table or list views.

🛠️ Learn more: How to create a portal and manage users’ access

4. Can I include subscription payments inside the same portal?

Yes. You can add a payment-enabled field to your subscription form (e.g., for upgrades or plan renewals) and connect it to a payment method like Stripe. Just make sure your payment settings and pricing logic are fully configured before going live.

🧾 Learn more: How to create a subscription-based payment on your form

5. How do I share this portal with only my existing customers?

You can:

• Restrict page access to logged-in users only, and
• Invite or import customers into your portal so they receive login links or can sign up with their email.

From there, share only the portal URL and keep individual forms unlisted if you want customers to always go through the portal.

🌐 Learn more: Share your form or app with your team or audience

Launch your subscription management portal with confidence

You now have a self-service subscription portal where customers can log in, review their details, request changes, and keep their account up to date—while your team stays in control through status fields, logic, and notifications.

From here, you can:

• Add dashboards to track churn, upgrades, and most requested plans.
• Introduce additional forms (support requests, feedback, NPS) into the same portal.
• Connect your flows to CRMs, billing tools, or analytics for a complete subscription lifecycle.

🎉 Learn more: Customize your form/app layout and design

Last updated November 2025