Contact

Back to Insights

Integrating MYOB Acumatica and Shopify: What You Need to Know

, ,

For businesses running MYOB Acumatica as their ERP, connecting Shopify can create a powerful eCommerce architecture.

MYOB Acumatica can remain the operational backbone of the business, managing inventory, customers, pricing, orders, purchasing and financial data, while Shopify provides the customer-facing commerce experience.

But integrating the two platforms successfully requires more than simply transferring orders from Shopify into the ERP.

Decisions need to be made around product ownership, inventory availability, customer accounts, pricing, fulfilment, order status, data structures and how frequently information needs to move between systems.

For B2B businesses, the integration can become considerably more sophisticated again, particularly where customer-specific pricing, account terms, multiple warehouses or complex product catalogues are involved.

In this guide, we look at what businesses should consider when integrating MYOB Acumatica and Shopify, the data that typically needs to be exchanged, and how to design an integration that can scale as your eCommerce operation grows.

Why Integrate MYOB Acumatica with Shopify?

The objective of an ERP and eCommerce integration should be relatively simple:

Avoid maintaining the same business information in multiple systems.

Without integration, eCommerce teams can quickly find themselves manually transferring information between Shopify and MYOB Acumatica.

This might include:

This approach might work when an eCommerce operation is small, but it becomes increasingly difficult as order volumes, product ranges and customer numbers increase.

A properly designed integration allows each platform to perform the role it is best suited to.

MYOB Acumatica can remain the source of truth for operational and financial information, while Shopify becomes the commerce layer through which customers browse products, place orders and manage their online interactions.

MYOB Acumatica and Shopify Have Different Jobs

One of the most important decisions when designing an integration is determining which system owns each type of information.

It can be tempting to try to synchronise everything in both directions.

In practice, this often creates unnecessary complexity.

A better approach is to establish clear ownership of different data domains. For example:

DataTypical System of Record
Products / SKUsMYOB Acumatica
InventoryMYOB Acumatica
Base pricingMYOB Acumatica
Customer accountsMYOB Acumatica or Shopify depending on model
Customer-specific pricingMYOB Acumatica
Online ordersShopify initially, then MYOB Acumatica
FulfilmentMYOB Acumatica / warehouse systems
Product merchandisingShopify
Product SEO contentShopify or PIM
Images and rich product contentShopify or PIM
Financial transactionsMYOB Acumatica

The exact architecture will vary between businesses.

The important point is that ownership should be deliberately defined.

Otherwise, businesses can end up with situations where Shopify updates Acumatica, Acumatica updates Shopify, and neither system has a clearly defined source of truth.

What Data Needs to Be Integrated?

A MYOB Acumatica and Shopify integration will typically involve several major data flows.

1. Product Data

Product information will often originate from MYOB Acumatica.

This may include:

However, ERP product data is rarely completely eCommerce ready.

This is an important distinction.

An ERP might contain enough information to identify, purchase and invoice a product, but an eCommerce platform generally needs significantly richer information to merchandise and sell that product effectively.

Shopify may require additional information such as:

For larger catalogues, a Product Information Management system may also sit between the ERP and Shopify.

The architecture could therefore become:

MYOB Acumatica → PIM → Shopify

rather than attempting to make MYOB Acumatica responsible for every piece of customer-facing product information.

2. Inventory Availability

Inventory is one of the most important parts of an ERP integration.

Shopify needs to understand whether a product can be purchased, but determining “available stock” is not always as simple as sending a stock-on-hand number.

A business might have:

For example, Acumatica might report:

Stock on hand: 100

But if 25 units are allocated to existing orders and another 10 units are reserved as safety stock, Shopify should potentially only make 65 units available for purchase.

This is why an integration needs to define an Available to Sell (ATS) calculation rather than simply synchronising inventory quantities without considering the underlying business rules.

3. Multi-Warehouse Inventory

