Magento 2 ↔ PlentyONE. Fully Synced.
The only enterprise-grade bidirectional integration between Magento 2 and PlentyONE — 13 core modules covering products, orders, stock, customers, categories, attributes, and pricing.
M
Magento
All Entities
ORDER
#100024
Acme Corp
PRODUCT
SKU-1042
Widget Pro
STOCK
SKU-1042
150 units
CUSTOMER
CUS-189
john@acme
CATEGORY
CAT-5
Electronics
2,847
Synced
5
Entity Types
→
←
←
→
→
⇆ SYNC
P1
PlentyONE
ERP
ORDER
PO-5024
Acme Corp
RECV
ITEM
ITM-1042
Widget Pro
SENT
STOCK
W1
150 units
SENT
CONTACT
CON-189
John Smith
RECV
CATEGORY
CAT-12
Electronics
RECV
2,847
Processed
99.8%
Success
What is a Magento–PlentyONE integration?
A Magento–PlentyONE (formerly PlentyMarkets) integration keeps a Magento 2 storefront and a PlentyONE back office in sync: products, orders, stock, customers, categories, attributes and prices flow between the two automatically, and marketplace orders from Amazon and eBay route through PlentyONE back into Magento. The usual alternatives — an external middleware/iPaaS platform or a hand-built API integration — either can't reach Magento's internal extensions or become yours to maintain forever.
The Byte8 PlentyONE Connector is the official, PlentyONE-appointed Magento integration: a native Composer module suite that runs inside Magento rather than as external middleware. Because it executes in-process it can bridge internal-only extensions (Amasty, Webkul, Swissup, DHL Packstation) that expose no REST API, supports full Multi-Source Inventory, and streams 100K+ SKU catalogs through a v2 PIM pipeline. It installs from one metapackage, needs no extra servers, and is maintained by Byte8 as the Magento and PlentyONE APIs evolve.
Built by the appointed PlentyONE Magento partner
There's a lot of surface where Magento and PlentyONE need to agree — products, orders, stock, customers, categories, attributes, properties, prices, marketplace imports, and the Magento extensions your store already runs (Amasty, Webkul, Swissup, DHL Packstation, and more). One Composer module suite handles all of it.
Official PlentyONE appointed partner
Byte8 is the appointed developer for PlentyONE's Magento integration. No competitor operates at this scale — alternatives are basic CSV importers.
Magento Open Source + Adobe Commerce, cloud or on-prem
One metapackage covers every supported Magento edition — Open Source, Adobe Commerce on-premises, and Adobe Commerce Cloud. Five product types, multi-source inventory, marketplace import, plus Adobe Commerce Content Staging bridges where you need them.
v2 pipeline · 100× faster
PIM scroll API + 3–6 MB per product + item-level error isolation. 100K-SKU imports that used to time out now stream through cleanly.
13× ROI vs manual sync
A mid-market merchant on 5,000 SKUs / 1,000 orders/mo spends ~$27,600/yr on manual sync. The Connector starts at $1,990/yr.
Eight entity surfaces, every flow under one engine
Products
Magento ⇆ PlentyONE
Orders
Magento → PlentyONE
Stock
PlentyONE → Magento
Customers
Magento ⇆ PlentyONE
Categories
Magento ⇆ PlentyONE
Attributes
Magento ⇆ PlentyONE
Properties
PlentyONE → Magento
Prices
Magento ⇆ PlentyONE
Native extension vs. middleware vs. custom build
There are three ways to connect Magento 2 and PlentyONE (formerly PlentyMarkets). Here is how a native, in-process extension compares to an external middleware platform such as Synesty and to a hand-built API integration.
| Capability | Byte8 connectorNative Magento extension | Middleware / iPaaSe.g. Synesty | Custom API buildIn-house |
|---|---|---|---|
Where it runs | Inside Magento | External cloud service | Your own code & servers |
Bidirectional sync (products, orders, customers, categories, prices) | Per field you map | Build each flow | |
Real-time / sub-minute stock sync | Polling intervals | Build it | |
Amazon / eBay marketplace order import | Sometimes | Build it | |
Multi-Source Inventory (multi-warehouse) | Limited | Build it | |
Bridges internal-only extensions (Amasty, Webkul, Swissup, DHL Packstation) | Custom Magento code | ||
Extra servers / subscriptions to run the integration | None — ships in Magento | iPaaS subscription | You host & scale it |
Maintained as Magento & PlentyONE APIs change | By Byte8 (official partner) | You re-map on breakage | Your team |
Official PlentyONE-appointed partner |
10-stage order pipeline — every document, every channel
Orders flow through a complete processing pipeline: collection, customer creation, quote, order, invoice, shipment with tracking, credit memos, returns, warranty orders, and order property sync. Marketplace orders from Amazon and eBay import via PlentyONE back into Magento. Each stage is item-isolated, so one bad row never poisons the batch.
Multi-warehouse inventory · MSI-native, 100K+ SKU tested
Full Multi-Source Inventory (MSI) support. Map PlentyONE warehouses to Magento sources, track stock movements in real time with row-level locking for concurrency safety, and handle reservations correctly across multiple warehouse locations. Stock sync interval ladders 15 min → 5 min → 1 min by tier.
v2 pipeline · 100× faster imports for large catalogs
v2 replaced the load-whole-catalog-into-memory pattern with PIM scroll APIs that stream variations in pages, batch processing at 3–6 MB per product, and item-level error isolation. A 100K-SKU import that used to crash with OOM after 40 minutes now lands in well under five — and a single broken row no longer stops the entire run.
Profile-based sync engine with admin orchestration
Every sync surface is a configurable profile — products, orders, stock, customers, categories — with field-level mapping, store-view filtering, batch sizes, and per-profile cron schedules. Staging profiles let you validate config against a sandbox before promoting to production. Magento message queues with RabbitMQ for async ordering; failed items retry with exponential backoff.
Drop-in bridges for Amasty, Webkul, Swissup, DHL
Native sync bridges for the Magento extensions your store already runs — Amasty Gift Card, Amasty Rewards, Amasty Cash on Delivery, Webkul Pre-Order, Swissup Checkout Fields — plus a Byte8-maintained module for DHL Packstation addresses. These third-party extensions have no REST API surface, so an external iPaaS can't reach them at all; only an in-process Magento bridge can. Each ships as its own optional Composer module so you install only what you actually run.
One metapackage, one command
All 13 core modules installed, then the system check verifies PHP version, Magento version, file permissions, and your PlentyONE API connection in one run. Follow up with the 7-step in-admin setup wizard or the plenty:* CLI for headless onboarding.
Setup wizard, not setup ticket
After setup:upgrade, three commands take you from “installed” to “syncing live data”. Interactive wizard, live connection test, one-shot reference-data bootstrap — every step prints a result table, not a stack trace.
bin/magento plenty:setup:client — Interactive 3-step wizard with sane defaults — log rotation, REST timeouts, API credentials. Live connection test before save. About 2 minutes.
How fresh does your inventory data need to be?
Overselling losses scale linearly with how stale Magento's stock numbers are vs PlentyONE's. Pick the interval that matches the cost of being wrong on your busiest SKU.
Standard
15 min
Stock pull cadence
Low-volume B2C with comfortable stock buffers
10K SKUs · 1K orders/mo
Professional
5 min
Stock pull cadence
Mid-volume stores where overselling causes complaints
50K SKUs · 5K orders/mo
Enterprise
1 min · realtime
Stock pull cadence
High-volume B2B and multi-channel where stock accuracy is critical
Unlimited SKUs
Install the suite or pick the pieces you need
The metapackage byte8/magento-plentyone-suite installs the core suite in one command. Adobe Commerce add-ons, optional modules, and third-party extension bridges ship separately — only what your store actually uses.
Core suite
Ships in the byte8/magento-plentyone-suite metapackage
module-core
module-profile
module-profile-notification
module-plenty-core
module-plenty-item
module-plenty-order
module-plenty-stock
module-plenty-customer
module-plenty-attribute
module-plenty-category
module-plenty-property
module-plenty-log
module-plenty-profile
Adobe Commerce add-ons
Required when running on Adobe Commerce — bridges its built-in Content Staging surface to PlentyONE
module-plenty-category-staging
module-plenty-item-staging
Additional optional modules
Drop in when you need the extra surface — utilities, storefront enhancements, DHL Packstation
module-utils
module-plenty-storefront
module-plenty-packstation
Third-party extension bridges
Native sync for Amasty / Webkul / Swissup extensions that have no REST API surface
module-plenty-amasty-cash-on-delivery
module-plenty-amasty-gift-card
module-plenty-amasty-rewards
module-plenty-webkul-preorder
module-plenty-swissup-checkout-fields
Pays for itself 13× against manual sync
A mid-market merchant with 5,000 SKUs and 1,000 orders / month. Annualised.
Cost line
Manual sync
With Connector
Admin labour
~30 hrs/mo × $50 = $1,500/mo
$0
Overselling losses
~$500/mo (conservative)
$0
Data-entry errors
~$300/mo (returns, wrong items)
$0
Annualised
~$27,600 / year
from $1,990 / year
Which Magento are you running?
Adobe Commerce customers get the Content Staging bridge modules included — same tier, no edition surcharge.
PlentyONE Connector pricing
Annual billing — pay upfront and save versus monthly.
Standard
/yr
10K SKUs · 1K orders/mo
15-min stock sync · self-service
Professional
/yr
50K SKUs · 5K orders/mo
5-min stock sync · 2 hrs/mo support
What's in each tier
Every paid tier ships the full 13-module suite and every sync surface. Tiers differ on capacity, stock-sync cadence, and support depth.
| Feature | Standard | Professional | Enterprise |
|---|---|---|---|
| Capacity & throughput | |||
SKUs synced | 10,000 | 50,000 | Unlimited |
Orders / month | 1,000 | 5,000 | Unlimited |
Stock sync cadence | Every 15 minutes | Every 5 minutes | 1 minute / realtime |
| Sync surfaces | |||
Order sync (bidirectional) | |||
Marketplace order import (Amazon / eBay) | |||
Stock sync (bidirectional) | |||
Product sync (bidirectional) | |||
Customer sync (bidirectional) | |||
Category sync (bidirectional) | |||
Attribute sync (bidirectional) | |||
Property sync (PlentyONE → Magento) | |||
Manufacturer / brand sync (bidirectional) | |||
Price sync (bidirectional) | |||
| Engine & extras | |||
v2 pipeline (PIM scroll API) | |||
Multi-Source Inventory (MSI) | |||
Staging profiles | |||
Webhook notifications | |||
Adobe Commerce Content Staging bridge | Included | Included | Included |
Third-party extension bridges | Amasty / Webkul / Swissup / DHL Packstation | Same as Standard | Plus custom bridges |
All 13 core modules | |||
Cargoman Composer registry access | |||
| Support & operations | |||
Break/fix SLA on connector bugs | 48h first response | 24h first response | Per contract |
Configuration / integration support | Add-on (£200/mo) | 2 hrs/mo included | Custom |
Admin dashboard + usage analytics | |||
Dedicated engineer | |||
Custom SLA | |||
Minimum term | 12 months | 12 months | 12 months |
Frequently asked questions
What's the best way to integrate Magento with PlentyONE (formerly PlentyMarkets)?
Are you really the official PlentyONE partner for Magento?
What Magento versions are supported?
How does the bidirectional sync actually work per entity?
Can it really handle 100K+ SKU catalogs?
How does Multi-Source Inventory (MSI) work?
What about Amasty, Webkul, Swissup, DHL Packstation, and similar?
What's the demo flow — is there a free tier or trial?
How does pricing work?
What does 'break/fix support' actually cover?
I'm an existing customer — does my contract carry over?
I'm on v1 (mage2plenty) today — what does the v2 migration look like?
Where do operators live — CLI, admin, or both?
Part of the Byte8 ecosystem
Ready to sync your Magento store with PlentyONE?
Request a hosted demo and we'll spin up a Magento + PlentyONE pairing on Byte8 infrastructure, pre-loaded with realistic data, for up to 14 days. No Composer access until you subscribe — no “install, extract, cancel” risk.