Subscription record requirements
On this page
When a customer buys a subscription through your store, StoreConnect creates the subscription record and fills in every field it needs automatically. You only need to think about these requirements when a subscription is created outside of checkout, for example when you import or migrate subscriptions from another system, or create one manually in Salesforce. For the whole import process, see Migrate subscriptions from another platform.
A subscription that is missing one of these fields can fail quietly: the daily job either skips it or errors on that one record and moves on to the next, so the rest of your subscriptions keep working and the gap is easy to miss until a customer’s renewal doesn’t happen.
Subscription minimum required fields
Check that these fields are populated for all subscriptions, so they are processed and renewed correctly.
| Field | API name | Why it is needed |
|---|---|---|
| Product | s_c__Product_Id__c |
The product the customer is subscribed to. StoreConnect reads the product to work out the price and tax when it builds each renewal order. If the Product is blank, the renewal order cannot be created, so the subscription is skipped with an error and no order is raised. See the note below. |
| Contact | s_c__Contact_Id__c |
The customer who owns the subscription and is billed for it. Renewal orders and payments are created against this contact. Set it to the same contact as Bill To Contact on the original order: the customer’s account page lists subscriptions through the order’s contact, and opens or updates one through this field. |
| Original Order | s_c__Order_Id__c |
The order the subscription was first created from. Each renewal takes the store, price book, shipping method, and billing and shipping addresses from it. The order also needs an order product linked to this subscription. See Link the subscription to an order product. |
| Term Price | s_c__Period_Price__c |
The amount charged each billing cycle. Without it there is no amount to invoice or charge. |
| Full Price | s_c__Full_Price__c |
The total value of the subscription. For an evergreen subscription, set it to the Term Price. For a fixed-term subscription, it is the total to collect: charging stops once the payments recorded against the subscription reach it. |
| Start Date | s_c__Start_Date__c |
The date the subscription becomes active. The daily job only processes subscriptions whose start date is today or in the past. |
| Term Unit and Term Length | s_c__Period_Type__c, s_c__Period_Length__c |
Together they define the billing interval (for example, every 1 month). They are used to advance the billing date after each renewal. |
| Type | s_c__Type__c |
Whether the subscription is evergreen or fixed-term. This determines how it is charged and when it ends. |
Fields needed for renewals to run on schedule
The fields above make a subscription valid. These additional fields control when it renews and whether it is charged. Set them so renewals fall on the right date and are charged only when there is a card to charge:
| Field | API name | Why it is needed |
|---|---|---|
| Next Renewal Date | s_c__Next_Renewal_Date__c |
The date the current term ends. After each successful payment the job advances it by one term from the previous value, not from today. Set it to the next real renewal date. If you import the original join date instead, every advance leaves it in the past and the subscription is charged again on every run until it catches up. |
| Next Billing Date | s_c__Next_Billing_Date__c |
The next date payment is charged. The job only picks up subscriptions where this is today or in the past. Set it to Next Renewal Date plus any billing delay. |
| Charge Payments and Payment Token | s_c__Charge_Payments__c, s_c__Payment_Token__c |
Check Charge Payments only when the subscription has a token from the payment gateway. With it checked and no token, the gateway declines every charge, the subscription goes delinquent, and it is suspended after the day 8 retry. For customers who pay you outside StoreConnect, leave it unchecked: the job then creates the renewal order and advances the dates without charging. Charge Payments is checked by default, so uncheck it when you import a subscription without a token. A subscription with it checked also needs a Payment Provider, or it fails validation and is never charged. See Subscription processing, payments and renewals. |
For the full list of conditions the daily job checks before processing a subscription, see Subscription processing, payments and renewals.
Link the subscription to an order product
StoreConnect finds each subscription’s line on the original order through the Subscription field (s_c__Subscription_Id__c) on the Order Product. Checkout sets it for you. For an imported or manually created subscription, set Subscription on the original order’s product line to the subscription.
These problems follow when the link is missing:
- An evergreen renewal order is created with no products on it, but the customer is still charged the Term Price.
- A fixed-term subscription never counts as fully paid, because the payments are recorded against the linked order product. It keeps charging until the End Date.
- A payment taken against the original order, in Salesforce or through the order payment link, creates a second subscription instead of updating this one.
Why Product matters even though Salesforce lets you save without it
Product is not a required field at the Salesforce level on a Subscription object — you can save a subscription record with it blank. However, StoreConnect needs the product to be set in order to price and tax a renewal order.
:::warning A Subscription with no Product will not renew.:::
When it becomes due, StoreConnect tries to read the product’s tax rules to build the renewal order, cannot find a product, and skips that subscription with an error. Every other subscription renews as normal, so the problem shows up as one customer’s renewal silently going missing rather than an obvious failure.
This commonly happens after a data import or migration, where subscription records are loaded without their product lookup connected. Before you enable subscription processing on a newly imported set of subscriptions, confirm that Product (and other required fields) are populated on every record.
How to check for subscriptions missing a Product value
- In Salesforce, create a report or list view on the subscription object.
- Add a filter for
Product equals blank. - For each record returned, set the correct product — this is the product the subscription is billing for, which you can match from the original order’s line item.
- Save. The subscriptions will be picked up automatically the next time the daily job runs.
When these fields are set for you
| How the subscription was created | Are these fields set automatically? |
|---|---|
| Customer purchase through your store checkout | Yes — StoreConnect populates all required fields. |
| Imported or migrated from another system | No — manually ensure each field is populated. |
| Created manually in Salesforce | No — you must populate each field yourself. |
For the complete field list, see the Subscription Object Reference.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.