When a sales order ships in Brightpearl, or reaches an order status you choose, Reviewflowz asks the customer for a review. Orders your staff keyed in Brightpearl or its POS credit the review to them. See the Brightpearl integration.

From each sales order we take the customer's name, email and phone, and the order reference, warehouse, sales channel and staff owner.

Each trigger sends to its own request. Connecting adds Order shipped, switched off. + Add a trigger adds another, and switching a trigger on creates its request: Fernhill Outdoor Co. has "Brightpearl order shipped" and "Brightpearl order Collected in store". A customer matching both goes to both. Deleting a trigger keeps its request, paused.

Only customers who've opted in to marketing emails in Brightpearl are asked. Marketplace orders never are, since Amazon and eBay don't allow review requests off their site, and neither are orders from a sales channel Brightpearl doesn't list or web-channel orders with only a phone number. Those customers are still kept, so their reviews can be matched by name. A sales order back-imported into Brightpearl as history never asks.

We import the last 90 days of sales orders (when you connect, or when you link a warehouse) for matching and staff credit. Nobody from that history is asked. An order that shipped or reached its status before you connected, linked its warehouse or switched the trigger on never gets a request.

In Brightpearl, create a private app and copy its reference and account token. Your account ID is the name in your Brightpearl web address. The private app only reads: nothing in Brightpearl is changed.

In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click Brightpearl. Fill in your Brightpearl account ID, the Data centre (Europe (euw1) or North America (use1)), the App reference and the Account token, then click Connect Brightpearl. If we can't find the account, the message tells you to try the other data centre.

Link each warehouse that ships or hands over orders to a Reviewflowz location. That decides which location's review page the request points to. Fernhill links Bristol shop to Fernhill Bristol and Bath shop to Fernhill Bath, and leaves Avonmouth fulfilment centre Not linked, so its orders aren't read. Linking a warehouse imports its last 90 days, for matching only. Added a warehouse? Click Refresh warehouse list. If your account isn't set up by location, there's nothing to link: every warehouse is read.

Switch on each trigger you want. That creates its request, switched off. Open it from Sends to, set the review link, objective and message, and click Turn requests on. Orders that ship or reach the status before you turn the request on are never asked about. A sales order that reaches us more than 7 days after it shipped or reached its status is never asked about.

A sales credit against an order withdraws the unsent request that order created, unless another live order from the same customer still qualifies for that request. An order we first see already refunded never asks. A message already sent can't be pulled back.

The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. Ruby Hargreaves's Google review of Fernhill Bath is credited to Lucy Bennett, the staff member who owns the order. Credit comes from orders keyed in Brightpearl or its POS; web-channel orders credit no one. Change an order's staff owner in Brightpearl and the credit follows the next time we read that order. The Team Attribution Leaderboard ranks your staff, and the CRM Integration widget tracks requests, links clicked and reviews matched.