Flousify Connect

Description

Flousify Connect lets a WooCommerce store send order and cart events to Flousify, so the merchant can follow up on abandoned carts.

Nothing is sent when you activate the plugin. Sending stays off until you check Send order and cart data to Flousify or click Connect to Flousify on a store-specific download.

The plugin does not lock features, run a trial, or phone home in the background. Every feature on the settings screen works without a paid code inside the plugin. Flousify, the service, applies its own account limits after it receives an event.

Classic cart and checkout pages are supported. The storefront script is loaded only on the cart and checkout, and only while sending is enabled.

External services

This plugin connects to Flousify. See the External services section below for what is sent, when it is sent, and the terms and privacy policy.

External services

This plugin connects to Flousify, an abandoned-cart recovery service operated at https://flousify.net.

Flousify terms of use: https://flousify.net/en/terms

Flousify privacy policy: https://flousify.net/en/privacy

The service is provided by the plugin author. The plugin does not send data to any other third party.

When you click Connect to Flousify

Clicking Connect to Flousify sends these fields to https://flousify.net/api/woocommerce/plugin/complete (or the API URL from a legacy store zip):

• one-time connect code (pasted from Flousify, or from includes/connect-code.php in a legacy store zip)
• site URL
• site name

Flousify responds with a webhook URL, webhook secret, and tracking token. Those values are stored in the WordPress option flousify_connect_settings and sending is turned on. This request is not made on activation, and it is not repeated on later admin page loads once pairing has succeeded for that code.

When sending is enabled

Order and cart events are posted to the webhook URL you saved (the default is https://flousify.net/api/webhooks/woocommerce). Each request is JSON over https and includes:

• event name (order.created, order.updated, order.status_changed, cart.updated, checkout.updated, or plugin.test)
• order id, cart id, and order status when available
• order or cart total and currency
• customer name, phone, and email
• line item name, quantity, and total
• site URL and tracking token

The plugin also sends an X-Flousify-Signature header (HMAC-SHA256 of the body) and an X-Flousify-Site header. The tracking token is included only in that signed JSON body. It is not added to the webhook URL.

Order and cart deliveries are queued with Action Scheduler (or WP-Cron when Action Scheduler is not available) so the checkout request does not wait on Flousify. Empty carts are not sent. The same payload is not queued again for ten minutes. The storefront cart route allows 30 updates per minute for one shopper session, or for one IP when no session exists, and it rejects a phone number that is not a plausible telephone number.

Cart events are skipped when the customer has no phone number and no email. The storefront script posts those contact fields only to this site’s REST route flousify-connect/v1/cart, which then queues the same server-side request.

A test event sends the name “Flousify Test”, the phone 5550100000, and test@example.com. That test stays on the settings request so you can see the HTTP result.

No data is sent while the sending checkbox is off. You can turn on a checkout notice that tells the customer their name, phone, and email are sent to Flousify. Deactivating the plugin clears queued deliveries. Uninstalling the plugin also clears those deliveries, then deletes its options, the cart id stored on orders, and its short-lived transients.