Crossfire Cloud EDI/API Integration
Crossfire provides the most comprehensive EDI/API integration solution with Cin7 Core.
Are you looking to integrate with your retail customers, suppliers, or your 3PL warehouse, or another system that doesn’t already have an integration with Cin7 Core?
Crossfire handles the entire setup for you, liaising with your trading partners, and setting the integration up on the Crossfire Integration Platform so you can get on with running your business. No in-house EDI knowledge required.
Streamlined processes, full visibility, and simple pricing.
Prerequisites
None
What is integration with EDI?
Electronic Data Interchange (EDI) is a process where orders, invoices, and other business transactions are passed electronically between business systems. It requires a specialised system to manage this process, and the expertise to keep it going.
Crossfire integration use cases
Common EDI Requirements:
Sales Orders: Have orders from retailers or customers automatically loaded into Cin7 Core via Crossfire Cloud EDI.
Advanced Shipping Notifications: Send shipping notices to your customers when sales orders are marked as completed.
Invoices: Send invoices automatically to your customers or your accounting package using Crossfire Cloud EDI.
Other EDI Requirements:
Purchase Orders: Have purchase orders sent from your supplier automatically entered into Cin7 Core via Crossfire Cloud EDI.
Inventory Balances: Have your inventory on-hand in Cin7 Core updated via Crossfire Cloud EDI from your 3rd party logistics provider, or online stores you drop ship for.
Product Updates: Automatically enter new products from another system (POS) into Cin7 Core, or automatically load new products from Cin7 Core into your POS or accounting package.
Transport Orders: Complete a Sales Invoice in Cin7 Core and have Crossfire Cloud EDI send a pickup request to your courier or transport company.
Retail example
3PL example
What is actually involved
Many Crossfire customers use systems such as Cin7 Core to manage their inventory. To enable data to flow in and out of these systems when data is being exchanged between trading partners, these different systems have developed APIs to allow specified data to pass through. To pull/push data in and out of these systems, an integration solution provider such as Crossfire has to develop a way to enable certain messages to pass through transports (such as FTP and AS2). Calls to the systems API's will need to be developed and once these are set up it allows for EDI to take place.
Connect to Crossfire
Step 1
Get in contact with Crossfire here. Tell us about your business and what you are looking to achieve.
Once we understand your requirements, our expert team will advise on the best solution for your business.
Step 2
Crossfire will set up and configure your API/EDI integration in our system.
Step 3
Any good integration will involve testing. Crossfire will test the integration with whoever you are integrating with, ensuring a robust setup.
Step 4
Go live. You will now have a free flow of data getting pushed into and pulled out of Cin7 Core.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB