Recharge

connect your recharge subscription data to chord recharge is the subscription management platform that powers recurring billing, customer portals, and lifecycle events for many subscription brands on shopify chord ingests subscription, order, charge, customer, and product data from recharge so you can model retention, churn, and lifetime value alongside the rest of your stack what chord ingests from recharge chord pulls 12 datasets from your recharge account each dataset becomes its own table in your chord snowflake schema dataset what it contains subscriptions active and historical subscription records frequency, status, line items, next billing date orders subscription driven orders, including cart and shipping details charges individual charge attempts and outcomes successes, failures, retries customers customer profiles linked to subscriptions addresses shipping and billing addresses on customer accounts discounts discount codes and their usage on subscriptions events subscription lifecycle events cancellations, pauses, reactivations, swaps, skipped charges products subscribable products in your catalog collections product collections and their merchandising structure plans selling plans (frequency × price tiers) attached to products one time products one time products purchased alongside subscriptions bundle selections choices made within bundle subscriptions generate a recharge api token you'll need a recharge api token with the seven read scopes listed below the token is created in the recharge merchant admin and pasted into chord hub required scopes chord needs all seven of these read scopes for the connector to pull every dataset cleanly make sure each one is enabled before saving the token scope datasets unlocked read subscriptions subscriptions, one time products, bundle selections read orders orders, charges read customers customers, addresses read discounts discounts read events events read products products, collections read plans plans connect the token in chord troubleshooting token expired or revoked recharge api tokens don't expire automatically, but they can be revoked from the merchant admin if validation suddenly fails on a token that previously worked, check apps & integrations → api tokens in recharge admin to confirm the token is still listed and active if it's been revoked, generate a new one and re paste into hub rotating the token generate a new token in recharge admin, paste it into the same chord credential entry, and save chord uses the new token starting on the next scheduled sync the old token can be deleted from recharge admin once you've confirmed the new one validates successfully need help? if you hit a scope or permission issue you can't resolve, reach out to help\@chord co mailto\ help\@chord co with the exact error message we'll trace the request and tell you which scope is missing