ReturnPool makes connectivity easy

Traditionally, ReturnPool operates in an industry whereby many parties require system-to-system integration to a wide variety of entities. In our experience companies struggle to deal with multitude of imposed connectivity standards. The requirements are often regarded as too complex to deal with (especially smaller players), too time consuming and too expensive. Often it is not just connectivity standard that is prescribed, but also the data to be communicated need to be “translated” into the receivers language. What they need is easy connectivity.

In our projects we are typically connecting many partners that often struggle with the above-mentioned issues. In our (reverse) logistics supply chain projects we have connected systems of OEM´s, operators (carriers), retailers, couriers, customer support centers, repair centers and logistics hubs.

In our view supply chains can only be efficient if they are connected, focus on data enrichment throughout the chain, and prevent double data entry; hence the high level of dedication within ReturnPool to have in-house capabilities to make this happen. Since we also have a strong focus on short implementation lead-times, ReturnPool has introduced the concept of Value Added Connectivity.

How to implement Value Added Connectivity ?

Obviously direct system-to-system connectivity is the preferred way of connecting. However, if such a connection is not feasible due to the earlier mentioned reasons, then the ReturnPool connectivity solution is a viable alternative.

When the decision is taken to use the ReturnPool connectivity solution, the implementation process will exist of the following steps:

• Contrary to implementation of the imposed connectivity standard, we ask the party to be connected which data can be easily communicated without development and via which preferred file format (XML, CSV, XLS).
• We identify which data requires data enrichment. In other words, which data are missing and need to be added by our system or retrieved from other systems and which data need to be reformatted or “translated” into the format of the receiver’s system.
• We configure the most applicable of our connectivity frameworks and can start the UAT in a matter of days. The result of these steps is that we receive standard X with dataset A and send out the required standard Y with dataset B. The solution facilitates error capturing and related alert handling.

Globally we have connected a vast number of parties and have facilitated them to deploy their projects in record time.