Skip to content
ERP ⇄ E-commerce

Brightpearl to Easypost integration — real-time, two-way sync

Keep Brightpearl and Easypost in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Brightpearl and Easypost

Keep the storefront in step with the back office: Easypost and Brightpearl share products, inventory, and orders in real time, in both directions.

Easypost runs the storefront and takes the orders; Brightpearl owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs CarrierAccount, Webhook, Shipment, Address in Easypost with Contacts, Inventory and warehouses, Goods-out notes, Invoices and payments in Brightpearl field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Brightpearl, order and customer detail from Easypost — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Create a Tracker for every outbound shipment and stream tracker.updated webhook events into Postgres or a warehouse so support and ops see live delivery status beside order records.
  • 02 Verify and normalize customer Addresses through EasyPost before they are saved to the CRM or OMS to cut failed deliveries and carrier address-correction surcharges.
  • 03 Land order and margin data in a warehouse for retail performance reporting.
  • 04 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Brightpearl is the inventory system of record: stock stays accurate

Available quantities from Brightpearl publish to Easypost, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Easypost creates the matching record in Brightpearl with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Brightpearl and Easypost

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Brightpearl objects Easypost objects How this pairing syncs
Purchase orders Supplier orders synced with procurement or accounting systems. Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. Purchase orders is specific to Brightpearl and Address to Easypost — each maps to any object or custom field on the other side.
Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Contacts is specific to Brightpearl and Parcel to Easypost — each maps to any object or custom field on the other side.
Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. Inventory and warehouses is specific to Brightpearl and Rate to Easypost — each maps to any object or custom field on the other side.
Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. Goods-out notes is specific to Brightpearl and Tracker to Easypost — each maps to any object or custom field on the other side.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. Invoices and payments is specific to Brightpearl and Batch to Easypost — each maps to any object or custom field on the other side.
Custom fields Per-object custom attributes included in field mappings. CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. Custom fields is specific to Brightpearl and CarrierAccount to Easypost — each maps to any object or custom field on the other side.

How changes propagate between Brightpearl and Easypost

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Brightpearl Easypost Sub-second propagation

DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.

DeliveryEach detected change is written to Easypost through its API, with automatic retries and rate-limit backoff.

Easypost Brightpearl Sub-second propagation

DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.

DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
  • Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
What ships with Brightpearl ⇄ Easypost

Connect Brightpearl and Easypost for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Easypost connection.

Real-time

Two-way sync

Changes in Brightpearl or Easypost instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Brightpearl or Easypost data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Brightpearl or Easypost record.

Observability

Monitoring

Track your Brightpearl ⇄ Easypost sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Brightpearl and Easypost.

How the Brightpearl and Easypost connectors work

Brightpearl

Integration surface
REST API, organized into services (order, product, contact, warehouse, accounting)
Authentication
OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers
Change detection
Webhooks for object created/updated events, with resource search polling as a fallback
Capabilities
read · write · webhooks
Rate limits
Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints

Easypost

Integration surface
REST API (EasyPost API v2, https://api.easypost.com/v2)
Authentication
HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys
Change detection
Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
Capabilities
read · write · webhooks
Rate limits
Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
Easypost setup guide
How it works

How to connect Brightpearl to Easypost — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Brightpearl and Easypost with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Brightpearl connected
    Easypost connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Brightpearl and Easypost objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Brightpearl ⇄ Easypost
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Brightpearl Easypost
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Brightpearl and Easypost integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 465 integrations available for Brightpearl and Easypost.

Popular · 7 of 465
All Brightpearl integrations All Easypost integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own