Magento 2 / Adobe Commerce — configurables, MSI, per-store pricing sync (v6.13.3)
Dedicated sync module for Magento 2 (Open Source and Adobe Commerce). Configurables, Multi-Source Inventory (MSI), per-website/store/customer-group pricing. For distributors with complex Magento setups.
What Magento 2 / Adobe Commerce sync covers
Configurable & child products
PixeePIM Product Variants mapped to the Magento configurable+children pattern. Auto-generation of configurable attributes, child association, option propagation.
Multi-Source Inventory (MSI)
Native MSI compatible (Magento 2.3+): push stocks per source/stock, reservations management. Without MSI: fallback to legacy Stock Items.
Per-website / store / customer-group pricing
Magento manages 3 pricing levels: website (currency), customer group (B2B tier), special price (promo). The PIM maps them via multi-channel Price Lists without manual intervention.
Custom EAV attributes
Magento custom EAV attributes mapped from PIM fields. Auto-creation of missing `eav_attribute`, support for text/textarea/select/multiselect types.
Multi-store categories
Categories shared at Global level, content localized per store view (description, meta SEO). The PIM handles both layers from the Categories Manager.
Orders & returns pull
Periodic Magento orders read (sales/orders) to decrement PIM stock. Returns and cancellations handled with re-increment. No multi-channel overselling.
Why a dedicated Magento module (not a generic REST connector)
Magento 2 is one of the most powerful e-commerces — and one of the most complex. EAV for attributes (great for flexibility, hellish to script), configurable+children pattern (logical but verbose), MSI multi-source, multi-store/multi-website, 3 pricing levels. A poorly calibrated REST connector pushes products that don't display, or breaks MSI sources.
The PixeePIM v6.13.3 module knows Magento from the inside: it generates the right EAV payloads, respects the `configurable first, children next` order, handles MSI reservations cleanly, and logs Magento errors (usually cryptic) in readable English.
For distributors on Magento — often by historical choice for multi-store or advanced B2B — this is the difference between a sync that works and one that breaks on the next Magento patch.
Typical use cases
Multi-country Magento
One Magento, 5 per-country store views. PIM as source of truth, the module pushes translated descriptions/SEO per store view, per-website prices (currency), MSI per physical warehouse.
Advanced B2B with customer groups
10+ customer groups with differentiated tier pricing, per-group catalog visibility. PIM maintains the pricelists, the module pushes them to the right Magento groups.
Magento 1 → 2 or Adobe Commerce migration
During the Magento migration, the PIM holds product data consistency. You launch Magento 2 with a complete and synced catalog, not a manual re-entry.
Magento 2 / Adobe Commerce sync is included in every paid plan
One of 17 e-commerce/marketplace connectors + 6 ERP sync modules natively in PixeePIM.