Essential E-commerce Integrations Every Online Seller Should Have

Online selling rarely happens in one place. You start with your own store, add a marketplace, then a second one, ship parcels with two couriers, issue invoices in a separate program, and track stock in a spreadsheet. Each of these tools works great on its own — the problem is that they don’t talk to each other. And it’s the integrations that decide whether your business scales smoothly or drowns in manual data entry.

This article is an overview of the key integration categories that sooner or later concern every seller: stores, marketplaces, couriers, accounting, notifications, and inventory. For each one we explain what it’s for and in what order it’s worth rolling out — because trying to connect everything at once is the shortest path to chaos.

Why integrations are a problem in the first place

As long as you sell on a single channel, the store panel is enough. The trouble begins with the second order source: suddenly the same unit can sell twice, statuses live in several places, and every parcel is handled in a different panel. Manually rewriting data between systems is not just a waste of time — it’s the main source of errors in the address, quantity, or price.

An integration is simply an automatic bridge between two systems: an Allegro order lands in a single view, stock drops across all channels at once, and the tracking number returns to the customer on its own. The more of these bridges you build, the less work a human does by hand. We’ve ordered the categories below roughly by when they actually start to hurt.

1. Store integrations — the foundation

Before you think about marketplaces, you need your own store connected. It’s usually the heart of the brand and the first source of orders. A store integration means that orders from your WooCommerce, PrestaShop, or Sylius automatically flow into a central system, and you don’t log into the store panel for every new order.

What to look for:

• Data completeness — whether the integration pulls not just the product and quantity, but also the recipient details, the chosen shipping method, and the payment status.
• Write direction — whether the tool only reads from the store (READ-ONLY) or also writes back. Read-only is safer and is enough to centralize orders.
• Sync frequency — whether new orders appear within minutes or once an hour.

This is priority no. 1, because without tidy store orders no further integration has anything to work with.

2. Marketplace integrations — a jump in volume

Once the store works, the natural next step is a marketplace: in Poland mainly Allegro, and Amazon or eBay for cross-border sales. A marketplace is the fastest way to grow volume — but also where chaos grows fastest, because it adds another order source with its own statuses, its own shipping naming, and its own rhythm.

A good marketplace integration should:

• collect orders into the same view as the store, in a normalized form,
• keep shared stock so the same unit doesn’t sell on the marketplace and in the store at once,
• unify statuses — a single “shipped” regardless of where the order came from.

This is usually priority no. 2. We cover taming multiple channels at once in the guide to multichannel sales management software.

3. Courier integrations — the end of manual labels

When orders flow in from several channels, shipping becomes the bottleneck. Clicking labels by hand in the InPost, DPD, or DHL panels works for a few parcels a day — at a few dozen it becomes a daily grind. A courier integration lets you generate a label from the order data, without retyping the address, and close the loop: the tracking number returns to the order, the status changes to “shipped,” and the customer gets a notification.

The key elements of a good courier integration are shipping method mapping (the channel’s name → a specific courier service), handling parcel lockers and pickup points as a separate data field, and tracking that flows back to the order. This is usually priority no. 3 — it comes in when parcel volume starts eating hours a day.

4. Accounting integrations — fewer manual invoices

Every order eventually has to turn into an invoice or receipt. Issuing documents manually in a separate program (Fakturownia, wFirma) is another step that can be automated. An accounting integration means the order data — buyer, line items, amounts, VAT rates — reaches the accounting system without manual retyping, and the document is created on its own once the order is paid.

This is usually priority no. 4: it doesn’t block sales the way a disconnected warehouse does, but at growing volume it saves plenty of tedious, repetitive work and reduces document errors.

5. Notifications — customer communication on autopilot

A customer who has bought wants to know what’s happening with their order. Automatic notifications — email and SMS sent after payment, packing, and dispatch — are not just a convenience for the buyer, but also fewer questions to customer service and higher trust in the brand.

This category is rewarding because you can turn it on early and at low cost. It usually rests on an automation engine running on events: “when the status changes to shipped → send an SMS with the tracking number.” You can read more about how an order drives the whole process without clicking in the post on what an OMS is for e-commerce.

6. Inventory and stock — a single source of truth

The last category, but the one that ties everything together, is shared inventory. When each channel counts stock its own way, sooner or later you’ll sell the last unit twice — and overselling means complaints, cancellations, and lost trust. An inventory integration means a single source of truth about availability, shared across the store, the marketplace, and every further channel.

In practice, inventory isn’t a separate “for later” step — it permeates all the other integrations. As soon as you have a second channel, shared stock becomes the condition for everything else to make sense. So treat it not as the sixth item on a list, but as the foundation that closes the multichannel puzzle.

How to set rollout priorities

Don’t connect everything at once. A sensible order is usually:

1. Store — tidy up your own store’s orders into a single view.
2. Shared inventory — right away with the second channel, to avoid overselling.
3. Marketplace — add Allegro/Amazon once the foundation is stable.
4. Couriers — when parcel volume starts eating hours.
5. Accounting — when manual invoices become a bottleneck.
6. Notifications — turn on in parallel as soon as you have an automation engine.

The overriding rule: integrate what actually hurts now, not what looks nice on a feature list. Start with the data — check where you lose the most hours — and point the next bridge there.

Where Sellaro fits in (honestly, about status)

Sellaro is a central OMS — it collects orders and products from all connected channels into a single normalized view, keeps shared inventory, and has an automation engine that reacts to domain events with actions: email (SMTP), SMS, webhooks (HMAC + retry), and a log entry. It’s the layer on which all the integrations above actually make sense.

We need to be clear about where we are:

• Ready today: store modules PrestaShop, Sylius, WooCommerce (connecting a store as a channel, READ-ONLY — Sellaro does not write back to the store).
• On the roadmap / added on request: Allegro, Amazon, Shopify, courier integrations (InPost and others), and accounting (Fakturownia, wFirma). Email/SMS notifications and webhooks already work today as automation actions.

We operate on the principle that we add a missing integration for free within your plan — if your main channel is Allegro or your key courier is InPost, flag it during onboarding and we’ll prioritize it. You’ll find the current module status on the integrations page.

Frequently asked questions

Which integration should I start with?

Your own store and shared inventory. The store is usually the first order source, and shared stock protects against overselling from the moment a second channel appears. Only then is it worth adding marketplaces, couriers, and accounting.

Do I need all these integrations at once?

No. Integrate what actually hurts now. A small store on a single channel will do fine without most of them; the need for integrations grows with the number of channels and the order volume. It’s better to roll out gradually than to connect everything on one day.

What does it mean that an integration is READ-ONLY?

That the tool only reads data from the channel (orders, products, stock) and does not write back to the store — it doesn’t change orders or create listings. This is a safer model for centralizing data and is entirely enough to have one clean view of your sales.

Does Sellaro integrate with Allegro and couriers today?

The PrestaShop, Sylius, and WooCommerce modules are ready today. Allegro, Amazon, couriers, and accounting are on the roadmap and added on request within your plan — the “we add a missing integration for free” principle. The foundation (normalized orders, shared inventory, automation) already works.

Summary

Integrations are the nerves of your e-commerce: the store and marketplace bring in orders, shared inventory guards against overselling, couriers close out shipping, accounting removes manual invoices, and notifications keep the customer in the loop. The secret isn’t connecting everything at once, but rolling out in sequence — where you actually lose the most time.

Want to work out what it would cost? Check the pricing — 0% sales commission, all integrations included in the plan, and we’ll add a missing one for free. You’ll see the current module status on the integrations page.