Used by purchasing teams at







Sound familiar?
01
Another integration to maintain.
Every point-to-point link with a supplier is one more thing to monitor and fix.
02
EDI only covers a few suppliers.
The rest still runs on email and manual entry.
03
No capacity for a long project.
The team is already busy with the ERP itself.
What changes
How Tradecloud One fits your landscape.
Supplier · Portal
Supplier · EDI
Supplier · API
Supplier · Portal
Supplier · EDI
Tradecloud One
All suppliers, all routes
One connection
Your ERP
One interface to maintain
01
One connection to your ERP.
Your ERP connects to Tradecloud One once. Suppliers connect to the platform, not to your ERP.
Select image to enlarge
02
Suppliers choose their own route.
A free web portal, or their own ERP connection.
Select image to enlarge
03
Managed message flow.
Messages are queued, checked and monitored.
Select image to enlarge
Connection routes
Four routes to connect.
01
Standard and partner connectors.
For SAP, Microsoft Business Central, Microsoft Dynamics 365 F&O, Exact Globe, Infor LN, ISAH and Ridder iQ.
02
REST JSON API.
A generic API, available for all functions.
03
SCSN.
Connect through the generic SCSN OpenAPI connector.
04
Custom connections.
Template integrations translate external formats into the Tradecloud format, on request.
Running on the ERP you use
Customers run Tradecloud One connected to SAP, Microsoft Business Central, Microsoft Dynamics 365 F&O, Exact Globe, Infor LN, ISAH and Ridder iQ.
Documented and monitored.
Security
Queued, checked and monitored.
Messages are queued, checked and monitored. Security, privacy and service status are documented in the Trust Center.
API
Specifications for every function.
The REST JSON API is available for all functions. The specifications are published at docs.tradecloud1.com.
Before you get started.
Walk through the integration with one of our specialists.
Let’s walk through your ERP, the connection route and the supplier rollout.
