Selling memberships with physical products: set the rules before checkout

AI-generated conceptual illustration: physical products and paid media can share an offer while retaining distinct shipping and access rules.

On the product page, a membership with a welcome kit is easy to explain: pay, receive a parcel and open the content library. The harder questions arrive later. A customer returns the kit, changes their address or cancels while waiting for a shipment. A renewal payment fails, but there is still an order to send.

Decide what happens in those cases before configuring checkout. Billing, shipping and content access need records you can connect, but canceling one doesn't necessarily cancel the others.

A kit refund might leave separately purchased video access unchanged. Someone who cancels their renewal may still be owed a shipment. Put those rules in writing for support. "Look after the member" gives them very little to work with when the answer involves both a refund and a parcel.

Give each purchase its own record

A welcome product ships once; a product subscription ships on an agreed schedule. Neither tells you how long membership access should last. That period belongs in the membership offer, while a separately purchased download needs its own access or license terms.

Name each component and give support a record they can find. A "member" field alone won't tell them whether someone is owed a kit, another month of access or a download.

Shopify's subscription setup documentation distinguishes subscription-only products from products available by subscription or one-time purchase. It also directs merchants to configure their subscription app and add a cancellation policy. Those choices are a starting point. You still need to check how the app handles the physical and digital benefits you plan to sell together.

Work through a craft membership example

Suppose a craft publisher sells a monthly video membership. With their first purchase, customers can buy a separately priced welcome kit and add optional pattern downloads. The kit ships once, not every month. This is an invented offer, and the table contains proposed rules for that example. Have them reviewed for your markets before using them.

Benefit: Video membership

What renews or ships?: Monthly access renews; nothing ships

Access or delivery timing: Begins after confirmed payment; ends at the paid-through date after ordinary cancellation

Exception to decide: Failed payment follows an explicitly defined grace policy

Proposed owner: Membership operations

Benefit: Welcome kit

What renews or ships?: One separate purchase; one shipment

Access or delivery timing: Dispatch after payment and address validation

Exception to decide: Stockout triggers a revised date or an agreed remedy, not silent substitution

Proposed owner: Fulfillment lead

Benefit: Optional pattern download

What renews or ships?: Separate one-time purchase; no shipment

Access or delivery timing: Delivery after its payment is confirmed

Exception to decide: Return or refund treatment follows the separate purchase terms

Proposed owner: Customer support

Benefit: Replacement for damaged kit

What renews or ships?: No subscription renewal and no duplicate sale

Access or delivery timing: Support authorizes replacement under the published policy

Exception to decide: Keep the original order linked to the replacement

Proposed owner: Customer support and fulfillment

View full-size image

Under these proposed rules, ordinary cancellation stops future membership charges. It leaves an outstanding kit order in place. Likewise, returning the separately purchased kit doesn't cancel the separately priced membership, and a pattern purchase keeps its own terms. Customers need to see these distinctions before buying, and the terms need review for the markets you serve.

Charging one bundled price makes partial returns harder. You need to agree how much to refund and whether access changes. Calling the welcome item free on the sales page doesn't remove its cost. Finance, support and whoever is responsible for consumer terms should settle that together.

Check what happens after checkout

Take a buyer in this hypothetical offer who purchases monthly access, a kit and a pattern. Their confirmation needs to distinguish the recurring charge from the one-time purchases. Include the expected dispatch window and links or instructions for finding the videos and download. Read it as the buyer: can you get to what you paid for, or does it just tell you how much you spent?

After confirmed payment, verify each result separately. The buyer should have membership access, fulfillment should have the kit order and a usable address, and the pattern should reach the buyer through its own delivery process. One successful checkout is not proof that all of that happened.

Record the shipment against the kit order when it leaves. A shipping update must not renew the membership. If the carrier reports a problem, support should be able to distinguish a parcel issue from a login issue, and check for both before deciding what to do.

The next successful monthly renewal should extend video access without sending another welcome kit. Test this carefully if the configuration copies line items or benefits into renewal orders.

If the buyer returns the kit, support should follow the reviewed return policy and record the refund against the kit. Check that membership access hasn't changed by accident. If the buyer also asks to cancel the membership, record that request separately and confirm when access ends.

View full-size image

For an ordinary cancellation during a paid month, the confirmation should give the final access date. Support must also check any remaining kit obligation and the separate pattern purchase against their own terms. Put the rules beside the relevant order and membership actions in the support instructions so nobody has to reconstruct the policy mid-ticket.

Test the exceptions before customers find them

Run these cases with a test account and test orders. For each one, record what should happen, what happened and who will fix any mismatch:

• A successful purchase creates the right access and the right number of shipments.

• A successful renewal extends access without resending a one-time welcome product.

• An address change applies to the intended unshipped order, without rewriting the history of a shipped one.

• A stockout gives support an approved customer message and remedy.

• A damaged-product replacement does not create a second membership charge.

• A partial refund changes only the intended financial and access records.

• A failed renewal follows the documented payment and access policy.

• A cancellation stops the intended future charges and explains remaining access and deliveries.

• A cancellation followed by rejoining does not accidentally award a second first-purchase kit.

Ask a qualified adviser to review shipping geography, duties, tax treatment, cancellation and digital-content rights for the jurisdictions you serve. Another store's policy may not cover your combination of benefits. Once the wording is approved, check that the implementation does what it says.

Stackmodo's commerce page describes a tailored setup for products, orders and content. Whether you choose that approach or separate tools, include the rules matrix in the implementation brief. For each rule, establish whether the software handles it, someone needs to configure it or a colleague has to do it manually.

If your specialist commerce software already handles the warehouse and returns work well, adding member benefits may not justify replacing it. It is also worth questioning the membership itself: customers who only need instructions for a product they bought may be better served by including those instructions with the purchase.

Before launch, hand a support colleague the checkout confirmation and a returned-kit scenario. Can they work out the refund, any shipment still owed and the customer's access status without asking the founder? If they need help, fix the rules or the instructions before adding more benefits.