For businesses operating multiple warehouses or locations, the integration becomes more sophisticated.

Shopify can maintain inventory across multiple locations, while MYOB Acumatica may also maintain stock across warehouses.

The integration needs to determine whether inventory should be:

For example, a national retailer might operate warehouses in Brisbane, Sydney and Melbourne.

Instead of simply telling Shopify that 300 units are available nationally, there may be value in exposing individual location inventory so fulfilment decisions can be made more intelligently.

This can improve delivery times and reduce freight costs.

4. Pricing

For a straightforward B2C store, pricing integration can be relatively simple.

MYOB Acumatica provides the product price and Shopify displays it.

However, businesses frequently have more complicated pricing structures.

These might include:

This becomes particularly important when using Shopify for B2B eCommerce.

The integration architecture needs to determine whether prices should be calculated in MYOB Acumatica in real time, periodically synchronised into Shopify, or translated into Shopify’s native B2B catalogue and pricing functionality.

There isn’t necessarily one correct answer.

The appropriate architecture depends on the number of customers, number of products, complexity of the pricing rules and how frequently pricing changes.

5. Customer Accounts

Customer integration is particularly important for B2B.

A B2C Shopify customer may simply exist within Shopify until they place an order.

A B2B customer, however, may already exist within MYOB Acumatica with significant information attached to their account.

This could include:

The Shopify account therefore needs to be correctly associated with the corresponding Acumatica customer.

This relationship becomes the foundation for functionality such as personalised pricing, account terms and order history.

6. Shopify Orders into MYOB Acumatica

Order integration is usually one of the central workflows.

A typical process might look like:

Customer places Shopify order → Order validated → Order created in MYOB Acumatica → Inventory allocated → Order processed → Fulfilment returned to Shopify

But there are several decisions hidden inside this relatively simple flow.

For example:

What happens if the ERP rejects the order?

What happens if inventory changes between checkout and ERP processing?

How are discounts represented?

How are freight charges mapped?

How are Shopify gift cards handled?

How are refunds handled?

How are taxes represented?

How are payment methods mapped?

How are Shopify order numbers associated with Acumatica sales orders?

These rules should be documented during the integration discovery process rather than being determined during development.

7. Fulfilment and Shipment Updates

The integration should not stop once an order reaches MYOB Acumatica.

Customers expect Shopify to provide accurate information about their order.

Once an order is fulfilled, information should generally flow back into Shopify.

This might include:

This is particularly important when an order can be shipped from multiple locations.

A single Shopify order might result in several shipments.

The integration should be capable of representing these fulfilments accurately rather than simply marking the entire order as shipped after the first item leaves the warehouse.

8. Cancellations, Returns and Refunds

The “happy path” is usually the easiest part of an integration.

The complexity tends to appear around exceptions.

Businesses should consider how the integration will handle:

There also needs to be a clear decision around which system initiates each process.

If a customer service representative processes a refund in Shopify, should that transaction automatically flow into MYOB Acumatica?

Or should refunds originate within the ERP and subsequently update Shopify?

These workflows need to match the operational processes of the business.

Using Shopify Plus with MYOB Acumatica for B2B

MYOB Acumatica and Shopify can be particularly powerful when Shopify is being used as a B2B commerce platform.

Shopify’s B2B functionality can provide the customer-facing experience, while Acumatica continues to manage the underlying commercial relationships.

The integration can potentially support:

This is where integration design becomes particularly important.

The objective should not be to rebuild the ERP inside Shopify.

Instead, the integration should expose the information customers need to transact online while leaving the underlying ERP responsible for the business logic it already manages effectively.

Should Shopify Call MYOB Acumatica in Real Time?

Not necessarily.

One of the biggest architectural decisions is determining which data needs to be real time.

It can sound attractive to have Shopify call the ERP whenever a customer requests information.

But excessive real-time dependency can create performance and reliability problems.

