Brightpearl + Dotdigital
Everything you need to connect Brightpearl and Dotdigital: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 20 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10-15 minutes
Prepare Brightpearl
- Confirm the Brightpearl account context
- Use the agreed Brightpearl app setup
- Authorize the integration
- Save the account-specific identifiers
- Finish the setup in Junipeer
- about 5 minutes
Prepare Dotdigital
- Open API users in Dotdigital
- Create a new API user
- Leave the generated username unchanged
- Set the password and enable the user
- Save and copy the credentials
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
Junipeer - Customers
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Brightpearl (21)
| Setting | What it controls | Key |
|---|---|---|
| Allow orders that contain products that do not exist in BrightPearl? | Decide what happens with an order that contains a product that doesn't exist in Brightpearl. | brightpearl_allow_not_existent_product_on_orders |
| Brightpearl API Url | Enter the address Junipeer uses to connect to your Brightpearl account. | brightpearl_api_url |
| Brightpearl APP ref | Enter the Brightpearl app reference that Junipeer uses when connecting to your Brightpearl account. | brightpearl_app_ref |
| Brightpearl Customer Fields to update | Choose which customer details may be updated in Brightpearl. | brightpearl_update_customer_fields |
| Brightpearl acc token | Enter your Brightpearl account token . | brightpearl_acc_token |
| Brightpearl price lists to be exported | Choose which Brightpearl price lists should be exported. | brightpearl_export_price_lists |
| Channel on BrightPearl | Choose the Brightpearl channel that is set on orders sent to Brightpearl. | brightpearl_channel_for_orders |
| Create Customer in Brightpearl | Decide whether Junipeer should create new customers in Brightpearl. | brightpearl_create_customer |
Show all 21 settings
| Setting | What it controls | Key |
|---|---|---|
| Default BrightPearl warehouse [Export Stock] | Choose the Brightpearl warehouse to use as the default when stock is exported. | brightpearl_default_warehouse |
| Map Order Statuses (new and updated orders to Brightpearl) | Connect the order statuses in your webshop with the order statuses in Brightpearl. | brigthpearl_map_order_statuses |
| Map Pricelists (for Brightpearl order import) | Connect the price lists in your webshop with the price lists in Brightpearl, for orders sent to Brightpearl. | brightpearl_map_pricelists |
| Map Shipping methods | Connect the shipping methods in your webshop with the shipping methods in Brightpearl. | brightpearl_map_shipping_methods |
| Map Vat/Tax codes | Connect the VAT percentages on orders from your webshop with the tax codes in Brightpearl. | brigthpearl_map_vat_taxes |
| Multiple warehouses on BrightPearl [Export Stock]? | Decide whether stock is exported per warehouse or as one total. | brightpearl_multiple_warehouses |
| Price/Stock Article Number (to match webshop SKU) | Choose how the article number for prices and stock should be built, so that it matches the SKU in the other system. | brightpearl_sku_generator |
| Price/Stock Article Number Separator | Enter a separator to put between the fields that build the price and stock article number. | brightpearl_sku_separator |
| Update Customer in Brightpearl | Decide whether Junipeer should update customers that already exist in Brightpearl. | brightpearl_update_customer |
| Update Customer's Addresses | Decide whether the addresses (billing and shipping) of existing customers should be updated in Brightpearl. | brightpearl_update_customer_addresses |
| Use Brightpearl "on hand" value? [Export Stock] | Decide which stock value from Brightpearl is exported. | brightpearl_on_hand |
| Use custom SKU when Export Prices from Brightpearl? | Decide which article number is used when prices are exported from Brightpearl. | brightpearl_price_use_custom_sku |
| Use custom SKU when Export Stock from Brightpearl | Decide which article number is used when stock is exported from Brightpearl. | brightpearl_stock_use_custom_sku |
Settings for Dotdigital (13)
| Setting | What it controls | Key |
|---|---|---|
| Consent Attribute Fallback | Choose what happens when the customer attribute doesn't contain consent information . | dotdigital_consent_from_attribute_fallback |
| Consent Attribute Field | Enter the name of the customer attribute that holds the consent text. | dotdigital_consent_from_attribute_field |
| Consent Text | Enter the consent text that is attached to a contact when it is created or updated in Dotdigital. | dotdigital_consent_text |
| Consent URL | Enter the web address (URL) where the customer gave their consent. | dotdigital_consent_url |
| Consent from Customer Attribute | Read the consent text from a customer attribute instead of using the fixed Consent Text . | dotdigital_consent_from_attribute_enabled |
| Contact Identifier | Choose how contacts are identified in Dotdigital. | dotdigital_contact_identifier |
| Default Contact List | Choose a Dotdigital list that contacts are added to by default. | dotdigital_default_list |
| List Attribute Fallback | Choose what happens when the customer attribute doesn't contain a list ID . | dotdigital_list_from_attribute_fallback |
Show all 13 settings
| Setting | What it controls | Key |
|---|---|---|
| List Attribute Field | Enter the name of the customer attribute that holds the Dotdigital list ID(s). | dotdigital_list_from_attribute_field |
| List from Customer Attribute | Read Dotdigital list IDs from a customer attribute , instead of (or in addition to) the list settings. | dotdigital_list_from_attribute_enabled |
| Map Country to Contact List | Add contacts to a specific Dotdigital list based on their billing country . | dotdigital_list_by_country |
| Map Customer Attributes to Data Fields (Store) | Write customer attributes to Dotdigital data fields when contacts are saved. | dotdigital_map_attributes_store |
| Map Customer Fields to Data Fields (Store) | Choose which customer fields are written to Dotdigital data fields when contacts are saved. | dotdigital_map_data_fields_store |
Did this page help you?