A selling plan is the offer. A contract is the agreement.
The selling plan describes the purchase option a customer chooses, such as a delivery interval and a subscription price adjustment. The subscription contract records the ongoing arrangement after checkout. Keeping these concepts separate helps a team understand why editing a product offer is not the same as editing an existing subscriber’s agreement.
For a launch, write down the product, variant, quantity, delivery interval, price, and customer choices. Then test how those details appear on the product page, at checkout, and in the customer account. If the team cannot explain the next charge in a sentence, the offer probably needs another pass.
Choose the experience before choosing the feature list.
Begin with the jobs your customers need to complete: see the next delivery, understand the price, update payment details, and ask for help. Then list what the merchant team needs: find a contract, understand its state, handle a customer request, and see whether a renewal completed.
Use an actual scenario when evaluating an app. A customer has two subscriptions, wants to pause only one, and has a payment update pending. Ask the provider to show what happens in the account, in the admin, and on the next renewal. A demo that works only for one simple subscription leaves important questions open.
- Can a customer identify the exact subscription they want to change?
- Which changes are self-service and which need support?
- What happens after a payment fails or a scheduled job is missed?
- How does the team verify a change actually completed?
Treat migration as its own project.
Existing subscriptions belong to a specific app and payment setup. A CSV can help map records, but it does not prove that a new app can charge the same payment method or take ownership of the same contract. Inventory the current platform, products, customer identifiers, next billing dates, and payment method constraints before setting a launch date.
Reconcile a small staged set before moving the whole program. Check counts, amounts, dates, and customer access. Decide which system is responsible for each renewal during the transition so that the same subscription is not charged twice.
Where Lasso fits.
Lasso is bringing a Shopify subscription app together with customer conversations. The unified experience is in early access. We review the workflows your store needs before confirming a launch; automated migration and every customer-facing action should not be assumed available.
Put the idea to work in Shopify.
Lasso brings selling plans, subscriber management, and payment history into your Shopify workflow. Explore the subscription app to see how these ideas fit your products, then talk with us about an early-access setup.
Common questions
Does a Shopify product become a subscription automatically?
No. A subscription offer uses a selling plan. When a customer purchases through that plan, Shopify creates a subscription contract.
Will installing another app transfer my contracts?
No. Existing contracts and payment arrangements need a specific migration review. Installing an app or importing a list is not proof of a completed transfer.