Checklist
This checklist an overview of all technical design decisions you need to make before starting to build an API integration with Tradecloud One.
This is divided in:
Architecture Design
ERP Design
API Integration Design
Checklist Architecture Design
When you are going to connect your ERP to Tradecloud One, you have to make some integration architecture decisions:
Connector or API Integration?
This mainly depends on your ERP system.
If your ERP is compatible with one of the Tradecloud connectors below, we advise to use one of our connectors. These connectors already contain the necessary components, message flows and data transformations to connect with Tradecloud One. They are battle-tested by our customers and will speed up your onboarding onto the Tradecloud One platform.
If your ERP is not compatible with one of these connectors, it is possible to build an integration with our JSON/XML API. This will require in-depth knowledge about your ERP and a partner or in-house software developer that has experience with web-based API integrations.
Tradecloud One Connectors
Together with our partners, Tradecloud offers the following connectors.
ERP-specific connectors:
AFAS Connector (by Improvit)
Tradecloud templates at Copernicus Niklas integration platform
Exact Globe Connector (by AB Software)
Infor LN Connector (by Xibis)
Isah API Connector (by Tambien)
Microsoft Dynamics 365 Business Central Connectivity Studio (by To-Increase)
Microsoft Dynamics 365 Finance & Operations Connectivity Studio (by To-Increase)
SAP SOAP Connector - for single SAP ERP instances
Slim4 Forecast Connector (by Slimstock)
Generic Connectors:
CSV Connector (by Supply Drive) Compatible with any ERP that supports the CSV format
Edifact Connector (by Supply Drive) Compatible with any ERP that supports the Edifact format
SCSN Connector (by Supply Drive) Compatible with any ERP that supports the SCSN format.
Middleware or 1-1 connection?
Using Message-oriented Middleware You will need message-oriented middleware if one of the following applies:
You have multiple business systems, like ERP, WMS and PLM systems, that have to integrate with Tradecloud One
You plan to integrate with the outside world, eg. with webshops or logistics partners
Examples of message-oriented middleware that some of our customers use are:
ConnectPlaza, Mulesoft, Orbis and WebMethods.
Microsoft Azure Integration Services mostly using API Management, Logic Apps and Service Bus.
Be aware you still have to build and maintain message flows & data transformations and install and configure the middleware components.
Using a 1-1 connection If you have only one ERP system and are planning to connect to Tradecloud only, building a 1-1 connection without message-oriented middleware will suffice.
Some Tradecloud customers build 1-1 connections using the tools provided by the ERP system. Be aware that these tools may be limited, and may miss for example a HTTP client or server, or security or data transformation features.
Required team members
When using a Tradecloud One Connector, in most cases a partner consultant will install, configure and maintain the Connector for you.
When using message-oriented middleware, you will need an integration consultant with ERP knowledge to build and maintain the message flows & data transformations and install & configure the middleware components.
When building an API integration, you will need developers and a tester, both with ERP knowledge, to build and maintain the message flows & data transformations and install & configure the components.
In all cases you will need a cloud or system engineer, to configure a firewall, configure SSL, install and configure a web server or Microsoft Azure Integration Services components.
Message flows
This depends on the Tradecloud One modules that are agreed upon in the contract with Tradecloud.
Within each module, there are several message flows possible dependent on the buyer or supplier role. The more flows are implemented, the less manual work remains. Whether a flow can be implemented depends on:
The process flow in your business
The capabilities of your ERP system
The capabilities of the integration
We are happy to support you in making this decision, sharing our expertise of the ERP and Supply Chain landscape.
As a buyer
For more information about the available message flows for buyers, check out:
The forecast process
As a supplier
For more information about the available message flows for suppliers, check out:
Checklist ERP Design
This part of the checklist is not applicable if you use a Tradecloud One Connectors
Before starting the actual implementation, you need to verify the capabilities and requirements of your ERP system for an integration.
Order/response Tradecloud sends only touched lines in an order/response message. It is no problem when your ERP needs all order/response lines, you may fetch the complete order, see:
Shipment Tradecloud sends always all lines in a shipment message. It is no problem if you only need touched shipment lines, you may filter out lines based on the 'lastUpdatedAt' field, see:
Checklist API Integration Design
This part of the checklist is not applicable if you use a Tradecloud One Connectors
When starting to build and integration with the Tradecloud One API, make sure to check the following:
Support
If you have any question, just ask:
Last updated