Home > Projects > Seur

Last updated:

SEUR Shipping Integration Hub: A Headless SaaS Platform Connecting Adobe Commerce, Shopify & BigCommerce Merchants

Cloud-based shipping integration hub with connectors for Adobe Commerce, Shopify, and BigCommerce, headless Vue.js/Laravel architecture, and AI-assisted engineering for a major parcel delivery carrier's merchant-facing SaaS platform

SEUR Shipping Integration Hub: A Headless SaaS Platform Connecting Adobe Commerce, Shopify & BigCommerce Merchants

Project Summary

SEUR, a major European parcel delivery and logistics carrier, needed a way to let its merchant customers configure and use SEUR shipping methods directly inside their own ecommerce platforms, without SEUR having to integrate individually with every store. Elogic Commerce designed and built a cloud-based, headless “Hub,” the central integration and orchestration layer between SEUR and connected ecommerce platforms, handling shipping configuration, label generation, pickup scheduling, and shipment tracking. Elogic Commerce built an Adobe Commerce connector for the Hub first, then extended the same Hub with public Shopify and BigCommerce marketplace apps. AI-assisted engineering practices supported the development workflow throughout, with architecture, code review, and production decisions remaining under Elogic Commerce’s engineering team.

Key Outcomes

55%

reduction in per-merchant integration effort, compared to building and maintaining a separate custom integration for each merchant

40%

faster merchant onboarding, from install to fully configured SEUR shipping

72%+

of shipping configuration handled by merchants through self-service, without SEUR engineering involvement

87%+

of shipment-status updates propagated automatically between SEUR and connected ecommerce platforms, without manual merchant intervention

Client

SEUR

Industry

Parcel Delivery & Logistics

Region

Spain, with architecture designed for future multi-market expansion

Project type

SaaS platform strategy, requirements mapping, and full-stack development

Architecture

Headless: Vue.js frontend, PHP/Laravel backend, MySQL, RabbitMQ, Redis, JWT authentication

Platform Connectors

Adobe Commerce (built first), Shopify (public app), BigCommerce (public app)

Infrastructure

Docker-based DEV/STG/PROD environments, hosted on SEUR's Azure infrastructure, BitBucket CI/CD

Methodology

Agile, 2-week sprints, daily code review by technical leads

About the Client

SEUR is a major parcel delivery and logistics carrier operating across Spain, providing shipping, tracking, and pickup services to ecommerce merchants of all sizes. Historically, connecting SEUR’s shipping capabilities to individual merchants’ ecommerce platforms required custom, one-off integration work for each store. As SEUR sought to scale its ecommerce-merchant relationships across multiple platforms, it needed a single, centrally managed system that could serve any connected merchant, rather than repeating custom integration work platform by platform.

Project Complexity

Multi-tenant middleware architecture

The Hub needed to function as a single point of business logic serving many merchants across multiple ecommerce platforms simultaneously, with each merchant independently configuring their own shipping conditions, costs, and availability, requiring careful data isolation and configuration management at scale.

Multi-platform connector development

Adobe Commerce, Shopify, and BigCommerce each have materially different extension architectures, app approval processes, and integration patterns (webhook-based order and shipping-rate requests in BigCommerce versus Shopify’s app and checkout extension model versus Adobe Commerce’s module-based extension system), requiring the shipping method and rate logic to be implemented natively within each platform’s constraints while sourced from the same underlying Hub.

Carrier-grade shipping logic

The system needed to support multiple SEUR shipping methods (flat rate, free shipping, weight/price/zone-based matrix pricing, pickup-point delivery), three distinct pickup models (automatic daily pickup, automatic pickup triggered by order, and manual merchant-initiated pickup), multi-package label generation and management, and return-shipment initiation, each with its own business rules and SEUR API interaction pattern.

Bidirectional status synchronization

Shipment status changes needed to flow automatically from SEUR’s systems into each merchant’s ecommerce platform via a secured webhook endpoint, while merchant-side manual status changes needed to be handled separately, requiring a reliable status-mapping layer between SEUR’s internal status list and each ecommerce platform’s status model.

Security and compliance requirements

The system spanned three distinct communication boundaries, SaaS-ecommerce-to-Hub, browser-to-Hub, and Hub-to-SEUR, each requiring TLS/SSL encryption, JWT-based authentication and authorization, and SSO integration with SEUR’s existing internal authentication system for Hub administrators.

Additive, non-disruptive integration model

The connectors needed to add SEUR shipping methods to a merchant’s store without replacing or interfering with any existing shipping methods already configured on the platform, supporting merchants regardless of platform tier or licensing.

Business Challenge

01

SEUR had no scalable way to offer its shipping methods inside merchants’ ecommerce platforms without repeated, custom, one-off integration work per store

02

Merchants needed self-service control over their own SEUR shipping configuration (rates, zones, pickup methods) without requiring SEUR engineering involvement per merchant

03

Shipment status, label generation, and pickup scheduling needed to work reliably across structurally different ecommerce platforms from a single backend system

04

The solution needed to be built for future scale, additional languages, and additional ecommerce platforms beyond the initial scope, without requiring architectural rework later

05

Security and authentication needed to satisfy both SEUR’s internal SSO standards and independent per-merchant ecommerce store authentication

Elogic Commerce's Solution

Requirements Mapping and Solution Architecture

Elogic Commerce ran structured discovery with SEUR, documenting functional requirements, database architecture, entity and data-process mapping, and API rate-limit investigation, resolving open questions on SSO behavior, label storage, pickup logic, order-attribute mapping, and status synchronization through a detailed clarification process before development began.

Headless Hub Development

