Ecommerce Integrations Guide: Payments, Delivery and CRM

An online store is never just a website. Behind every order there is a payment provider that charges the card, a carrier that delivers the parcel, an inventory system that knows what is in stock, an accounting tool that records the sale and a CRM or email platform that turns a one-time buyer into a repeat customer. When these systems talk to each other automatically, the store runs smoothly. When they do not, people copy data between tabs, orders get lost and customers buy products that are no longer in stock.

That connecting work is what ecommerce integration is about. In this guide we explain what it includes, walk through the main types of ecommerce integrations (payments, shipping, CRM and marketing, ERP and inventory, marketplaces and POS), compare the ways to build them, and show how to plan an integration project so it does not turn into a source of daily problems.

We build and connect online stores as part of our ecommerce development services and work with retailers and brands across Europe and the US. You can read more about our experience in retail and ecommerce. The advice below comes from that work.

What ecommerce integration is

So, what is ecommerce integration? It is the automated exchange of data between your online store and the external systems the business depends on. Orders, customers, products, prices, stock levels, payments and shipments move between systems without manual copying.

Technically, integrations rely on a few building blocks:

• API. An application programming interface lets one system request or send data to another in a structured way, for example “create a shipment” or “get stock level for this product”.

• Webhooks. Instead of asking for updates every few minutes, a system sends a message the moment something happens: payment succeeded, parcel delivered, refund issued.

• Middleware. A layer between systems that receives data from one, transforms it and passes it to another. It can be custom code or a ready platform.

• iPaaS. Integration platform as a service, a cloud product for building and running integrations without hosting your own middleware.

• Data synchronization. Rules for keeping the same data consistent across systems: which system is the source of truth for prices, which one for stock, how often they sync.

Here is a typical order flow in an integrated store, from cart to accounting:

1. The customer places an order and pays. The payment gateway authorizes the payment and sends a confirmation back to the store.

2. The store creates the order and passes it to the order management system (OMS) or ERP, which reserves stock.

3. The shipping integration creates a shipment with the carrier, generates a label and returns a tracking number.

4. The customer receives a confirmation email with tracking from the email or CRM platform.

5. Stock levels update in the store and on every marketplace where the product is listed.

6. The sale, payment and fees are recorded in the accounting system.

7. Analytics tools receive the purchase event for reporting and advertising optimization.

Every arrow in this flow is an integration. If one breaks, someone has to do that step by hand.

Why does this matter so much for growth? A store that processes twenty orders a day can survive with manual steps: someone copies addresses into the carrier’s website and updates stock in a spreadsheet in the evening. At two hundred orders a day, the same process needs several full-time people and still produces errors. Ecommerce integrations are what let order volume grow without operations costs growing at the same rate. They also make the business more resilient: when one person is on vacation, orders still flow.

There is a customer-facing side too. Customers do not see integrations, but they feel their absence immediately: a product that turns out to be out of stock after payment, a tracking number that never arrives, a support agent who cannot see the order. Each of these moments costs trust and repeat purchases.

Payment integrations

Payments are the first integration every store needs and the one with the least room for error. The main options are payment gateways such as Stripe, PayPal and Adyen, wallets such as Apple Pay and Google Pay, and buy now, pay later services such as Klarna.

Most stores offer several methods at once. Cards cover the majority of customers, wallets speed up mobile checkout, PayPal reassures customers who do not want to enter card details on an unfamiliar site, and BNPL can lift conversion for higher-value orders.

Choosing a payment gateway

When comparing gateways, look beyond the headline fee:

• Fees. Transaction fees, currency conversion fees, chargeback fees and any monthly costs. Compare them on your real order profile, not on a single example.

• Supported countries and currencies. Can the gateway accept payments from all your markets and pay out in the currencies you need? Is it available for a company registered in your country?

• Payouts. How quickly money reaches your bank account and whether there are reserves or holds for new merchants.

• Checkout UX. Does it support wallets, saved cards and local payment methods? Can the payment form be embedded in your checkout, or does it redirect customers away?

• Integration quality. Clear documentation, a sandbox for testing, reliable webhooks and ready plugins for your platform.

Security and compliance

Card payments come with strict rules. PCI DSS is the security standard for any business that handles card data. The simplest way to reduce your obligations is to never let raw card numbers touch your servers: use hosted payment fields or a hosted checkout from the payment provider, and work with tokenization, where the provider stores the card and gives you a token instead.

3-D Secure adds an extra authentication step for the cardholder, usually a confirmation in the banking app. In Europe, strong customer authentication rules make it standard for most online card payments. A good integration handles the 3-D Secure flow smoothly, so customers are not dropped from the checkout halfway through.

Shipping and delivery integrations

After payment, shipping is where integrations save the most manual work. A good ecommerce shipping integration covers four tasks:

• real‑time rates. The checkout shows accurate delivery prices and options from carriers, based on the customer’s address, parcel size and weight.

