ERP software integration with your SaaS stack: ask this first

Table of contents

1. The integration problem nobody warns you about
2. Why your existing SaaS stack matters more than vendors admit
3. The five integration questions to ask before you sign
4. CRM integration: Salesforce and HubSpot
5. E-commerce integration: Shopify and WooCommerce
6. Accounting and payroll: QuickBooks, Gusto, and ADP
7. Shipping and logistics tools
8. Native connectors versus middleware versus custom builds
9. What good integration actually looks like in practice
10. Red flags to watch for in vendor integration claims
11. What to do next

The integration problem nobody warns you about

Here is a scenario that plays out more often than it should. A California founder spends four months evaluating ERP platforms, picks the right one, executes a clean implementation, trains the team — and then discovers three months after go-live that the connection between their ERP and their Shopify store is not syncing inventory in real time. Orders are being fulfilled from stock that no longer exists. The sales team is still manually exporting from Salesforce and importing into the ERP because the native integration does not actually support the fields they need.

The ERP works fine. The integrations do not. And fixing integration problems post-go-live is significantly more expensive and disruptive than getting them right before you sign the contract.

This article is about making sure that does not happen to you. The questions here are the ones to ask during the evaluation process — before the demo turns into a proposal and the proposal turns into a signature.

Why your existing SaaS stack matters more than vendors admit

Most California small businesses that reach the point of evaluating ERP already have a collection of SaaS tools doing real work. There is a CRM managing customer relationships. There is an e-commerce platform processing orders. There is a payroll provider handling compliance with California’s complex wage and hour requirements. There may be a shipping tool, a support platform, a project management system.

These tools were chosen carefully, they work well, and your team has built processes around them. The expectation — reasonable, and often encouraged by vendor sales teams — is that the ERP will slot neatly into the center of this ecosystem, connecting everything and eliminating the manual handoffs between systems.

The reality is more nuanced. Integration quality varies enormously between platforms and between specific tool combinations. A vendor’s integration with Salesforce might be deep and bidirectional. Their integration with HubSpot might be a basic one-way sync that requires a workaround for anything beyond contact records. Understanding those differences before you commit to a platform is one of the most valuable things you can do in the evaluation process.

The five integration questions to ask before you sign

These are the questions that cut through the integration portion of an ERP demo. Vendors are accustomed to demonstrating their best-case integration scenarios. These questions are designed to surface what happens everywhere else.

Question one: Is this a native integration or a third-party connector?

A native integration is built and maintained by the ERP vendor directly. A third-party connector is built on top of a middleware platform — typically MuleSoft, Zapier, or a specialist integration tool like Celigo or Boomi — and maintained by a partner or the middleware provider. Native integrations are generally more reliable and better supported. Third-party connectors work well until they do not, and when they break, accountability is often unclear.

Ask specifically: who built this integration, who maintains it, and who do you call when it breaks?

Question two: What data flows in each direction, and how often does it sync?

Integration is not binary. A Shopify integration might sync orders into the ERP in real time but only push inventory updates back to Shopify every four hours. Depending on your order volume, a four-hour inventory sync might be fine or it might be a significant operational problem. Understand the directionality and the sync frequency for every data type that matters to your business before you assume real-time bidirectional sync is what you are getting.

Question three: What happens when the integration breaks?

Integrations fail. APIs change, authentication tokens expire, mapping rules break when one side of the connection releases an update. Ask the vendor what the monitoring and alerting process looks like when an integration fails. Is there an automated alert? How quickly is it detected? Who is responsible for the fix, and what is the typical resolution time?

Question four: What customization is possible without developer involvement?

The best integrations allow a technically capable but non-developer business user to manage field mapping, adjust sync rules, and add new data objects without writing code. If every configuration change requires a developer engagement, the integration will become a bottleneck as your business evolves and your needs change.

Question five: What is on the integration roadmap?

If the platform does not currently have a native integration with a tool that is important to your business, ask whether one is planned and when. Get the answer in writing if it is material to your decision. Vendor roadmap promises have a way of shifting, and basing your platform selection on an integration that has not shipped yet is a risk worth understanding clearly.

CRM integration: Salesforce and HubSpot

For California businesses with an active sales function, CRM integration is often the most strategically important connection in the entire ERP ecosystem. When it works well, your sales team sees current inventory and pricing data without leaving their CRM. Finance sees customer payment history without leaving the ERP. Quotes generated in the CRM flow directly into sales orders in the ERP without manual re-entry.

