Feature Requests

Got an idea for a new feature or integration? We’d love to hear it! You can find our roadmap here.

25 votes

FluentCRM – Enhanced Ecommerce

When connecting to FluentCRM over the REST API, allow for syncing WooCommerce orders into the Purchase History tab, and triggering automations using the WooCommerce triggers (if possible).

Planned Category: Enhanced Ecommerce Jack Arturo shared this idea Updated: January 4, 2022

7 thoughts on “FluentCRM – Enhanced Ecommerce”

  1. For the Purchase History tab, FluentCRM doesn’t store WooCommerce orders within their own data storage, they read it directly out of WooCommerce… so it won’t be possible to sync data into that tab over the REST API.

    However, we should be able to sync orders into deals / stages / pipelines, since those will have their own data storage and record IDs.

    This is the latest discussion on the pipelines feature: https://www.facebook.com/groups/fluentcrm/posts/5669586806481943/

    It sounds like it will be released soon. Once that’s available, we’ll check it out and proceed with an integration.

  2. Christopher Miller

    This would be pretty cool. Is it too much to ask that this be made possible for multiple eCommerce sources? One reason for using the REST API rather than native is we have 2 separate Woo sites, one for physical products, one for memberships. Plus a Gravity Forms checkout for appointments. I guess they could all go into a list under the same Purchase History tab, but with the site name indicating which one it came from.

    1. Yup totally. Apparently, pipelines are coming within the next few weeks. When we add Enhanced Ecom support, it will work out of the box with all the plugins listed here https://wpfusion.com/documentation/ecommerce-tracking/ecommerce-overview/#supported-plugins, from as many connected sites as you want 🙂

      We will try to indicate the site name as long as the API supports it. A lot is up in the air while we wait for the feature to be released.

Leave a Comment

Your email address will not be published. Required fields are marked *

Powered by Simple feature Requests