A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Brightpearl Integration

Powered by Commercient
HubSpot and Brightpearl integration
Integration Assessment
Integration Assessment · Retail Operations

Brightpearl × HubSpot

How Brightpearl customers, trade price lists, credit terms, products, sales orders, shipments, returns and payments connect to HubSpot contacts, companies, deals, products and orders, so marketing and sales work from real buying history and operations keeps Brightpearl as the book of record.

Brightpearl REST APIContact, order and product servicesWarehouse and accounting servicesWebhooksPrivate app or OAuth 2.0B2B and B2C
Platform ownerSage (Brightpearl by Sage)
Integration typeCustom build on the Brightpearl API
Primary directionTwo-way, split by record
FeasibilityBuildable, open APIs
API accessOpen API
01 — Summary

Does Brightpearl integrate with HubSpot?

Brightpearl runs the operations side of a retail or wholesale business: orders from every sales channel, stock across warehouses, fulfilment, and the accounting behind them. HubSpot holds the people, the pipeline and the marketing. Connecting the two puts every order, shipment and return on the customer record.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The API reference is public. The client's Brightpearl admin creates a private app and staff token inside its own account; a public OAuth app instead needs a developer account that Brightpearl approves.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Brightpearl exposes customers, orders, products, fulfilment and payments through a documented REST API, so HubSpot can market and sell from what each customer actually buys.

Campaign Creators assessment

Brightpearl's REST API is split into services: contact, order, product, warehouse, accounting and integration. Each one supports reads, searches and writes, and the integration service adds webhooks for change events. Brightpearl connects to the client's sales channels, such as its webstore and marketplaces, so its orders already cover every channel. The CC build reads that order history into HubSpot for B2C and B2B customers, and sends won B2B deals back to Brightpearl as sales orders on the right price list.

Scorecard
Data richnessHigh
API accessOpen, documented
Request headroomThrottled
Build complexityModerate

Ratings are CC judgments from Brightpearl's and HubSpot's public documentation. Request limits, webhook events and the client's channel and warehouse setup are confirmed in discovery.

Strength

Every channel's orders in one API

Brightpearl collects orders from the client's webstore, marketplaces and wholesale accounts. One order service and one search endpoint give HubSpot the full buying history, whatever channel it came from.

Plan for

A shared request budget

Brightpearl throttles API requests per account, and other apps in the account draw on the same budget. The sync module reads in ID sets, uses webhooks for changes and writes rollups, not every row.

Gate

Credentials and ownership come first

The client's Brightpearl admin creates a private app and staff token, and operations and sales sign off which system owns customers, price lists and orders before the build starts.

02 — API modules

Which Brightpearl APIs does the integration use?

Seven surfaces matter for a HubSpot build. Four carry the integration, two support it, and one is a scope decision made with the client.

Core

Contact service

contact-service · contact, company, contact-search

Customers, suppliers and the companies they belong to, with the trade terms that decide how a B2B account buys.

  • Emails, phones, addresses and organisation
  • financialDetails: price list, credit limit, credit term days
  • contact-search with updatedOn and lastOrderedOn
Core

Order service

order-service · order, sales-order, sales-credit

Sales orders and sales credits from every channel, with status, payment status, shipping status and order rows.

  • Order GET returns up to 200 orders per call
  • order-search by status, channel and updatedOn
  • Sales order POST with externalRef to prevent duplicates
Core

Product service

product-service · product, price-list, product-price

The product catalog, its SKUs and the price lists used for retail and trade customers.

  • identity.sku, barcodes and sales channel names
  • Price lists by code and currency, sell or buy
  • Live or archived status per product
Core

Warehouse service

warehouse-service · goods-out note

Goods-out notes record stock leaving a warehouse to fulfil a sales order, through picked, packed and shipped events.

  • status: picked, packed, shipped
  • shipping.reference and shipping method
  • Drives shipped and delivered messages in HubSpot
Support

Accounting service

accounting-service · payments, balances

Customer payments and contact balances give HubSpot the finance view of each trade account.

  • customer-payment-search by order and date
  • Contact balance per currency
  • Read-only in HubSpot
Support

Integration service

integration-service · webhook

Webhook subscriptions tell the sync module when a Brightpearl resource changes, so it reads only what changed.

  • subscribeTo, uriTemplate, idSetAccepted
  • qualityOfService 1 for at-least-once delivery
  • Event list confirmed in discovery
Scope decision

B2B order entry

HubSpot deals or Brightpearl orders