When it does not work well, your sales team maintains their own spreadsheet of pricing because they cannot trust the CRM data, and your finance team spends hours each week reconciling what the CRM says against what the ERP shows.

Salesforce has native integrations with NetSuite, SAP Business One, and Microsoft Dynamics 365 Business Central — though the depth of those integrations varies by edition and configuration. NetSuite’s Salesforce connector, maintained through a certified partner ecosystem, is generally regarded as one of the more mature CRM-ERP integrations available for small and mid-market businesses.

HubSpot integration quality is more variable across ERP platforms. Odoo has a native HubSpot module that handles contact and deal sync reasonably well. For other platforms, HubSpot integration typically runs through middleware like Zapier or a specialist connector, which introduces the reliability considerations discussed above.

During your demo process, ask the vendor to show you a live demonstration of the CRM integration in a sandbox — not a slide deck showing how it works in theory, but an actual record being created in the CRM and appearing in the ERP, and a change in the ERP being reflected in the CRM. That demonstration tells you more than any integration overview document.

E-commerce integration: Shopify and WooCommerce

For California product businesses selling online, e-commerce integration is where ERP value is most immediately visible — and where integration failures cause the most visible operational damage.

A well-functioning Shopify-ERP integration handles order ingestion, inventory synchronization, customer record creation, shipping status updates, and return processing — all automatically, without manual intervention. The result is that your warehouse team sees new orders in the ERP without anyone having to log into Shopify and export them. Your Shopify storefront reflects accurate inventory because the ERP is pushing updates in real time after every sale and every receiving event.

Shopify has native integration support with several major ERP platforms. NetSuite’s SuiteCommerce and its third-party Shopify connectors are widely used and generally reliable for mid-volume merchants. Acumatica has a well-regarded native Shopify integration. Microsoft Dynamics 365 Business Central has a Shopify connector that Microsoft maintains directly, which is a meaningful advantage for reliability and long-term support.

WooCommerce integration quality is less consistent across platforms. Because WooCommerce runs on WordPress and is highly customizable, the integration complexity varies significantly based on how the store has been configured. If you are running WooCommerce with significant customization, verify integration compatibility against your specific setup rather than assuming the standard connector will cover your needs.

Regardless of platform, the specific data points to verify in an e-commerce integration demo are: real-time inventory sync directionality and frequency, how split shipments are handled, how returns and refunds flow back into the ERP, and how multi-currency or multi-warehouse configurations are managed if they are relevant to your business.

Accounting and payroll: QuickBooks, Gusto, and ADP

One of the first integration questions California founders ask is whether they can keep QuickBooks running alongside their new ERP. The short answer is: usually not in the way you are imagining, and usually not for long.

An ERP replaces QuickBooks for most businesses, because the ERP’s financial management module handles everything QuickBooks does and integrates it with the rest of your operations. Running both creates the exact data reconciliation problem you are buying an ERP to eliminate.

The practical question is migration path, not ongoing integration. How cleanly can your QuickBooks data — your chart of accounts, your open invoices, your vendor balances, your historical transactions — be migrated into the ERP at go-live? Most major platforms have migration utilities or partner-supported migration processes for QuickBooks Online and QuickBooks Desktop. Ask for a specific methodology and a reference from a business that has made the same migration.

Payroll integration is a different situation. Most ERP platforms do not replace your payroll provider — they integrate with it. In California, where payroll compliance involves state income tax, SDI withholding, local taxes in several jurisdictions, and detailed wage and hour rules, most businesses are better served by keeping a California-specialized payroll provider and connecting it to the ERP rather than running payroll inside the ERP itself.

Gusto has become one of the most common payroll platforms for California small businesses, and its integration availability across ERP platforms has improved significantly. NetSuite, Acumatica, and Odoo all have Gusto integration options, though the depth varies. Verify specifically that the integration handles California-specific payroll components — SDI, SUI, local taxes — accurately before assuming standard payroll sync covers your compliance requirements.

ADP integrations are available across most major platforms and tend to be more mature given ADP’s market position, though they typically require a middleware layer and are configured differently depending on which ADP product your business uses.

Shipping and logistics tools

For product businesses, the connection between your ERP and your shipping and logistics tools determines how smoothly your fulfillment operation runs. The integration typically needs to handle outbound shipment creation, carrier rate shopping, label generation, tracking number writeback into the ERP, and in many cases, 3PL, meaning third-party logistics provider, communication.

