Subscription record requirements
On this page
When a customer buys a subscription through your store, StoreConnect creates a subscription record and fills in every field it needs automatically.
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 - you need to check that the subscription fields are fully complete, otherwise the renewal may fail.
We recommend checking that all subscriptions are configured correctly, to avoid ‘quiet fails’ where the jobs seem to run smoothly, but skip invalid records.
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 — 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. |
| Original Order | s_c__Order_Id__c |
The order the subscription was first created from. StoreConnect uses it as the source for the renewal order’s line items and order context. |
| Term Price | s_c__Period_Price__c |
The amount charged each billing cycle. Without it there is no amount to invoice or charge. |
| 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. |
Fields needed for renewals to run on schedule
The fields above make a subscription valid. These additional fields control when and how it renews. Set them so renewals fall on the right date and for the right term:
| Field | API name | Why it is needed |
|---|---|---|
| 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. |
| 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. |
For the full list of conditions the daily job checks before processing a subscription, see Subscription processing, payments and renewals.
Always configure the product field on the subscription record
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.
Recommendations for checking required fields
| 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.