Recommended Custom Fields in Zuora

Limio recommends to implement in Zuora a set of custom fields that will automatically be populated by Limio orders. These custom fields allow Limio to pass additional information - such as metadata about the offer, customer, or context - without any manual mapping or configuration.

Limio order processing includes built-in logic to check if specific custom fields are defined in your Zuora tenant. If a supported custom field is present, Limio will automatically include it in the relevant object in the order or request payload sent to Zuora. If a field is not defined in Zuora, it will not be included in the order payload. This ensures that only valid custom fields are passed during processing.

This is different from configuring your own custom fields in Zuora and getting Limio to map to them. For this, go to 👉

How to use the built-in custom field logic

To use one of the built-in custom fields in your Limio orders:

  1. Check the table below to identify which custom field you want to use and the Zuora object it belongs to.

  2. Create the field in your Zuora environment with the specified name (excluding the __c suffix).

  3. Perform a Zuora Catalog sync in Limio to ensure the custom field becomes available.

⚠️ Important: Do not include the __c suffix in the custom field name when creating it in Zuora. This is appended automatically by Zuora when storing custom fields.

Zuora Object (where the custom field needs to be defined)

Custom Field Name (Zuora custom field name)

Limio path

Description

Subscription

CancellationReason__c

data.reason.id

If defined in Zuora on Subscription Fields, this field will be populated via the , and journeys if any cancel survey, reasons or switch component is used.

Debit Memo

GiftCode_c

If defined in Zuora on Debit Memo Fields, when a gift is purchased (by they buyer), the gift code will be populated on the debit memo created.

Order

Source__c

order.initiated_source

This defines where the checkout was initiated. If it was done so via Limio for Salesforce, the value would be salesforce if it were the Limio shop flow the value would be shop.

Order

InitiatedSource__c

order.source

This defines where the event was processed. If it was done so via Limio for Salesforce, the value would be salesforce if it were the Limio shop flow the value would be shop.

Offer

lmo_offer__c

order.offer.path

From Release v97.0+ If defined in Zuora, this field will be populated with the url path of the limio offer

Last updated

Was this helpful?