Version 2 for Commerce recurring framework is a module that closely resembles a "feature" and heavily relies on Fields & Rules for all the processes.

Structure

The module provides a new product type for basic recurring usage, but virtually any product type could be recurring.

Five fields are provided in the default product type.

• Initial price - Sets the initial price of the product, this might be used to do trial periods. (Commerce price).
• Initial period - Period or offset of after which the recurring price and period will be effective. (Interval field).
• Recurring price - Price used for recurring the product. (Commerce price).
• Recurring period - Periodicity to apply the recurring price. (Interval field)
• End period - Period after wich end the recurring. (Interval field)

A new Recurring entity is provided with these fields and properties

• Id.
• User assigned to the recurring process.
• Bundle (Product / Order).
• Recurring reference - Entity reference field to the bundle (product or order).
• Status property.
• Price at the moment of creation.
• Start date (Created date). Date property.
• Due date. Calculation is based on start date + initial/recurring date.
• End date (optional), it might be empty or created date + expiration period, or a given timestamp on cancelling the recurring. Date property.
• Order reference (multiple), to all the orders associated with the recurring process, being 0 the initial one.

Recurring process

When an order containing a Recurring product is purchased for the first time for the current user, by default the module reacts on "Order is paid in full" event, a Recurring entity will be created associated with that product for the current order.

On a cron event, the recurring entities with past due dates are retrieved and an order is created for each recurring entity associated with the recurring product and customer.

Note: When this cron event runs it's the time to trigger the payments or use another technique to build a queue of payments.

All this process is driven through Rules so most of it is modifiable

How do I transform a "normal" product type into a recurring one

If a product has value on any of these fields, it will be considered as a recurring product.

• commerce_recurring_ini_price
• commerce_recurring_rec_price
• commerce_recurring_ini_period
• commerce_recurring_rec_period
• commerce_recurring_end_period

There's room to improve this (i.e. with a hook).

Basic UI support through Entity API UI & Views

There's a Commerce Recurring UI submodule providing basic administration and user interface for the module, based in Views and Entity API so it's highly customizable.

Patches and notes

• Latest -dev of Commerce card on file 2.x module.
• Latest -dev of Interval Field is needed.

Extras

• For managing failed payments use Commerce Dunning

Roadmap

• What happens if the payment fails? Take into account completed orders and assume a default behavior.
• Initial period on recurring entity must be configurable by rules so you can override the initial period order.
• Complete test coverage
• Recurring Orders support