If a subscription ships more frequently than it is charged, it is considered a prepaid subscription. Prepaid subscriptions require more attention to detail when migrating to ensure the subscriptions are configured correctly.

Pay special attention to the following columns for prepaid subscriptions when creating your migration template.

charge_interval_frequency and shipping_interval_frequency

The charge_interval_frequency should be greater than the shipping_interval_frequency.

For example, if you have a six-month prepaid subscription and the customer receives a shipment every month, set the charge_interval_frequency to six while shipping_interval_frequency would be set to one. This ensures customers are charged every six months, but receive their shipments every month.

last_charge_date

The last_success_charge represents the date the customer’s current prepaid subscription cycle started. The Recharge system uses this date and the frequencies to determine the number of $0 shipment orders remaining and when shipments will be sent.

If customers are charged on a specific day of the month, you will need to ensure the day on your last_success_charge matches the charge on day of month parameter. If you have a cutoff day, you may need to edit the month to coincide with the cutoff shipment.

number_charges_until_expiration

If you have gift prepaid subscriptions that should expire after the cycle ends, add the number_charges_until_expiration column to the template and enter a 1 for the affected rows. The last_success_charge is used as the one charge and Recharge will not renew the subscription after the prepaid cycle.