If every product page, customer login or checkout depends on a successful ERP request, the eCommerce experience becomes dependent on ERP performance.

A more resilient architecture often combines synchronised data and real-time requests.

For example:

Synchronised periodically:

Potentially real time:

The goal should be to minimise unnecessary dependencies while still ensuring customers receive sufficiently current information.

How Frequently Should Data Synchronise?

There is no universal answer.

Different data types have different requirements.

Product descriptions might only need to synchronise when they change.

Inventory could need to update every few minutes.

Orders might need to enter the ERP almost immediately.

Fulfilment information might update whenever warehouse processing occurs.

A good integration therefore does not simply run “every 15 minutes”.

Instead, synchronisation frequency should be considered separately for each data domain.

Where possible, event-driven integration can also reduce unnecessary API requests by processing information when something actually changes.

Direct Integration vs Middleware

Businesses also need to decide how Shopify and MYOB Acumatica will communicate.

There are several possible architectures.

Direct Integration

Shopify communicates directly with MYOB Acumatica APIs.

This can work well where requirements are relatively contained and there are only two major systems involved.

Middleware Integration

A middleware layer sits between Shopify and Acumatica.

For example:

Shopify ↔ Middleware ↔ MYOB Acumatica

Middleware can provide significant advantages for more complicated environments.

It can handle:

It also reduces the degree to which Shopify and MYOB Acumatica need to understand each other’s internal data structures.

This becomes increasingly valuable if additional systems need to be connected later.

For example:

MYOB Acumatica ↔ Integration Layer ↔ Shopify

PIM ↔ Integration Layer

CRM ↔ Integration Layer

Warehouse ↔ Integration Layer

Marketplace ↔ Integration Layer

The integration layer effectively becomes the mechanism through which the broader commerce ecosystem communicates.

Don’t Forget API Limits and Performance

API performance should be considered from the beginning of the project.

Imagine a business with:

Attempting to continuously synchronise every possible combination of this information can create an enormous volume of API traffic.

A well-designed integration should minimise unnecessary processing.

Techniques can include:

This can dramatically improve integration performance and resilience.

Error Handling Is Just as Important as Data Transfer

One of the most overlooked parts of ERP integration is error management.

What happens when something fails?

An order should not simply disappear because MYOB Acumatica was temporarily unavailable.

A robust integration should include:

For example, if Shopify successfully accepts an order but Acumatica is unavailable for five minutes, the integration should queue the order and retry it.

Once Acumatica becomes available again, processing can continue.

This architecture is significantly more reliable than requiring both platforms to be continuously available at exactly the same time.

Map the Data Before You Start Development

Data mapping should be completed before integration development begins.

For each data flow, document:

Shopify field → transformation/business rule → MYOB Acumatica field

This should include obvious fields such as SKU and price, but also less obvious information including:

This process frequently exposes problems before development starts.

For example, Shopify might allow a value that does not have an equivalent in the ERP.

The business can then decide how that information should be transformed rather than discovering the problem after orders begin failing.

ERP Categories Don’t Necessarily Belong in Shopify

Another common mistake is assuming the ERP’s product category structure should automatically become the Shopify navigation.

ERP categories are often designed around:

Customers may think about products completely differently.

Shopify categories and collections should therefore be designed around how customers search, browse and purchase products.

The integration can map ERP categories to Shopify categories without requiring the two structures to be identical.

This distinction can have a major impact on usability, SEO and product discovery.

Consider Your Product Data at the Same Time

An ERP integration project is also a good opportunity to assess the quality of your product data.

Businesses migrating from older eCommerce platforms often discover that product information has accumulated inconsistencies over many years.

Common problems include:

Simply moving this information into Shopify recreates the same problem on a newer platform.

Instead, consider what an eCommerce-ready product record should look like before building the integration.

For larger businesses, this can also be the right time to consider whether a PIM should become part of the architecture.

MYOB EXO to MYOB Acumatica and Shopify

