A website that lives apart from your back office sooner or later starts telling lies. The price on the site says one thing, the ERP another. A product gets ordered, but it's already out of stock. A sales rep copies orders from email into the CRM by hand and mistypes the phone number. Integrating your website with your ERP, CRM and inventory means data is entered once and then flows to every system on its own.
Here is what data usually moves between systems, which exchange methods exist and how they differ, how often to sync stock levels, what breaks most often, and how to prepare for the project so it doesn't drag on for six months.
What data moves between the website, ERP and CRM
The set depends on the business, but for online stores and B2B websites it's almost always similar. It's important to pin down not only what's transferred but in which direction.
- Product catalog. Names, SKUs, categories, attributes, variants (size, color, volume), units of measure. Usually flows from the ERP to the site.
- Prices. Retail, wholesale, by price list and customer group, promotional. Also from the ERP to the site.
- Stock levels. Total or per warehouse and store, sometimes accounting for reservations. Same direction.
- Orders. Line items, total, shipping, payment, comments. They go from the site to the ERP and the CRM.
- Customers. Contacts, company details, custom terms. They can be created on the site, in the CRM and in the ERP at the same time, which is the main source of duplicates.
- Statuses. Paid, packed, shipped, delivered. They come back from the ERP or CRM to the site and the customer's account.
B2B adds documents to the list: invoices, statements, contracts, account balances. They're often shown in the customer portal, and that's a separate data flow with its own access rules.
Ways to sync data between a website and an ERP
Technically, there are several ways to connect the systems. The choice depends on catalog size, how standard your ERP setup is, and how many systems take part in the exchange.
Off-the-shelf connectors
Many e-commerce platforms and ERPs offer ready-made connectors: plugins or apps that sync the catalog, prices and stock to the site and pull orders back. For a standard store on a standard ERP setup, this is the fastest route: the exchange is configured, not programmed.
The limits show up when the logic goes beyond the standard: custom pricing, complex variants, several legal entities, a heavily customized ERP. Then the exchange gets patched on both sides and becomes fragile.
ERP APIs
Most modern ERPs expose a REST API, and many let you publish custom endpoints. The site or a middleware service calls them directly and gets only the data it needs: the stock of a specific product, an order status, a customer-specific price. This is more flexible than a connector, but it requires ERP development work and an internet-facing instance with well-designed security.
Middleware (integration bus)
A separate service sits between the systems: it receives data, normalizes it, routes it to the right recipients and keeps an exchange log. This approach pays off when there are more than two systems: the website, ERP, CRM, warehouse management system, marketplaces. Each system integrates with the bus once, instead of with every other system in pairs.
Scheduled file exports
The simplest option: the ERP drops a file (XML, CSV, Excel) on the server on a schedule, and the site picks it up. It works for small catalogs and data that rarely changes. It's no good for real-time orders and stock.
| Connector | ERP API | Middleware | |
|---|---|---|---|
| Time to launch | Fast for a standard ERP | Medium | Longest |
| Flexibility | Low | High | High |
| Sync frequency | Scheduled, in batches | On request, near-instant | Configurable |
| Best for | Standard store, site + ERP | Custom logic, B2B | Three or more systems |
In practice, methods get combined: the catalog syncs once a day through a connector, while the stock of items in the cart is checked through an API call at checkout.
Website CRM integration: HubSpot, Pipedrive, Salesforce
The CRM usually owns sales: leads, deals, customer communication. HubSpot, Pipedrive and Salesforce all have open REST APIs and webhooks, so leads and orders from the site reach them without manual copying. The site sends the contact, order contents, source and UTM tags, and statuses can flow back from the CRM to the site.
Things get complicated when both a CRM and an ERP are in the picture. The order has to land in both systems, and the customer must not be duplicated. You need to decide up front who creates the order in the ERP: the site directly, or the CRM once a sales rep confirms the deal. With a custom CRM, this is settled during design; with an off-the-shelf one, through configuring and extending the connector.
Syncing stock and prices: how often, and what happens when they lag
Sync frequency is a trade-off between load on the ERP and data accuracy. A full catalog export can take a noticeable amount of time and strain the database, so it doesn't run every five minutes. Stock and prices are usually sent separately and more often than descriptions and images.
Rough guidelines:
- Descriptions, attributes, photos: once a day or on change.
- Prices: several times a day or on change; immediately during promotions.
- Stock: the more often the better; for fast sellers with low inventory, with a check at checkout.
- Orders and statuses: immediately or with minimal delay.
If stock data lags, the store sells what it doesn't have. Next come an apology call, a cancellation, a refund and a dent in the company's reputation. A stock error costs more than extra load on the sync. If products sell fast and inventory is small, you can't do without a stock check at checkout.
What breaks most often
The data transport itself rarely fails. The trouble is usually in the data and in agreements between people.
- No agreed master for the data. If a price can be changed both in the ERP and in the site's admin panel, a week later nobody knows which one is right. Each data type needs one master system; the others only read.
- Manual edits on both sides. A content manager fixes a product name on the site, and the next sync overwrites it. Decide up front which fields the sync updates and which the site owns: SEO copy, photos, descriptions.
- Duplicates. Products without a stable identifier, customers matched by name instead of phone number or tax ID. Every sync creates new records instead of updating existing ones.
- Mismatched reference data. Units of measure, warehouses, shipping and payment methods, order statuses are named differently in different systems. Without a mapping table, the order reaches the ERP with empty fields.
- Product variants. Size and color are set up as variants of one item in the ERP, while the site expects separate products, or the other way round. This needs sorting out before development, not after the first export.
- Silent failures. The sync failed overnight, and nobody noticed for three days until customers complained. You need an exchange log and failure alerts.
Each data type needs one master system; the others only read.
How the work is done
ERP integration is first and foremost data analysis and agreements, and only then code. Here is the sequence we follow on integration projects.
- System audit. Which ERP and how heavily it's customized, which CRM, what platform the site runs on, whether there's an existing exchange and why it falls short.
- Data map. Which entities are transferred, in which direction, how often, and which system is the master for each. A mapping table for reference data and fields.
- Choosing the exchange method. Connector, API, middleware or a combination, based on the data map, not the contractor's habits.
- Data preparation. Removing duplicates, assigning identifiers, aligning reference data. Our developers handle ERP integrations end to end, including this work on the ERP side; if you have your own ERP specialist, we coordinate changes with them.
- Development and test sync. First on a copy of the ERP database and a staging site. We check edge cases: a product was deleted, a price was zeroed out, an order was canceled after payment.
- Launch and monitoring. The first live sync under supervision, a log, error alerts, and instructions for staff on who now edits which data and where.
What the client should prepare
The more of this list is ready before kickoff, the faster and more accurate the estimate.
- The ERP product and version, and details of any customizations.
- A contact for your ERP specialist or the company that maintains the system, if any, so changes can be agreed with them.
- Access to a copy of the ERP database for testing.
- Access to the CRM and the site's admin panel, and a description of the current exchange, if there is one.
- A list of the data to be transferred and the desired frequency.
- A decision on which system is the master for products, prices, customers and orders.
- A business owner who makes the call on disputed fields and statuses.
What drives the timeline and cost
You can't price a website ERP integration without an audit: tasks that sound the same can differ in scope several times over. The estimate depends on:
- Number of systems and data flows. A site plus an ERP is one story; a site, ERP, CRM, warehouse system and marketplaces is a very different one.
- Standard or customized ERP. On a standard setup much can be configured with built-in tools; on a customized one, the exchange is often written from scratch.
- Catalog size and frequency of changes. This determines whether a batch export is enough or you need change tracking and an API.
- State of the data. Cleaning up reference data can take longer than the programming.
- Pricing complexity. Customer-specific prices, volume discounts, multiple warehouses and legal entities.
- Reliability requirements. An exchange log, retries on failure, alerts, monitoring.
If the integration is part of building a new website, it's best to plan for it from the start: the catalog structure and product pages are designed around the ERP data from day one. As a web development agency, we've built online stores and services with integrations like these; you can see them on our work page.
FAQ
What is an off-the-shelf ERP connector?
It's a ready-made plugin or app that links a popular e-commerce platform or CMS to an ERP and syncs the catalog, prices, stock and orders in a standard format. For a typical online store on a standard ERP setup, it means the exchange can be configured rather than built from scratch.
Can a custom-built website be integrated with an ERP?
Yes. Ready-made connectors exist for many platforms, and for websites built on custom code or frameworks the exchange runs through the ERP's API or a middleware service. The choice depends on the business requirements, not the CMS.
How often should stock levels be synced?
It depends on sales velocity and inventory size. For slow-moving products, a few syncs a day is enough. For fast-selling items with low stock, it's better to check availability in the ERP at the moment of checkout.
Do we need a separate ERP developer if an agency builds the site?
Work on the ERP side is almost always needed: even a standard exchange requires configuring the sync, reference data and permissions, and custom logic means building API endpoints or modifying the exchange. At Sphere, our developers handle ERP integrations end to end, so you don't need to find another contractor. If you have your own ERP specialist, we coordinate the changes with them.
What if orders get duplicated in the ERP or CRM?
Check which identifier the system uses to decide that an order or customer already exists. Duplicates almost always come from the lack of a stable ID or matching by name. The fix is proper matching rules and a one-time cleanup of the database.




