If a subscription ships more frequently than charged, then this is considered a prepaid subscription. This means that when you are preparing your CSV for migrations, the charge_interval_frequency listed is greater than your shipping_interval_frequency.
Prepaid subscriptions take a little more attention to detail when importing as fixing issues with prepaid data is more complicated than bulk updating upcoming charges. This guide provides details on how to handle importing prepaid subscriptions to help mitigate any issues.
Understand prepaid subscription data
To import prepaid subscriptions you will need three pieces of data: charge_interval_frequency, shipping_interval_frequency, and last_charge_date.
The charge_interval_frequency should be greater than your shipping_interval_frequency. For example, if you have a 6 month prepaid and the customer receives a shipment every month than the charge_interval_frequency would be 6 and the shipping_interval_frequency would be 1. This will ensure customers are charged every 6 months, but receive shipment every month.
The shipping_interval_frequency should be lesser than your shipping_interval_frequency. For example, if you have a 6 month prepaid and the customer receives a shipment every month then the shipping_interval_frequency would be 1 and the charge_interval_frequency would be 6. This will ensure customers are charged every 6 months, but receive shipment every month.
The last_charge_date is the date the customer's current prepaid cycle started. Our system will use this date and the frequencies to figure out how many $0 shipment orders remain and when the shipment orders should be sent out.
If you charge customers on a specific day of the month then you need to be sure the day on your last_charge_date matches your charge on day of month. If you have a cutoff day then you may need to edit the month to coincide with the cutoff shipment.