Decide where trade orders start. Some clients quote and close wholesale deals in HubSpot and send them to Brightpearl as sales orders. Others keep order entry in Brightpearl and send only history to HubSpot.

  • One system creates B2B orders
  • Prices always come from Brightpearl price lists
  • Written into the SOW before mapping starts
03 — Framework

How does the Brightpearl HubSpot integration work?

A CC-built integration layer sits between Brightpearl and HubSpot. It listens for Brightpearl changes, reads in batches within the request budget, applies ownership rules, and writes to one HubSpot data model.

Brightpearl
Contacts & companiescustomers, suppliers, trade terms
Products & price listsSKUs, retail and trade prices
Orders & creditssales orders, returns, order rows
Goods-out notes & paymentsshipments, payments, balances
CC integration layer
Webhook intakeresource change events, ID sets
Change readersearches on updatedOn, batched GETs
Ownership ruleswhich system wins, per field
Rollup enginelifetime value, RFM, order counts
Writers & replayHubSpot batch upserts, Brightpearl orders by externalRef
HubSpot
Contacts & companiesB2C customers and trade accounts
Deals & line itemswholesale pipeline and quotes
Productscatalog with Brightpearl prices
Ordersorder history, status, tracking
Lists, workflows & reportsRFM, reorder, shipping messages
Brightpearl → HubSpot (customers, terms, products, orders, shipments, returns, payments)HubSpot → Brightpearl (new trade customers, won B2B deals as sales orders, consent)
Principle

Each record has one owner

HubSpot owns marketing contacts, consent, deals and quotes. Brightpearl owns price lists, credit terms, products, orders, stock and payments. The other system reads them.

Principle

Store what the team acts on

HubSpot gets orders, status and rollups such as lifetime value and last order date. Stock levels, ledgers and journals stay in Brightpearl.

Principle

Respect the request budget

Webhooks trigger reads, reads use ID sets, and writes go in batches, so the sync module never crowds out the client's sales channel apps.

04 — Process

What does Brightpearl HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Operations and sales both sign the ownership rules, because both teams depend on them.

1

Discovery & inventory

List the sales channels, warehouses, price lists, order statuses and custom fields in use, the HubSpot hubs and tiers, and the decisions each team should make from HubSpot.

Gate to next phaseSigned list of records and features in scope
2

Access & request budget

The client's Brightpearl admin creates a private app and staff token. CC measures the requests other apps already use and plans the sync module's share.

Gate to next phaseCredentials return data from a contact search
3

Ownership & mapping rules

Agree which system owns each record and field, the match keys (email for people, Brightpearl contact ID for accounts), and how B2B and B2C customers are told apart.

Gate to next phaseSigned field map and ownership table
4

HubSpot data model

Create custom properties, order and line item mappings, product properties, custom events for shipments and returns, and the deal stages that create orders.

Gate to next phaseSchema approved in a HubSpot sandbox
5

Build the sync module

Build webhook intake, change reads, rollups, sales order creation by externalRef and the error replay queue. Test won-deal-to-order and shipment messages end to end.

Gate to next phaseOrder and shipment flows pass in a test account
6

Backfill

Load customers, products and an agreed window of order history, then compute lifetime value and RFM once.

Gate to next phaseHubSpot order totals reconcile to Brightpearl reports
7

Parallel run & launch

Run two weeks with order creation in review mode and customer messages paused, compare daily, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Brightpearl HubSpot integration sync?

Brightpearl field names follow its API reference. Custom fields, order statuses, channels and price lists differ in every account and are read during discovery.

