Which integration approach do you need?
Pick the wrong approach and you pay for it twice: once building it, again replacing it. The choice comes down to how far your processes sit from what a connector vendor assumed when they built theirs.
| Pre-built connector | Middleware / iPaaS | Custom API integration | |
|---|---|---|---|
| Fits when | Standard platform, standard ERP, standard processes | Several systems to link, requirements still moving | Proprietary or heavily customized systems, non-standard business logic |
| Speed | Fastest to launch | Moderate | Slowest to launch |
| Upfront cost | Lowest | Moderate, plus platform licence | Highest |
| Ongoing cost | Vendor licence, per connection | Platform licence, scales with volume | Maintenance only, no licence |
| Where it breaks | Your process differs from the connector’s assumptions and you cannot change either one | Transform complexity or record volume outgrows your plan tier | Nobody documented it and the person who built it left |
| What Atwix does | Implement, extend, and tell you when it will not stretch far enough | Build and operate on your platform of choice | Build to your logic, or deploy Sirius for ERP |
Sirius: our ERP integration middleware
We built Sirius because we kept hitting the same wall on ERP projects. Connectors could not handle client-specific pricing tiers or multi-warehouse allocation, and every custom build restarted from zero.
Sirius sits between your store and your ERP as a middleware layer we own and maintain. You get the speed of a connector with the flexibility of a custom build, and no per-transaction licence.

eCommerce Integration Services We Build
Atwix covers the full scope of back-office connectivity, from the ERP that owns your inventory to the marketplace that resells it.
Integration services by platform
How an integration project runs
What are eCommerce integration services?
eCommerce integration services connect an online store to the back-office systems that hold the rest of the business data, so orders, inventory, customers and product information move between them without anyone retyping it.
- What gets connected: ERP, CRM, PIM, payment gateways, shipping and fulfillment, marketplaces, accounting
- Three ways to build it: pre-built connector, middleware platform, custom API integration
- Who needs one: any merchant running more than one system of record
- What decides the approach: how far your processes sit from the connector vendor’s assumptions
- Most common failure: nobody owns the integration after launch
Not sure which approach you need?
Send us your stack. We will tell you whether a connector covers it, and say so plainly when it does.
Frequently Asked Questions
Still deciding which approach fits your stack? Ask us directly →
How long does an eCommerce integration take?
A pre-built connector implementation runs the shortest, and a custom API integration runs the longest. The variable that most affects the timeline is how long your team takes to agree on field mapping and order-state logic. Projects stall in workshops, not in development.
Do I need middleware or a custom build?
Choose middleware when you are connecting multiple systems and expect your requirements to keep changing. Middleware gives you a platform to reconfigure without a developer ticket each time, though the license cost scales with volume. Build custom when your business logic, including pricing tiers, warehouse allocation rules, and proprietary workflows, cannot be expressed in a platform’s standard transforms. The line between the two usually lies in the stability of your requirements.
What is eCommerce API integration?
eCommerce API integration connects your store to another system through that system’s API rather than through a packaged connector. You control what data moves, when, and how it transforms. It suits proprietary systems, legacy ERPs, and any process that a connector cannot express.
Can you integrate with a legacy or proprietary ERP?
Yes. Systems with no public connector are a large share of the integration work we do. If it exposes an API, a database, or even a file drop, we can build against it.
What happens when my platform or ERP gets upgraded?
Custom integrations we build get regression-tested against platform upgrades as part of maintenance. This is the question most buyers forget to ask, and the reason integrations that worked at launch quietly break eighteen months later.
How much does eCommerce integration cost?
Cost tracks the approach, not the platform. Connectors carry the lowest build cost and a recurring license. Custom builds cost the most upfront and nothing per transaction. Over three years, the two often converge, which is why we model both before recommending either.
What are B2B eCommerce integrations?
B2B eCommerce integrations connect a B2B storefront to back-office systems such as ERP and CRM while handling the complexities that distinguish B2B from retail: account-based pricing, multi-warehouse allocation, approval workflows, and customer-specific catalogs. Standard retail connectors rarely cover these requirements without significant customization.







