Brightpearl's app store is built around the biggest retail channels, Shopify, Amazon, eBay, with order and inventory sync that mostly just works once it's connected. Magento sits in a different spot: it's a real platform plenty of Brightpearl customers run, but Brightpearl's own native support for it isn't as deep or standardized as what the big three get. That gap is exactly where we build a direct connection instead of waiting for a one-click app to cover it.
For Shopify, Amazon, and eBay, Brightpearl's app store handles the core loop well: orders flow in, inventory syncs out, and fulfillment status updates without much manual attention once it's set up. That's the connector experience most of Brightpearl's own marketing and documentation is built around.
Magento isn't one of those headline integrations. It's a real e-commerce platform a meaningful number of retailers run, especially ones with more complex catalogs or custom storefront needs, but the native path from Magento into Brightpearl is thinner and often depends on which Magento version and which third-party connector, if any, you're already using.
Magento supports multiple store views and websites under one installation, which is a real feature a lot of larger Magento stores actually use, but it complicates how orders and inventory should map into Brightpearl if Brightpearl is only expecting one storefront's worth of data. Catalog sync has the same issue: Magento's product attributes and configurable products don't map one-to-one onto how Brightpearl structures inventory, so getting that mapping right usually takes a direct build rather than a generic connector's default settings.
BigCommerce comes up for a similar reason: it's another real storefront some Brightpearl customers run instead of, or alongside, the big three, and the same direct-API approach applies there too, whichever platform you're actually trying to connect.
Orders from each Magento store view or website land in Brightpearl correctly attributed, and inventory updates reflect the right storefront instead of treating a multi-store Magento install as a single generic channel.
Configurable products and custom attributes in Magento map onto Brightpearl's inventory structure the way your catalog actually works, not the simplified version a generic connector assumes.
Tell us which platform it is and what's currently getting exported or re-entered by hand, and we'll look at building the connection directly.
Tell us what's currently getting exported from Magento and typed back into Brightpearl, orders, stock counts, customer records, and we'll look at building the direct connection instead. And if Magento isn't actually the bottleneck, that's fine too, we automate whatever manual step is costing you the most.
Let's talk →Brightpearl's native app store is built mainly around Shopify, Amazon, and eBay. Magento support is thinner and depends on your specific setup, so a lot of Brightpearl-Magento pairings end up as a direct build against both platforms' APIs instead.
Yes, as another storefront outside Brightpearl's headline native connectors, in the same category as Magento. The practical approach is usually the same: a direct integration built for your actual catalog and order structure.
Not automatically. A generic connector tends to treat a Magento install as one storefront, which causes problems if you're running multiple store views or websites that should map to different channels or pricing inside Brightpearl.
If orders or stock counts are moving between the two more than occasionally, a direct connection almost always pays for itself quickly, since manual exports are exactly the kind of recurring, error-prone task that scales badly as order volume grows.