Brightpearl fieldHubSpot propertyObjectDirectionNotes
Customers & companies
communication.emails.PRIemailContact↔ BothMatch key for people. HubSpot owns contact details once matched.
contactIdbp_contact_idContactBP → HSBrightpearl key. Unique.
firstName, lastNamefirstname, lastnameContact↔ BothFill blanks only after the first sync.
organisation.name / companynameCompany↔ BothTrade accounts become HubSpot companies with their contacts associated.
financialDetails.priceListIdbp_price_listCompanyBP → HSTrade or retail price list. Read-only in HubSpot.
financialDetails.creditLimitbp_credit_limitCompanyBP → HSRead-only in HubSpot.
financialDetails.creditTermDaysbp_credit_term_daysCompanyBP → HSPayment terms for trade accounts.
marketingDetails.isReceiveEmailNewsletterSubscription statusContact↔ BothHubSpot owns consent. Confirm the rule with the client's privacy lead.
assignment.current.staffOwnerContactIdhubspot_owner_idCompanyBP → HSMatched on staff email.
contact balance (per currency)bp_balance_owedCompanyBP → HSFrom the accounting service.
Products & pricing
identity.skuhs_skuProductBP → HSMatch key for products.
salesChannels product name, descriptionname, descriptionProductBP → HSBrightpearl owns the catalog.
product price on the price list in scopeprice, bp_trade_priceProductBP → HSRetail price and trade price. Confirm price list codes in discovery.
statusbp_product_statusProductBP → HSArchived products are hidden from quotes.
Orders, shipments & returns
order (orderTypeCode SO)OrderOrderBP → HSOne HubSpot order per Brightpearl sales order, associated to contact and company.
orderStatus.namebp_order_statusOrderBP → HSStatuses are set per account.
assignment.channelIdbp_channelOrderBP → HSWebstore, marketplace or wholesale.
totalValue, currencyOrder total and currencyOrderBP → HSIn order currency. Confirm field names in discovery.
orderRows: productSku, quantity, rowValueLine itemsLine itemBP → HSAssociated to the HubSpot order and product. Confirm field names in discovery.
goods-out note status.shippedCustom event: Order shippedContactBP → HSTriggers shipping messages.
goods-out note shipping.referencebp_tracking_referenceOrderBP → HSCarrier reference for customer messages.
sales credit (orderTypeCode SC)Custom event: Return creditedContactBP → HSRolls up to bp_return_count.
orderPaymentStatusbp_payment_statusOrderBP → HSPaid, partially paid or unpaid.
B2B deals to orders
sales-order POST: customer.id, priceListId, rowsDeal + line itemsDealHS → BPCreated at closed-won for trade accounts. Prices from the customer's price list.
externalRefhs_object_id (deal)DealHS → BPStops duplicate orders on retry.
new contact (contact POST)Company + contactCompanyHS → BPCreates the trade customer in Brightpearl when it does not exist yet.
order IDbp_order_idDealBP → HSWritten back after the order is created.
Rollups
sum of sales orders less creditsbp_lifetime_valueContact, CompanyBP → HSComputed in the integration layer, in base currency.
lastOrderedOnbp_last_order_dateContact, CompanyBP → HSFrom contact search.
count of sales ordersbp_order_countContact, CompanyBP → HSComputed in the integration layer.
recency, frequency, valuebp_rfm_segmentContactBP → HSSegment rules agreed with marketing.
06 — Auth & API

How are authentication and API limits handled?

Brightpearl and HubSpot both publish their API rules. Values Brightpearl sets per account, or does not list in its reference, are marked for confirmation.

TopicBrightpearlHubSpot
InterfacesREST API split into services: contact-service, order-service, product-service, warehouse-service, accounting-service and integration-service. Base URL: https://{datacenter}.brightpearlconnect.com/public-api/{account}/.REST APIs: CRM objects, associations, products, line items, orders, custom events.
AuthenticationPrivate app: the client's admin creates it in Brightpearl and requests carry the app reference and staff token headers (brightpearl-app-ref, brightpearl-account-token). Public app: OAuth 2.0 authorization code, tokens valid seven days with refresh. Confirm header names in discovery.Private app access token or OAuth 2.0 public app, scoped per object.
DatacentersEach account lives in one datacenter, named in the base URL. The OAuth token response returns the api_domain to use, which can change on refresh.One portal; region is set by the HubSpot account.
Rate limitsBrightpearl's help center describes a cap of 200 requests per rolling minute per account, with 503 returned when exceeded, shared by the account's private apps. Confirm with Brightpearl.Per-10-second burst and daily limits by subscription tier. Batch endpoints for volume.
Batch readsID sets in the URL: order GET returns up to 200 orders per call; goods-out note ID sets take up to 500 IDs. Searches return IDs and changed dates.Batch read and upsert endpoints; search returns up to 10,000 results per query.
Change detectionWebhooks on the integration service, with at-least-once delivery when qualityOfService is 1. Searches on updatedOn catch anything missed.Webhooks on deal stage and company changes trigger outbound writes.
Duplicate protectionA sales order's externalRef with the installed integration instance forms a unique key, so retries never create a second order.Upsert by unique property (bp_contact_id, hs_sku).
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Shared request budgetHigh

Sales channel, shipping and accounting apps already call the API. Measure their use in discovery and design the sync module around webhooks, ID sets and rollups.

Who creates B2B ordersHigh

If both HubSpot and Brightpearl users enter trade orders without a rule, orders duplicate. The ownership table names one system for order entry.

Telling B2B from B2CMedium

Retail customers and trade accounts both live as Brightpearl contacts. Agree the rule (company, contact group or price list) that decides whether a record becomes a HubSpot company.

Marketplace customersMedium

