Question 1

What Chargebee data can Polytomic sync?

Accepted Answer

A wide set. Customers, subscriptions, invoices, credit notes, and transactions form the core, alongside quotes, orders, coupons, gifts, promotional credits, unbilled charges, hosted pages, payment sources, virtual bank accounts, currencies, events, and comments. Subscription entitlements and usages come through as child objects. Which catalog objects appear depends on your Product Catalog version: 1.0 sites get plans and addons, while 2.0 sites get items, item families, item prices, differential prices, and features. Configured custom fields are included on the entities that support them.

Question 2

How does incremental syncing work?

Accepted Answer

Most primary objects filter on updated time, requesting records changed since the last cursor up to the current moment, and the cursor advances with a deliberate five minute overlap that Chargebee itself recommends. That small amount of rereading is insurance against records changing right at the boundary. The very first read deliberately omits the updated time bound entirely, so older records that predate Chargebee's updated timestamp support are not silently missed. Events are the exception and filter on occurrence time instead.

Question 3

Can I sync usage data for metered billing?

Accepted Answer

Yes, though it works differently from the other objects. Usages are fetched per subscription rather than as one collection, so Polytomic enumerates subscriptions and then requests usage for each, which makes it noticeably more request heavy than its row count suggests. Usages are also read in full on each ETL run rather than incrementally, as are the other parent and child objects. If you have a large metered book, factor that into your schedule and consider syncing usage less frequently than the core billing objects.

Question 4

Does this work with both Chargebee catalog versions?

Accepted Answer

Yes, and the connector adapts to yours. Product Catalog 1.0 sites see plans, addons, business entities, and entity transfers. Product Catalog 2.0 sites see items, item families, item prices, differential prices, features, entitlements, attached items, and subscription discounts. Customers, subscriptions, invoices, credit notes, transactions, payment sources, usages, and quotes work on both. Some fields on subscriptions and coupons are filtered by version too, because Chargebee represents them differently between the two.

Question 5

Can Polytomic write back into Chargebee?

Accepted Answer

No, Chargebee is a source only connector, so ETL out of it is supported but writes into it are not. In practice the outbound direction is where the value is: getting billing data somewhere it can be joined to product usage and CRM records. From there the same platform runs reverse ETL, so a subscription status, plan tier, or overdue invoice flag computed from Chargebee data can be written onto a Salesforce account or into a lifecycle marketing tool without a second vendor.

Chargebee

Perfect pairings

Incremental across the board

Product Catalog 1.0 and 2.0

Custom fields included

Example workflows

What you can sync

From Chargebee

To Chargebee

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Chargebee in minutes

More integrations beyond Chargebee