Two-way sync
Changes in Brightpearl or Nuorder instantly reflect in both systems. No stale data, no manual imports.
Keep Brightpearl and Nuorder in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Nuorder 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 Orders, Companies, Line Items, Inventory (ATS) in Nuorder with Products, Sales orders, Purchase orders, Contacts 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 Nuorder — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
An order captured in Nuorder creates the matching record in Brightpearl with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
As orders are picked, shipped, or invoiced in Brightpearl, tracking and status flow back to Nuorder so buyers see accurate updates.
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 | Nuorder objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Products Fluent-schema catalog records (style, SKU, images, custom fields); brands push them in via /api/product/new (POST) and update via /api/product/{id} (PUT), typically mastered in a PIM or ERP. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Custom fields Per-object custom attributes included in field mappings. | Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. | Custom fields is specific to Brightpearl and Line Items to Nuorder — each maps to any object or custom field on the other side. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Inventory (ATS) Available-to-sell stock levels updated via /api/inventory/{id} (PUT); usually written from a warehouse or ERP into NuORDER so buyers see accurate availability. | Sales orders is specific to Brightpearl and Inventory (ATS) to Nuorder — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Pricing / Price Lists Wholesale and retail price data attached to products through the product data feeds; read out for margin reporting or written in during catalog loads. | Purchase orders is specific to Brightpearl and Pricing / Price Lists to Nuorder — 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. | Payments Payment status and detail returned alongside Orders (the modified-orders date-range query returns the order plus its payment information); read-oriented in most syncs. | Contacts is specific to Brightpearl and Payments to Nuorder — 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. | Orders Wholesale sales orders with nested line items and payment info; read via /api/orders/{status}/detail, created via /api/order/new (PUT), and advanced via /api/order/{id}/process and /cancel. | Inventory and warehouses is specific to Brightpearl and Orders to Nuorder — each maps to any object or custom field on the other side. |
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.
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 Nuorder through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Nuorder for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Nuorder connection.
Changes in Brightpearl or Nuorder instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Brightpearl or Nuorder data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Brightpearl or Nuorder record.
Track your Brightpearl ⇄ Nuorder sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Brightpearl and Nuorder.
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.
Authenticate Brightpearl and Nuorder with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Brightpearl and Nuorder 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Nuorder: authenticate both systems, choose the objects to sync (such as Brightpearl's Products and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Brightpearl and Nuorder: New orders reach the back office; One product catalog; Fulfillment and shipment status close the loop. An order captured in Nuorder creates the matching record in Brightpearl with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
Brightpearl: 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. Nuorder: REST API (JSON), with optional SFTP flat-file data feeds. Authentication: OAuth 1.0 — consumer key/secret plus an access token/secret issued per approved application in the NuORDER Portal (Admin > Settings > API Management > Approved Applications). Stacksync manages authentication, retries, and rate limits on both sides.
Nuorder: Change tracking is polling-based: the API exposes a date-range endpoint returning order IDs modified within a UTC window rather than pushing native webhooks. Brightpearl: Resource search endpoints return column-oriented result sets with filter parameters, which is the efficient way to poll for changed records. Stacksync's field mapping accounts for these differences between Brightpearl and Nuorder without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Brightpearl and Nuorder records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Nuorder connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Nuorder integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 370 integrations available for Brightpearl and Nuorder.