> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/billing-and-payments/zuora-integration/custom-field-sync-to-billing-systems-e.g.-zuora.md).

# Custom Field Sync to Billing Systems

### Overview

Our platform now enables seamless syncing of custom field data to billing systems (e.g., Zuora) based on real-time inputs captured during a user Journey.

Admins can configure Content steps with text inputs or dropdown menus, and the information customers provide flows directly into the corresponding Subscription or Order custom fields. The integration leverages the EcommerceAPI to keep records enriched and accurate—no manual updates or developer intervention required.

<figure><img src="/files/3ueOWJYFFzgTRzP2rEuP" alt=""><figcaption></figcaption></figure>

### Business Value

This feature transforms the way businesses capture and manage customer data by bridging the gap between user input and their billing system of record:

* Solve for fragmented data: Directly capture insights like cancellation reasons, preferences, or feedback at the point of interaction.
* Boost operational efficiency: Eliminate manual data entry or the need for hard-coded updates.
* Enrich customer records: Ensure Subscription and Order objects reflect the real story of each customer interaction.
* Drive better outcomes: Cleaner data enables smarter reporting, faster decisions, and more personalized customer experiences.

For prospects, this represents a powerful differentiator: the ability to create meaningful, self-service interactions while ensuring back-end accuracy.

### User Impact

For Customers

* Provide meaningful context during a Journey (e.g., select a cancellation reason or share custom preferences).
* Experience smoother, more personalized engagement since businesses capture their exact inputs.

For Admin Teams

* Configure what fields sync without developer support—text or dropdown fields can be easily mapped.
* Gain control over how customer input updates Subscription and Order records.
* Reduce reliance on IT resources by managing configurations directly in the Journey builder.

For Businesses/Sites

* Strategic advantage: Enriched data enables upsell, retention, and smarter campaign targeting.
* Reduced churn: Collecting accurate cancellation or feedback data helps refine offerings and improve customer satisfaction.
* Faster innovation: Business teams can launch new Journeys without long development cycles.

### Key Functionalities

* Dynamic Field Support
  * Syncs both text inputs and dropdown selections.
* Supported Objects
  * Subscription and Order objects in billing systems (e.g., Zuora).
* Admin Configuration
  * Configure Content steps with inputs and map them to system fields using ecommerceAPI.addCustomField.
* Automatic Sync
  * Upon Journey completion, values are automatically sent to the billing system via APIs (for example in Zuora):
    * PUT /v1/subscriptions/{subscriptionId}/customFields
    * PUT /v1/orders/{orderNumber}/customFields
* Default Behavior
  * If not enabled, Journeys run as normal without syncing inputs to billing records.
* Real-Time Updates
  * Data is captured and reflected immediately, ensuring records are always up to date.

### Why It Matters

Customers today expect personalized, responsive experiences—and businesses need reliable data to deliver on that promise. This feature closes the loop: it captures customer input at the source, enriches billing records instantly, and empowers businesses to act with confidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/integrations/billing-and-payments/zuora-integration/custom-field-sync-to-billing-systems-e.g.-zuora.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.