Elogic Commerce built the central Hub on a headless architecture, Vue.js frontend using the Vuexy template, PHP/Laravel backend, MySQL persistence with clustering for high-load periods, and RabbitMQ for queue management, giving merchants a web interface to configure shipping conditions, costs, and availability, and giving SEUR administrators a separate, permissioned Super Admin view on the same platform.

Adobe Commerce Connector

Elogic Commerce built the first platform connector for Adobe Commerce, extending the Hub’s shipping, label, and tracking capabilities into Adobe Commerce merchant stores.

Shopify and BigCommerce App Development

Elogic Commerce subsequently extended the same Hub with public marketplace apps for both platforms, implementing merchant-facing shipping-method configuration, pickup-point selection at checkout, and the platform-specific endpoints each marketplace requires (including BigCommerce’s real-time shipping-rate request/response model), while requiring merchants to authenticate with valid SEUR credentials to activate the integration.

Shipping, Label, and Tracking Logic

Elogic Commerce implemented multi-method shipping configuration (flat rate, free shipping, weight/price/zone matrix, pickup point), multi-package label generation against SEUR’s label API, three pickup models, and automated bidirectional shipment status synchronization between SEUR and each connected ecommerce platform.

Security and Authentication Architecture

Elogic Commerce implemented JWT-based authentication and authorization, TLS/SSL encryption across all three communication boundaries, and SSO integration allowing Hub administrators to authenticate using their existing internal SEUR credentials.

AI-Assisted Engineering

AI-assisted development practices were incorporated into the engineering workflow throughout the Hub and connector development, contributing to a 25% increase in development speed and a 35% reduction in QA cycle time. These gains applied to engineering delivery, not the platform’s operational metrics; architecture decisions, code review, and production deployment remained under Elogic Commerce’s engineering team.

Results & Business Impact (Measured for the Shopify and BigCommerce connectors)

55%

reduction in per-merchant integration effort. Compared with the effort required to build and maintain separate custom integrations for individual merchants, SEUR reduced the engineering work required for each new merchant connection by 55%, achieved by centralizing shipping logic, authentication, and carrier API communication in a reusable Hub.

40%

faster merchant onboarding. Merchant onboarding, from app install to fully configured SEUR shipping, became 40% faster, as self-service shipping configuration replaced manual, per-merchant technical setup.

72%+

of shipping configuration handled through self-service. Merchants now manage the majority of their own shipping configuration, methods, rates, zones, and pickup options, without requiring SEUR engineering involvement per merchant.

87%+

of shipment-status updates automated. Shipment-status changes are propagated automatically between SEUR and connected ecommerce platforms through a secured webhook endpoint, replacing manual status updates with a system where SEUR-side status changes flow directly into each merchant's store without merchant intervention.

One integration layer for three ecommerce ecosystems.

SEUR gained a centralized integration model in which the Adobe Commerce, Shopify, and BigCommerce connectors all connect to the same Hub and reuse the same shipping, authentication, label, pickup, and tracking logic, avoiding separate implementations of core carrier functionality for each platform.

Architecture Impact

3 platforms unified through 1 Hub

Adobe Commerce, Shopify, and BigCommerce supported through a centralized multi-tenant Hub, maintaining core shipping logic centrally rather than duplicating it across individual ecommerce integrations

Centralized business logic

Shipping configuration, authentication, and SEUR API communication consolidated in a single system rather than repeated per platform

Thin platform adapters

Each platform connector implements only platform-specific presentation and endpoint requirements, with core logic delegated to the Hub

Proven, extensible model

The Adobe Commerce connector, built first, established the Hub-and-connector pattern later extended to Shopify and BigCommerce, demonstrating the architecture’s ability to accommodate additional platforms without duplicating core shipping and carrier-integration logic

Capabilities Demonstrated

01

Multi-tenant SaaS platform architecture and development

02

Headless architecture (Vue.js, PHP/Laravel, MySQL, RabbitMQ)

03

Adobe Commerce connector development

04

Shopify public app development

05

BigCommerce public app development

06

Carrier and logistics API integration

07

JWT authentication, SSO integration, and TLS/SSL security architecture

08

Cross-platform shipping, label, and tracking system design for Adobe Commerce, Shopify, and BigCommerce

09

AI-assisted software engineering and QA, under engineer oversight

10

Agile delivery with structured requirements mapping and phased (MVP/Phase 2) scoping

Best Fit For

Logistics, carrier, and shipping companies needing to scale ecommerce integrations across multiple merchants without custom per-store development

Businesses building a multi-tenant SaaS platform connecting to Adobe Commerce, Shopify, BigCommerce, or other major ecommerce platforms

Organizations needing a central middleware “Hub” architecture serving many downstream merchant integrations from one system

Companies building platform-specific connectors or marketplace apps requiring different integration patterns across ecommerce platforms

Carriers or logistics providers needing self-service merchant configuration to reduce ongoing operational overhead

When This Solution Is a Good Fit

This approach is ideal for logistics providers, carriers, or platform businesses that need to serve many downstream ecommerce merchants across multiple platforms through a single, centrally managed integration layer, rather than building and maintaining custom integrations store by store.

It is generally not the right fit for businesses needing to integrate with only one or two specific merchant stores, where a direct, single-store integration is usually more efficient than building a full multi-tenant SaaS platform.

Planning a Shipping, Logistics, or Marketplace SaaS Integration?

If your business needs to connect shipping, logistics, carrier, or marketplace services to multiple ecommerce platforms at scale, Elogic Commerce can design the middleware architecture, build the platform-specific connectors, and deliver a self-service platform your customers can configure independently.

Get a free consultation