Billing Integration Cache
Settings → Billing Integration Cache shows the data PeakCommerce caches from your billing provider so the storefront, journeys, and admin screens stay fast and resilient even when the upstream provider (for example Zuora) is slow or briefly unreachable. Rather than calling the provider on every plan lookup or price resolve, PeakCommerce serves catalog and pricing data from this cache and refreshes it in the background.
Why it matters
Every product, rate plan, and charge a buyer sees is resolved through this cache. A healthy cache means low latency and no hard dependency on the provider being up at checkout time. A degraded cache (slow resolves, rising failures) is an early warning that something upstream is off.
What it shows
Hit ratio and cache size — how often resolves are served from cache versus going upstream, and how many entries are currently cached.
Resolve latency — average time to resolve, split by cache hit versus miss.
Slowest integrations — per-integration probe latency and failure rate, to pinpoint which provider connection is degraded.
Alerts and thresholds — configurable latency/failure thresholds that surface an alert when an integration crosses them.
How to use it
Refresh when you've just changed configuration upstream (new products, edited rate plans, price changes) and want PeakCommerce to pick it up immediately instead of waiting for the next background refresh.
Watch the hit ratio and slowest-integration latency after a provider change or incident to confirm the cache recovered.
Gotchas
A refresh pulls the latest into cache, but a full catalog reconciliation (adding/deactivating products) flows through catalog sync — see the pages below if products look stale after a refresh.
Related
Catalog Drift — nightly checks that re-sync when local and upstream diverge.
Catalog Sync History — log of catalog sync runs.
Last updated
Was this helpful?