What Spark Shipping Needs to Integrate with a Vendor

Spark Shipping allows retailers to send orders, receive tracking updates and receive inventory quantity updates from manufacturers, warehouses, distributors, etc. 

Using Spark Shipping, orders can be sent to a vendors in any format the vendor requires such as API, HTTP Web Service, EDI, CSV, XML, etc.

Retailers should expect vendors to let them know how to send them orders or how they will provide inventory.  

Here are the basic guidelines for what Spark Shipping needs to connect with any vendor:

1.  Vendors who use API
   • API keys (both Live and Test)
   • Any API documents/guides from the vendor
   • Instructions (if required Test API Key and URL) on how to send in a test order
   • 1 or more test shipments (Used to test tracking API)
2. Vendors who use FTP (CSV/XML/Flatfile)
   • FTP Login credentials (both Live and Test)
   • FTP directories/folders for 
     • Orders
     • Inventory
     • Tracking/Shipment
   • Any documents/guides for the required format of order files describing which fields are mandatory and which fields are optional
   • A sample inventory file uploaded on the FTP
3. Vendors who use EDI
   • FTP Login credentials (both Live and Test)
   • FTP directories/folders for:
     • Orders
     • Inventory
     • Tracking/Shipment
   • Any documents/guides for the required format of order files describing which fields are mandatory and which fields are optional
   • A sample inventory file uploaded on the FTP