• Label generation. Shipping labels and documents are created automatically when an order is ready, instead of being typed into a carrier’s website.

• Order tracking. Tracking numbers flow back into the store and into customer emails, and status updates arrive through webhooks.

• Returns. Return labels and return status are handled in the same flow, so customer service sees what is happening.

Stores can connect directly to carrier APIs from UPS, FedEx, DHL and national postal services, or use multi-carrier platforms such as ShipStation or EasyPost, which connect to many carriers through one integration and help compare rates. Direct integration gives more control, a multi-carrier platform gives speed and flexibility.

Local and last-mile delivery

Not all deliveries go through national carriers. Grocery, flowers, furniture and restaurants often use their own couriers or local delivery partners. Here the integration needs to handle:

• Delivery zones with different fees and minimum order values;

• Courier dispatch, assigning orders to couriers and planning routes;

• Delivery time slots that customers choose at checkout, with capacity limits so the store does not promise more than it can deliver.

These features are often custom, because they depend on how the business operates. They also tend to bring the biggest gains in customer satisfaction.

CRM and marketing integrations

Order data is valuable far beyond fulfillment. An ecommerce CRM integration sends customer profiles and order history into the CRM, where sales and support teams can see the full picture. For B2C stores, the most common tools are email and marketing platforms such as Klaviyo and Mailchimp. For B2B and mixed models, CRMs such as HubSpot and Salesforce are more typical.

What this connection enables:

• Customer segmentation. First-time buyers, repeat customers, high-value customers, people who bought a specific category.

• Abandoned cart flows. Automated emails or messages to customers who left items in the cart. These are among the highest-converting automated campaigns in ecommerce.

• Post-purchase flows. Order confirmations, review requests, cross-sell suggestions, replenishment reminders.

• Sales follow-up. For B2B, new orders and quote requests appear in the CRM as tasks for account managers.

Analytics and advertising are part of the same picture. GA4 should receive the full set of ecommerce events, from product views to purchase. Meta Conversions API sends purchase events from the server to Meta, which improves tracking accuracy and advertising optimization when browser tracking is limited. When the CRM, the store and analytics work together, this lets marketing see which campaigns bring revenue, not just clicks.

ERP, inventory and accounting integrations

For stores with significant volume, the most important integration is with the ERP, because it keeps stock and prices accurate. ERP systems such as SAP Business One, NetSuite, Odoo and Microsoft Dynamics often hold the master data for products, prices, stock and financial records.

Typical data flows are:

• Inventory sync. Stock levels move from the ERP or warehouse system to the store, so customers see accurate availability. This is the main protection against overselling, when a customer buys a product that is no longer in stock.

• Price sync. Price changes in the ERP appear in the store automatically, including customer-specific or volume prices for B2B.

• Order sync. Orders from the store go to the ERP or an order management system (OMS) for fulfillment, invoicing and returns.

• Product data. A PIM (product information management) system stores descriptions, attributes and images and feeds them to the store and other channels.

• Accounting. Sales, payments, fees and refunds are recorded in QuickBooks, Xero or the ERP’s financial module.

When the ERP is old or has a limited API, ERP integration usually needs an intermediate layer: middleware that reads data from the ERP on a schedule, transforms it and passes it to the store, and sends orders back in the format the ERP expects. This is slower to build than a direct connection, but it protects the store from the ERP’s limitations and makes it possible to replace the ERP later without rebuilding the store.

The data rules here must be very clear: which system is the source of truth for each type of data, and how conflicts are resolved. Most integration problems we fix in existing stores come from unclear ownership of data rather than from technical bugs.

For B2B, ERP integration is even more critical. A B2B ecommerce integration often needs contract prices, credit limits, payment terms and company accounts from the ERP. Without them, a B2B portal cannot replace phone and email orders.

Marketplace, POS and multichannel integrations

Many brands sell in several channels at once: their own store, marketplaces such as Amazon and eBay, shopping ads through Google Merchant Center and physical shops with a POS system.

A multichannel ecommerce integration connects these channels to one inventory and order flow:

• Ecommerce marketplace integration publishes products to marketplaces, imports orders and keeps stock in sync, so the same item is not sold twice.

• Google Merchant Center receives a product feed with prices and availability for shopping ads and free listings.

• Ecommerce POS integration connects physical stores and the online store, so stock, customers and loyalty points are shared, and options like “buy online, pick up in store” become possible.

Multichannel inventory sync is the core of all three. Without it, every new channel increases the risk of overselling.

Integration approaches

There are four main ways to build integrations. Most stores combine them.

You can see how we apply these approaches in practice in our ecommerce case studies, from boutique fashion stores to marketplaces and booking platforms.

Native plugins and apps

Most ecommerce platforms have marketplaces of ready integrations: Shopify apps, WooCommerce plugins, Magento extensions. For standard needs like popular payment gateways, major carriers or well-known email tools, a plugin is usually the fastest and cheapest route. This is what most people mean by an ecommerce platform integration.

The limits show up with volume and custom logic. Plugins may not support your specific workflow, can conflict with each other, slow the store down or stop being updated. Each plugin is also a security dependency. If you are deciding between a platform with plugins and a custom store, our comparison of custom vs ready-made ecommerce explains the trade-offs.

Custom API integration

A custom ecommerce API integration connects systems directly through their APIs, using REST or GraphQL requests and webhooks. It is the right choice when the business process is specific, the volume is high or no reliable plugin exists.

Custom integrations need to handle real-world details: rate limits (how many requests an API accepts per minute), retries when a service is temporarily unavailable, duplicate webhooks and changes in API versions. Done properly, they are the most reliable and predictable option. Done carelessly, they are a common source of silent failures.

Middleware and iPaaS

Middleware platforms sit between systems and let teams build integrations as workflows. Zapier and Make are popular for simpler automations and smaller stores. n8n offers more flexibility and can be self-hosted, which matters when you want control over data and costs. MuleSoft and similar enterprise tools target large organizations with many systems.

A platform of this kind is a good fit when a store connects many tools, the processes change often and the team wants to adjust workflows without full development cycles. We build such workflows on n8n regularly. Learn more on our n8n automation page.

Headless and composable commerce

In headless commerce, the storefront (what customers see) is separated from the commerce backend (catalog, cart, orders) and connected through APIs. Composable commerce goes further: the store is assembled from specialized services for search, content, payments, promotions and so on. The MACH approach (microservices, API-first, cloud‑native, headless) describes this architecture.

This approach gives maximum flexibility and performance for large brands with complex experiences across many channels. It also requires a strong technical team and careful integration planning, because everything is an integration. It makes sense when a brand sells through several storefronts and channels and the standard platform templates have become a constraint.

How to plan an ecommerce integration project

Good integrations are planned before they are built. Here is the step-by-step plan we follow.

1. Build an integration map. List every system involved: store, payments, shipping, ERP, CRM, email, marketplaces, analytics. Draw the data flows between them. This map often reveals duplicated tools or missing links.

2. Define data ownership. For each data type, decide which system is the source of truth: products in the PIM, stock in the ERP, customers in the CRM, orders in the OMS.

3. Do data mapping. Match fields between systems: SKU codes, product attributes, customer fields, order statuses, tax rates. Mismatched fields are the most common cause of integration errors.

4. Choose sync frequency. Some data must move in real time (payments, stock for fast-moving products), some every few minutes, some once a day (product descriptions, reports). real‑time everywhere is expensive and usually unnecessary.

5. Design error handling. Decide what happens when a system is unavailable or data is invalid: retries, queues, alerts, manual review.

6. Test in a sandbox. Use test environments from payment providers, carriers and ERPs. Test edge cases: failed payments, partial refunds, split shipments, out-of-stock items.

7. Set up monitoring. After launch, track integration health: failed syncs, delayed orders, API errors. An integration that fails silently is worse than one that fails loudly.

8. Document everything. Keep a short description of each integration: what it does, which systems it connects, which credentials and webhooks it uses, who owns it and what to do when it fails. This document saves days when a new developer joins or when something breaks at the worst possible moment, for example during a holiday sale.

How long does such a project take? For a typical store with a payment gateway, one or two carriers, an email platform and analytics, the integration part of a project usually takes a few weeks. Adding an ERP, several marketplaces and B2B pricing can extend it to two or three months. Most of that time goes not into writing code but into mapping data, agreeing on rules and testing edge cases.

Launch integrations in phases. Connecting payments, delivery, ERP, CRM and marketplaces all at once makes problems hard to trace. Start with what is needed to take and fulfill orders, usually payments and delivery, then add stock and accounting sync, then CRM and marketing. Each phase gets tested on real orders before the next one starts.

Common integration problems and how to avoid them

These are the problems we see most often when we audit existing stores.

Data duplication. The same customer or product exists several times in different systems, with slightly different data. Avoid it with clear data ownership and unique identifiers that every system uses.

Sync delays. Stock updates once an hour, so the store shows items that sold out forty minutes ago. Match sync frequency to how fast the data changes, and use webhooks where possible.

Overselling. The same item sells on the website and on a marketplace at the same moment. Use one inventory source, reserve stock at checkout and keep safety buffers for fast-moving products.

API version changes. A payment provider or marketplace updates its API, and an integration that worked for years suddenly fails. Track deprecation notices, keep integrations in maintenance and test updates before they are forced.

Vendor lock-in. All integrations are built inside one platform’s ecosystem, so moving to another platform means rebuilding everything. Keep business logic in your own middleware or code where it matters, and document every integration.

Integrations are not a one-time project. They need the same ongoing care as the store itself. If you want a team that builds the store and its integrations together and supports them after launch, our ecommerce development services cover the full cycle, from integration map to monitoring.