Connecting a supplier to Tradecloud through SCSN involves four parties: the buyer, the supplier, the supplier's SCSN service provider, and Tradecloud as the buyer's service provider. This checklist covers what needs to be arranged before you start testing.
Step 1: Register in the SCSN address book
Both parties must be registered in the live SCSN address book.
Buyer, already registered | Send us your company's GLN number as listed in the address book. |
Buyer, not registered | You need an SCSN subscription; contact sales@tradecloud1.com. We register you, using your GLN number. No GLN? We can create one for you. |
Supplier, already registered | Send us your GLN number, your company name as registered with the Chamber of Commerce (KvK), and a contact person. |
Supplier, not registered | Your SCSN service provider must register you first. No service provider yet? Find one on the SCSN website. |
Step 2: Check the messages
Tradecloud uses the SCSN Order v2.0 and Order response v2.0 messages (not Order status). Although these are standard messages, interpretations differ and they don't cover customer-specific fields. Tradecloud's mapping is the same for all buyers and can't be changed per customer.
Buyers: check that all information your purchasing process needs is in the order message mapping, and share it with your supplier and their service provider.
Suppliers: check with your service provider that both messages can be processed and cover the process you agreed with your customer.
Need fields Tradecloud doesn't support? Contact sales@tradecloud1.com.
Step 3: Agree on the process
Buyer and supplier must agree in advance how to handle deviations, for example a confirmation with a different price, date or quantity, a reconfirmation, a request to deliver earlier, and sharing documents such as drawings or certificates. Without clear agreements, an SCSN connection isn't possible.
The starting point: SCSN messages handle the standard flow, and all deviations, communication and documents are handled in the Tradecloud portal. Both sides get email notifications about deviations and approve or reject them in the portal; approved changes are processed in both ERP systems automatically. SCSN messages carry document references such as drawing and revision numbers, but not the documents themselves.
[Image to add: SCSN message flow diagram]
Step 4: Test end to end
Once both parties are registered, the messages are checked and the process is agreed, you can start testing. Agree on test scenarios first; see Acceptance test scenarios for supplier integrations. Then contact support@tradecloud1.com to start.