Out-Of-The-Box Zuora Custom Fields

The concept is simple, Limio order processing has built-in logic to detect if a certain custom field is defined in Zuora and in case it is, it will add it to the order (or request) in the corresponding object.

If you don't have the field defined nothing gets added to your Zuora request.

In case you want to use some of this built-in information you just need to:

1. Check in the table below for the custom field name and object it belongs to
2. Add it to your Zuora environment
3. Perform a sync from Zuora Catalog

List of OOTB Custom Fields

Note: you do not need to add the '__c' to the field name as Zuora will add this automatically.

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 cancel, cancel/save and switch 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