Editing a PayRequest product does not automatically update existing subscriptions. Each subscription keeps the price and custom field configuration captured when it was created. To apply later custom field changes, review Sync with Product on one subscription and select the differences deliberately.
The important risk is removal: applying a “Removed from Product” change deletes that field's current value from the subscription. This guide is for service and membership operators changing a product configuration while preserving useful customer information.
Treat the product and subscription as separate records
The PayRequest Sync Product Changes documentation distinguishes a product's current configuration from the subscription's saved configuration. Changing the product affects new subscriptions; existing records need an explicit action.
On the subscription detail page, Sync with Product reports In Sync or Out of Sync. Sync Fields, or Check for Updates when already in sync, opens the differences. The tool works on that subscription only. There is no bulk version of custom field sync.
An “Out of Sync” label is a difference to inspect, not proof of an error. An older customer's configuration may intentionally reflect a different service agreement.
Review three kinds of field change
PayRequest labels differences New Field, Modified, and Removed from Product. New and modified differences are selected by default; removals are not. Default selection is a starting point for review, not a decision that every change suits this customer.
Here is an original review matrix for a fictional support subscription. The example values are illustrative, not records from a customer account.
| Product change | Existing subscription | Review decision |
|---|---|---|
| Add “Service region” | Field is absent | Decide whether this customer needs the new field and what information is still missing |
| Modify “Service reference” configuration | Customer has reference AC-042 | Inspect the displayed difference and saved value before applying it |
| Remove “Legacy account code” | Customer has code LEG-17 | Keep it unchecked until the code's continued use and preservation have been reviewed |
Adding a field configuration does not establish the correct customer answer. A product default is not evidence of the customer's region. For a modified field, do not assume either preservation or deletion of its value without checking the actual change and saved result; the published guide does not promise one universal outcome for every modification.
Prepare a small change record before syncing
Record the subscription ID, product, field label, current configuration and current value where needed. Limit the record to information required for the change and keep it in an appropriate internal location. This is your own review log, not an additional PayRequest export feature.
For a removal, ask whether the value is used in a support workflow, invoice reference or another system. A field no longer needed for new customers may still identify an existing account. Preserve necessary information appropriately before approving deletion; do not keep personal information without a purpose.
Assign one operator and one intended subscription. If several subscriptions use the product, list the ones that need the change separately. Syncing the first is not evidence that the others changed.
Apply only the reviewed differences
Open the subscription, inspect the sync modal and uncheck new or modified fields you have not approved. Check a removal only when its deletion is intended. The documentation says the modal warns about the current value before a removed field is applied.
Confirm the selected fields, reopen the subscription and compare the result with the change record. Check field configuration and any relevant value, not just the status badge. If a field is missing unexpectedly, inspect what was selected before repeating the operation; do not promise an automatic undo.
Useful closeout notes are: “subscription reviewed; selected differences applied; saved result checked; other subscriptions unchanged or awaiting review.” They distinguish a completed change from a batch still in progress.
Keep price changes on a separate path
Custom field sync is not the tool for changing the recurring amount. The same documentation points to Bulk Price Adjustments for intentional changes to existing subscription prices. Review that workflow separately rather than assuming a field update changes an agreed amount or sends a customer notice.
For the underlying configuration, see PayRequest Custom Fields. To review an existing customer record, start with Subscriptions. Choose one subscription, one meaningful difference and one verified saved result before expanding the work.
Editorial note: AI assisted with this article and cover. Published documentation was checked on 6 October 2026. The field matrix and review log are original planning artifacts, not an account test or guarantee of data recovery.