ShipStation and ShipBob are two of the most commonly used shipping and fulfillment platforms among California small businesses. Both have integration options with major ERP platforms, though the maturity varies. ShipStation’s integration ecosystem is broad but relies heavily on third-party connectors for ERP platforms beyond the largest names. ShipBob has been developing more direct ERP integrations as it has matured, particularly for NetSuite and Acumatica, but verify current status directly given how quickly these integrations evolve.

For businesses using a 3PL, the integration complexity increases significantly. 3PL communication typically involves EDI, a standardized data format used for electronic business document exchange, or API-based connections that the 3PL needs to support on their end. Before assuming your ERP can connect to your 3PL, confirm that the 3PL has the technical capacity and willingness to build or maintain the connection — the ERP side is often the less complicated half of that equation.

Native connectors versus middleware versus custom builds

By the time you have worked through your integration requirements, you will have identified some connections that exist as native integrations, some that require middleware, and possibly some that would need to be custom-built. Understanding the implications of each category matters for both your implementation budget and your long-term maintenance picture.

Native connectors are the lowest-risk option. They are built and maintained by a vendor with direct knowledge of both systems, they typically update automatically when either system releases a new version, and support accountability is clear. When a native connector exists for a tool that is important to your business, use it.

Middleware platforms like Celigo, Boomi, MuleSoft, and Zapier sit in between your ERP and your other tools, handling data transformation and routing. They are flexible and can connect almost anything to anything, which is why they are genuinely useful for integration scenarios where no native connector exists. The tradeoffs are cost — middleware platforms carry their own subscription fees, typically $500 to $3,000 per month depending on volume and complexity — and an additional failure point in your integration chain. When a middleware-dependent integration breaks, diagnosing the issue requires checking three systems rather than two.

Custom integrations built specifically for your business offer the most control and can handle scenarios that neither native connectors nor middleware platforms accommodate well. They are also the most expensive to build and the most expensive to maintain over time. If a custom integration is proposed during your implementation, push back and ask whether a middleware solution could achieve the same outcome. The ongoing maintenance cost of a custom build is frequently underestimated.

What good integration actually looks like in practice

It is worth painting a concrete picture of what a well-integrated ERP environment actually looks like for a California small business running at scale, because the goal can feel abstract when you are in the middle of evaluating platforms.

A product company with a well-integrated ERP ecosystem might look like this: a new order placed on their Shopify store at 2pm appears in the ERP within seconds. The warehouse management module flags it for picking based on the customer’s shipping tier. The inventory count in Shopify updates in real time as the item is picked, so the next customer who views that product page sees accurate availability. When the order ships, the tracking number is written back to both the ERP and the Shopify order automatically. The revenue is recognized in the financial module according to the company’s revenue recognition policy. The Salesforce account record for that customer shows the completed order the next morning when the sales rep logs in.

Nobody moved a spreadsheet. Nobody copy-pasted a tracking number. Nobody reconciled an inventory count at the end of the day.

That is the operational clarity a well-integrated ERP delivers. Getting there requires asking the right questions before you sign — which is exactly what this article has been about.

Red flags to watch for in vendor integration claims

A few specific warning signs that should prompt deeper questions during your evaluation.

A vendor who says their platform integrates with everything but cannot show you a live demonstration of a specific integration you care about is describing capability that may exist only on paper. Always ask for a live demo of any integration that is material to your decision.

A vendor who says an integration is on their roadmap but cannot give you a committed delivery date is telling you it is not a priority. Plan around what exists today, not what might ship before your go-live.

An implementation partner who proposes a custom-built integration as the first solution rather than as a last resort is potentially optimizing for billable hours rather than your outcome. Ask whether a native connector or a middleware solution was evaluated first.

A contract that grants the vendor the right to change integration terms, deprecate connectors, or modify API access with limited notice is a risk for any business whose operations depend on those integrations. Read the API and integration sections of the contract terms before you sign.

What to do next

Integration is the piece of the ERP puzzle that tends to surface problems latest — often after the implementation is complete and the team is trying to do real work. Evaluating it thoroughly before you commit to a platform is one of the highest-leverage investments of time you can make during the selection process.

For the full framework that puts integration alongside every other criterion that should drive your vendor decision, the complete ERP vendor selection guide for California entrepreneurs covers the end-to-end evaluation process so you walk into vendor conversations already knowing what you are looking for.

And if you are still building your foundational understanding of what ERP is and how it fits into your business — or you want to share a clear starting point with a colleague who is new to the conversation — the first piece in this series, what is ERP software: a plain-English breakdown for busy founders, co