A complex B2B storefront, on one set of pricing rules.
CubeERP and Adobe Commerce (Magento)
Adobe Commerce and Magento Open Source connected to CubeERP stock, customer-specific pricing, order processing and fulfilment.
- E-commerce
- No per-connector licence
- 01234 672 617
Magento is normally chosen because the pricing and catalogue requirements are complicated - customer groups, tiered pricing, negotiated rates, large catalogues. Maintaining those rules in two systems is where it goes wrong. CubeERP publishes stock, catalogue and customer-specific pricing to Adobe Commerce or Magento Open Source, receives orders into the standard order process, and returns shipment and tracking data on despatch.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.
- Into CubeERP
Orders
Orders and customer data arrive as sales orders, including B2B accounts, purchase order references and requested delivery dates.
- Out of CubeERP
Stock by source
Availability published per source or warehouse, working with Magento’s multi-source inventory rather than around it.
- Out of CubeERP
Catalogue and tier pricing
Products, attributes, customer group pricing and tier prices published from CubeERP so the pricing rules exist in one place.
- Out of CubeERP
Shipments and tracking
Shipment records and carrier tracking created on despatch, driving Magento’s customer notifications.
How it behaves
The detail that decides whether it is actually useful
B2B pricing from one engine
Customer groups, negotiated prices and quantity breaks come from the CubeERP pricing engine, so web and phone quote the same figure.
Multi-source inventory
Stock published per source, with fulfilment routing decided in CubeERP where sourcing rules and transfer times are known.
Quotes and B2B workflow
Requests for quotation raised on the storefront can be picked up as CubeERP quotes and returned with proper costed pricing.
Standard API integration
Built on Magento’s REST API with a dedicated integration account, so upgrades to the store do not require the connector to be rebuilt.
Setting it up
Three steps, done during implementation
- 1
Create a Magento integration account with the required API resources - no core modification is involved.
- 2
Agree the mastering split: pricing, stock and product codes in CubeERP; content, SEO and merchandising in Magento.
- 3
Reconcile SKUs and customer groups before go-live, then run in parallel for a short period.
Questions
What people ask about this one
Both. The integration uses the REST API present in both, with Adobe Commerce B2B features supported where you have them.
Yes, and they should. Maintaining negotiated pricing in two systems is the fastest way to quote two different prices to the same customer in a week.
Yes - stock is published per source, and CubeERP decides fulfilment routing based on sourcing rules it already holds.
Updates are incremental rather than full-catalogue pushes, so a large catalogue does not mean a long sync window or a nightly load spike.
Yes. Where a PIM owns product content, CubeERP publishes only stock and price and leaves content mastering where it is.
Related
Usually set up at the same time
- ShopifyOrders in, stock and pricing out, fulfilment and tracking back - so the website sells what you actually have.
- WooCommerceWordPress and WooCommerce connected to real stock, real pricing and real despatch - without a plugin stack held together by hope.
- EDIElectronic data interchange with retailers, OEMs and distributors - orders and schedules in, despatch advices and invoices out.
Magento
Check the Magento detail before you commit
Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.