Skip to main content

Subscriptions and one-time products can not coexist in a cart

At the moment, FluentCart doesn’t support creating multiple subscription products in the same cart or order. This is because the frontend checkout prevents it.

After contacting fluent support, I was informed that subscriptions and one-time products can coexist through custom code, but the default FluentCart frontend checkout intentionally prevents this.

A custom implementation can create an order with one subscription product and one-time products. However, multiple subscription products in the same cart are not recommended or reliably supported.

I’m currently developing a project that includes a headless WordPress backend for customers to sell multiple subscriptions and standalone products. I explained this to support, and they responded as follows:

“At the moment, FluentCart doesn’t support creating multiple subscription products in the same cart or order.

Even with a headless frontend, the same backend checkout and subscription logic applies. FluentCart is designed to handle one subscription item per checkout. You can include one-time products alongside a subscription through custom implementation, but multiple separate subscription products in one cart are not currently supported.

For your use case, the safer options would be:

- Create one combined subscription plan that includes service components.

- Process each subscription as a separate checkout or order.

- Use one main subscription in FluentCart and handle provisioning details through custom metadata.

This way, FluentCart can still handle billing, subscriptions, and FluentCRM integration, but multiple independent subscriptions in a single cart would require custom architecture outside the default supported flow.

The team assured me that they will pass on my feedback. They said, “Please note that our R&D team conducts a thorough analysis of each feature request to assess its feasibility and relevance. If the team determines that the feature aligns with our development roadmap, it will be forwarded to our development team for implementation.”

I hope this feature is considered for implementation. I’ve become a great supporter of the WPManageNinja products and have been integrating them into many of my recent development solutions for clients.