Some marketplaces pass masked or relay emails. Those customers sync for reporting but are left out of marketing lists unless consent is clear.

Account-specific statuses and fieldsMedium

Order statuses, channels, price lists and custom fields are set per account. Budget discovery time to read them and agree the list.

Webhook event listLow

Brightpearl publishes its subscribable events in its help center. Confirm the contact, order, product and goods-out note events in discovery and keep search-based checks as a backstop.

Opportunities in HubSpot

Lifetime value and RFM on every customerHigh value

Order history from every channel becomes lifetime value, order count and RFM segments, so marketing targets on real buying behaviour.

Replenishment and reorder campaignsHigh value

Last order date and the products a customer buys drive reorder reminders and cross-sell sequences timed to each buying cycle.

Won wholesale deals become sales ordersHigh value

A closed-won trade deal creates the Brightpearl sales order on the customer's price list. No re-keying, and no orders lost between teams.

Shipping and returns messagesMedium value

Shipped goods-out notes and sales credits trigger HubSpot emails and service tickets with the tracking reference and order attached.

Trade account context for salesMedium value

Price list, credit limit, credit term days and balance owed sit on the HubSpot company, so reps see account health before they call.

Channel reporting with marketing sourceMedium value

Orders tagged by channel join HubSpot attribution, so leaders see which campaigns drive webstore, marketplace and wholesale revenue.

Quote to cash, B2B

One flow, two systems, clear owners.

For trade accounts, HubSpot runs the selling motion and Brightpearl runs pricing, fulfilment and payment. The integration hands each record across at the moment ownership changes.

  1. HubSpot: wholesale deal and line items built from Brightpearl products and the customer's price list.
  2. Closed-won: the integration creates the Brightpearl customer (if new) and the sales order, keyed by externalRef.
  3. Brightpearl: allocation, goods-out note and shipment, with status and tracking written back to the HubSpot order.
  4. HubSpot: payment status, balance owed and reorder timing drive account management and replenishment campaigns.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the bp_ prefix in a Brightpearl property group. Rollups are calculated in the integration layer so every report agrees.

Internal nameLabelObjectTypeSource / logic
bp_contact_idBrightpearl Contact IDContactSingle-line textcontactId; unique
bp_price_listPrice ListCompanyDropdownfinancialDetails.priceListId
bp_credit_limitCredit LimitCompanyNumber (currency)financialDetails.creditLimit
bp_credit_term_daysCredit Term DaysCompanyNumberfinancialDetails.creditTermDays
bp_balance_owedBalance OwedCompanyNumber (currency)Accounting service contact balance
bp_lifetime_valueLifetime ValueContactNumber (currency)Sales orders less credits, base currency
bp_order_countOrder CountContactNumberCount of sales orders
bp_last_order_dateLast Order DateContactDate pickerlastOrderedOn
bp_rfm_segmentRFM SegmentContactDropdownRecency, frequency and value rules
bp_order_statusBrightpearl Order StatusOrderDropdownorderStatus.name
bp_channelSales ChannelOrderDropdownassignment.channelId
bp_tracking_referenceTracking ReferenceOrderSingle-line textgoods-out note shipping.reference
09 — Scope builder

Interactive scope builder

Choose the records and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
10 — Sources

Sources & verification

Based on public documentation from Brightpearl. Request limits, webhook events and account-specific setup are confirmed with the client's Brightpearl admin and Brightpearl during discovery.

Brightpearl × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Brightpearl HubSpot integration FAQ

Does Brightpearl integrate with HubSpot?

Yes, through a custom integration on the Brightpearl REST API. Campaign Creators builds on its contact, order, product, warehouse and accounting services, and uses Brightpearl webhooks to pick up changes.

What data syncs between Brightpearl and HubSpot?

Brightpearl customers, products, sales orders, shipments, returns and payments sync to HubSpot contacts, companies, products and orders, with buying history rolled up on the customer record. Won B2B deals are sent back to Brightpearl as sales orders on the right price list.

Does it work for both B2B and B2C customers?

Yes. Retail customers and trade accounts both live as Brightpearl contacts, so an agreed rule (company, contact group or price list) decides which records become HubSpot companies. Marketplace customers sync for reporting but stay out of marketing lists unless consent is clear.

What does setting up the Brightpearl HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and inventory, access and request budget, ownership and mapping rules, the HubSpot data model, building the sync module, backfill, and a parallel run before launch.

How long does the integration take and what does it cost?

Timeline and cost depend on the sales channels, warehouses, price lists, custom fields and order history in scope, and on how much of the API request budget other apps already use. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.