Subscription management for recurring retail orders
Manage subscriptions from a customer change to dispatch. Check subscription billing, payment retries and cancellations against the right order records.
- Published
- Last updated
Subscription management keeps a customer’s recurring agreement, payments and retail orders consistent as their needs change. Staff must check each renewal from the saved instruction to dispatch, especially after a skip, failed payment or cancellation. An active subscription alone does not prove that the latest order is paid or shipped.
How subscription management connects each recurring order
A subscription agreement records what the customer authorises you to supply repeatedly. The billing schedule determines when payment becomes due. A payment attempt records an effort to collect it, while a renewal order records the products to supply. The delivery record shows what actually leaves the warehouse.
These records move at different times. A customer can have an active agreement while a payment fails. A paid renewal can still await stock. A dispatched order remains a real shipment even after the customer cancels future renewals.
Shopify’s subscription contract documentation distinguishes the agreement from the order and describes billing attempts against the contract. Keep that distinction when answering, “Has my subscription gone through?” Find the renewal period, then identify the payment outcome and order before promising delivery.
Set the renewal rules and assign each record
Before a renewal becomes eligible, record the agreed products and variants, quantities, price and cadence. Include the next charge, delivery address, cancellation terms and evidence of customer authorisation. Keep billing frequency separate from delivery frequency when the customer prepays for several shipments.
Give each record an owner so staff know which system to trust when screens disagree.
| Record | Authoritative system | Staff responsibility |
|---|---|---|
| Agreement and requested changes | Subscription system | Support records the authorised instruction and its effective renewal |
| Payment attempt and collected amount | Payment provider | Billing staff resolve declines and reconcile charges |
| Renewal order and stock allocation | Commerce or inventory system | Operations checks the correct items and available stock |
| Dispatch and tracking | Fulfilment system | Warehouse staff confirm the shipment released |
| Conflict between records | Original systems, compared through their references | The operations lead owns resolution and assigns any billing or integration repair |
Give staff permitted access to these records and the retailer’s renewal terms before they handle changes. Write down the billing and warehouse cut-offs, including the time zone. A customer request needs an effective renewal, not just a note saying “address updated”.
If the system cannot carry these records through the process, use the operating requirements to assess subscription management software. Daily administration still needs a named operations lead after installation.
Apply customer changes before the next order
To manage subscriptions online, use the authenticated customer account or staff console for that agreement. A support email establishes the request, but staff must verify the customer’s identity under the store’s account procedure before changing it.
- Open the agreement and identify the next billing event. Check whether a renewal order already exists and whether the warehouse has released it.
- Compare the request with both cut-offs. Record the first renewal the change can affect under the retailer’s terms.
- Apply the permitted control and save. For a skip, confirm the selected cycle is skipped. For a pause, check the pause state and how resumption works.
- For an address change, update the agreement’s delivery address. Inspect an existing order separately. For a quantity change or product swap, confirm the exact variant and resulting renewal total.
- Refresh the page or reopen the record. Check that the saved instruction persists, then inspect the next expected charge and shipment.
- Tell the customer which renewal changes and what happens to any order already created. Record the confirmation with the agreement reference.
A skipped cycle and a paused agreement have different effects. Confirm the next eligible renewal after either action. A product swap also needs the customer’s agreement to its price and any changed delivery conditions.
Shopify’s contract instructions describe a Skipped badge for a skipped upcoming order and separate contract controls for pausing or cancelling. They also describe customer-account controls. Use the equivalent saved status in your system, rather than treating a button click as completion.
Once billing has started, hold the request for billing review if its effect is uncertain. Once an order exists, change that order through the order process. After dispatch, explain the available delivery or return action. For platform-specific setup, use the Shopify subscriptions guide.
Control automated billing and payment retries
Subscription billing collects authorised recurring payments on the agreed schedule. With automated billing, the customer does not place a fresh order and approve payment at every renewal. WooCommerce’s renewal process separates automatic renewals from manual renewals, which require the customer to log in and pay.
Before a retry, billing staff must find the existing attempt and its renewal reference. Check whether a retry is already scheduled. The corrective action depends on the payment result.
| Symptom | Check first | Permitted correction and completion check |
|---|---|---|
| Declined payment | Provider error and configured retry eligibility | For a recoverable decline, allow the scheduled retry after the cause is resolved. Confirm its outcome against the same renewal |
| Expired payment method | The payment method used and the provider’s update requirement | Send the customer to the provider’s secure update surface. Confirm the replacement applies to the agreement, then check the next eligible attempt |
| Interrupted attempt or timeout | Provider transaction status, billing attempt and existing renewal order | Establish whether collection succeeded before retrying. Ask the integration owner to recover a missing order without collecting again |
| Authentication required or hard decline | Exact provider response | Ask the customer to complete the required secure action. Escalate a blocked or unexplained result instead of repeatedly submitting it |
Use the provider’s secure payment-update page when the customer must replace payment details or authenticate. Keep card details out of support messages. After an update, check the agreement’s payment reference and retry schedule before promising recovery.
Recharge’s order-error guide separates automatic recovery from errors requiring manual action. It says hard declines need a payment-method update. Expired-card retry behaviour also depends on the payment integration. A rule that works for one provider is not permission to retry every failure.
Stop manual retries when authorisation is withdrawn, the provider blocks the attempt or the charge outcome remains unresolved. Billing staff must compare the provider’s successful transactions with the renewal record and confirm there is no duplicate charge before releasing the order.
Release stock and dispatch only once
Release a renewal only after its payment outcome and fulfilment instructions satisfy the store’s rules. Compare the saved variant and quantity with stock availability and the order’s allocation. A subscription promises a recurring purchase, but it does not by itself establish a stock reservation.
For an out-of-stock variant, operations must check the store’s shortage policy before processing. The permitted outcome might be waiting for stock, skipping the cycle or obtaining approval for a substitute. Record the customer’s choice and any price difference before releasing changed goods.
Recharge documents inventory-dependent processing and missing-variant errors. Its guide calls for correcting the variant reference before a manual retry. Match the replacement to the customer’s instruction, rather than choosing an available product just to clear an error.
For a paid renewal without a dispatch record, locate the commerce order first. Check warehouse holds and export failures. If the order is missing, the integration owner must reconcile the successful payment with one authorised order creation.
For duplicate-looking orders, compare agreement, renewal period, payment reference and line items. Check whether one order is a replacement or a separate purchase. Hold uncertain shipments for the operations lead. Release one permitted shipment and document what happens to the other order and any duplicate payment.
Cancel the agreement and settle the open order
Cancelling a subscription stops future renewals according to the agreement’s effective cancellation terms. An order already created needs its own decision. A refund requires a payment action, and a dispatched parcel needs the applicable delivery or return process.
Use this sequence for a cancellation request:
- Verify the customer and identify the agreement they want to end. Establish whether cancellation takes effect immediately or after the agreed period.
- Save the permitted cancellation and reopen the record to confirm its state. Inspect the next scheduled attempt, including any failed-payment recovery still awaiting action.
- Find outstanding renewal orders. Apply the retailer’s cancellation terms to each order and obtain billing review where payment has already been collected.
- Check warehouse status before promising to stop a parcel. Record any refund decision against the original payment and its processing status.
- Confirm the effective cancellation, the final order outcome and any remaining customer action. Keep the message with the subscription record.
A useful confirmation says whether another renewal will be collected and whether the current order will ship. If the retailer’s terms leave an existing order payable, explain that obligation separately from future cancellation. Never promise an automatic refund merely because the agreement now shows cancelled.
Give support one source of truth and a clear handover
Give support a view that brings the authoritative records together without replacing them. It must show the current subscription instruction, payment outcome, stock status, renewal-order reference and dispatch event. Include the policy that governs the customer’s request and links back to the original records.
For “Can I swap this product?”, shopping assistance can explain catalogue differences and the store’s substitution policy. Send the customer to the authenticated subscription control for the actual change. When staff must act, carry the requested variant, affected renewal and actions already taken into the handover.
The billing system remains responsible for collecting payments and applying agreement changes. A conversational answer about a pause does not prove the pause was saved. Support must read the resulting record before confirming it.
Keep customer self-service controls connected to staff escalation when a cut-off or failed payment prevents the requested action. Marketing preferences remain separate from subscription authorisation. Unsubscribing from promotional email must not be treated as evidence that a product renewal was cancelled.
Check the renewal process after a correction
Use fictional records to practise the handover and expected final state. The following examples describe intended outcomes, not transactions from a real store.
Successful renewal
A fictional coffee retailer has agreement SUB-41 for two bags every four weeks. The customer changes the delivery address before billing and warehouse cut-offs. Staff save the address against the agreement and confirm it after reopening the record.
At renewal, attempt PAY-41 succeeds. Order ORD-41 contains two bags and the new address. Stock is allocated, and dispatch SHIP-41 records the parcel leaving the warehouse. The customer receives the payment receipt and a dispatch message with tracking. The agreement shows the next renewal four weeks later.
Corrected failed renewal
Agreement SUB-42 reaches renewal, but attempt PAY-42 fails because the saved card has expired. The customer updates it through the secure payment page. Billing staff confirm the new method applies and inspect the configured recovery attempt before taking another action.
The recovery succeeds against the same renewal. Staff confirm one collected payment and one order, ORD-42, then check stock before dispatch. The agreement shows its next scheduled renewal. The customer receives confirmation of the recovered payment and the actual shipment status. A saved card alone would leave the case unresolved.
Assign recurring exception checks to named roles. Billing staff investigate attempts with no final result. Operations follows stock holds and missing orders. Support checks cancelled agreements that still show a scheduled charge and sends the conflict to billing before collection.
Close a case only when the records support the message sent to the customer. Reconcile reporting through recurring revenue after correcting orders and payments, so a scheduled renewal is not mistaken for money collected.
Trace Stripe and Salesforce subscription records
Stripe subscription management needs a billing connection and a separate route to the retail order. Stripe’s subscription lifecycle connects the customer, recurring price, subscription and invoice with payment collection. Store the customer’s authorisation with the agreement and map each billing cycle to its intended shipment.
For a Stripe Billing integration, follow the invoice result and subscription state through subscription webhook events. Handle payment failures and authentication requests before fulfilment. An active subscription can coexist with an outstanding invoice, so inspect the relevant payment record.
The store’s integration must turn an eligible paid renewal into one commerce order. Match its invoice reference to the order and retain that link if event delivery repeats. If payment succeeds but order creation fails, operations must repair the order connection without collecting again. A paid Stripe invoice is not a dispatch record.
For Salesforce, identify the billing product before treating a customer record as a recurring-order operation. Salesforce’s Commerce Subscriptions considerations specify digital subscriptions, excluding physical products. They list Commerce Growth or Advanced with Revenue Cloud Advanced, plus checkout and pricing dependencies. Those licences do not establish a supported physical-product renewal process.
A different documented connection is the Stripe app for Salesforce Platform. It brings Stripe billing objects and events into Salesforce and supports configured subscription workflows through Flow Builder or Apex. Stripe remains the billing authority in this arrangement. Salesforce can hold customer and service records, while the commerce system owns the retail order and dispatch.
The administrator must establish edition and API access compatibility for the chosen app and flows. Stripe’s installation instructions require Lightning Web Security, account authorisation and the API extension. Staff also need permissions for the records and actions assigned to them.
Before enabling collection, prove the configured connection in a test environment. Follow a renewal through the agreement, Stripe payment, Salesforce record and commerce order. Include a failed payment and a repeated event. Require one permitted charge and shipment, with a service record that identifies whoever must repair a failed handover.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.