Custom Mulesoft Application for Mapping Multiple 3rd Party Logistic Providers (3PL) to Multiple E-Commerce Storefronts

How Incepta helped map multiple 3PL providers to multiple storefronts for a leading Global Beverage Manufacturing Company in the US through custom Mulesoft Application

The Challenge

  • The company was selling through multiple storefronts which included a shopify based selling portal
  • The responsibility of order fulfilment was distributed across multiple 3rd party logistics (3PL) providers
  • Each of the 3PL providers had their own fulfilment system
  • The company was facing the challenge of connecting their storefronts automatically to the different 3PL provider systems.
  • The company needed an innovative solution to automatically send the order information to the different 3PL providers

The Solution

  • Incepta developed a framework built in mule which allowed for dynamic binding of orders placed in a storefront to a specific 3PL provider
  • The mapping with the logistic provider was dynamic and set in the database.
  • When a customer places an order the mule application receives the order retrieves the specific logistic provider tagged with the channel/product
  • The application then connects with the 3PL provider system via API and forwards the order information to the provider for fulfillment

Storefront Logistics Connector System

logistics-storefront-connector

The solution was developed in 3 steps:

  • Mapping of storefront with 3PL provider
  • Connecting with the storefront to retrieve the order
  • Connecting with 3PL provider system for forwarding of order details

Utilizing MuleSoft Anypoint Platform, Incepta built a 3-tier API led connectivity which allowed the system to connect with multiple eCommerce storefronts and access customer information, order information, pricing, etc. In the first phase of the project, Incepta connected the multiple storefronts with the MuleSoft framework.

In the second phase the The process API layer implementation (logic) flow was responsible to retrieve this mapping from the database. This allowed the experience layer and system layer implementation flows to support the rules that are specific to the ecommerce provider  and shipping service provider.

Ready. Set. Integrate.

The Power of Mulsoft Bi-Directional Sync Data Integration Pattern

The bi-directional sync data integration pattern combines two datasets in two different systems and has the ability to combine the disparate datasets to make them appear as one. The ability to combine different data systems makes Mulesoft a powerful and invaluable tool for modern industries which rely on multiple providers and IT systems, each specializing in a specific task.

In this particular use case Incepta made use of the bi-directional data sync principle to manage orders maintained in the Shopify system with the different 3PL provider systems. Using the bi-directional sync Incepta could demonstrate the use of both systems while maintaining a consistent real-time communication of data between both providers.

The customer enjoys a seamless experience of placing an order and receiving delivery status updates, while the bi-drectional sync mechanism does all the hard work of communicating with the different systems.

Such an implementation is critical to eCommerce companies operating via multiple storefronts and 3PL providers. In today’s world every system should be agnostic to the various backend systems.

MuleSoft can help drive eCommerce strategy by eliminating the point-to-point connections, and multiple potential points of failure. It removes the need to test all the different backend product systems thus ensuring smooth and hassle free operations.