The integration becomes particularly interesting for businesses migrating from MYOB EXO to MYOB Acumatica.

Rather than treating the ERP migration and eCommerce platform as completely separate projects, it can be valuable to consider the target architecture together.

A business might currently have:

MYOB EXO → Legacy eCommerce Platform

and be moving towards:

MYOB Acumatica → Shopify

This creates an opportunity to reconsider old integration decisions rather than simply recreating the EXO integration against Acumatica.

It may also be an opportunity to improve:

A platform migration should ideally simplify the technology environment rather than carry unnecessary legacy complexity into the new architecture.

Questions to Answer During Discovery

Before development starts, businesses should be able to answer questions such as:

  1. Which system owns each type of data?
  2. Where are products created?
  3. Where is pricing maintained?
  4. How is available inventory calculated?
  5. Which warehouses should Shopify sell from?
  6. How are Shopify customers matched to Acumatica customers?
  7. Are B2B customers using account pricing?
  8. How quickly must inventory update?
  9. How quickly must orders reach the ERP?
  10. What happens when the ERP is unavailable?
  11. How are refunds and cancellations processed?
  12. How are partial fulfilments handled?
  13. Does Shopify require real-time ERP information?
  14. How will integration failures be monitored?
  15. Will additional systems need to connect to the architecture later?

Answering these questions before development can eliminate a significant amount of rework. At OSE, we recommend a comprehensive Discovery process to clarify the above details.

A Typical MYOB Acumatica and Shopify Architecture

For a more sophisticated implementation, the architecture might look something like:

MYOB Acumatica
↓
Products, inventory, pricing, customers
↓
Integration / Middleware Layer
↓
Transformation, business rules, queues, monitoring
↓
Shopify
↓
B2C and/or B2B customer experience

Orders and customer activity then flow in the opposite direction:

Shopify
↓
Orders
↓
Integration Layer
↓
Validation and transformation
↓
MYOB Acumatica

Fulfilment information can subsequently return through the integration layer to Shopify.

For organisations with richer product information, a PIM can also form part of the architecture.

The exact solution should be determined by business requirements rather than forcing every organisation into the same integration model.

Choosing an Integration Partner

Integrating MYOB Acumatica and Shopify sits at the intersection of ERP, eCommerce and business operations.

That makes it important to choose an implementation partner that understands more than Shopify development alone.

The integration team should understand:

This is particularly important for complex B2B and multi-location businesses.

A technically successful integration that doesn’t reflect the organisation’s operational processes can still create significant problems.

The objective should be to understand how the business operates first, then design the technology architecture around those requirements.

Final Thoughts

MYOB Acumatica and Shopify can provide a strong foundation for modern eCommerce.

Shopify can deliver the customer-facing commerce experience while MYOB Acumatica continues to manage the operational and financial processes behind the business.

But the quality of the outcome depends heavily on the integration architecture between them.

The most successful implementations don’t simply ask:

“How do we connect Shopify to MYOB Acumatica?”

They ask:

“What should each system be responsible for, and how should information move between them?”

That distinction matters.

It leads to better decisions around inventory, pricing, customers, product data, orders and fulfilment. It also creates an architecture that is easier to monitor, maintain and extend as the business grows.

For organisations migrating from MYOB EXO, implementing B2B eCommerce, operating multiple warehouses or managing complex pricing, this discovery process becomes even more important.

Done properly, MYOB Acumatica and Shopify should not feel like two separate platforms that happen to exchange data.

They should operate as one connected commerce ecosystem, with each system doing the job it does best.

PREVIOUS ARTICLE

The Complete Guide to Automotive eCommerce

Selling automotive parts online presents challenges that simply do not exist in most other forms of eCommerce. A customer buying a pair of shoes generally needs to choose a size and colour. A customer buying a suspension component, brake part or engine component needs to know whether that specific product will fit their vehicle. That […]