Introduction
Our Volusion integration works by connecting to your shopping cart at scheduled intervals to perform tasks related to orders and inventory.
Fulfilling New Orders
Each time we connect to Volusion to retrieve new orders we are requesting only orders that match a certain order status. Orders matching your chosen status are retrieved by our integration module which attempts to inject each order into your Fulfillment Control Panel account for processing.
Note: Any order matching your chosen status will be retrieved, regardless of how old the order is.
Tracking Updates to Volusion
At the end of each day our integration module will send tracking numbers back to Volusion, for orders shipped that day, and update the order status to "Shipped".
Inventory Syncing (optional)
Our integration module can update the stock counts of your Volusion products with the available warehouse quantity.
Our standalone Inventory Sync Guide will walk you through setting up Inventory Syncing after you successfully add the Integration to your FCP Account.
Note: Product SKUs in Volusion must match the product SKUs available in your Fulfillment Control Panel account.
Connecting EFS & Volusion
Prerequisites
API Access is required to connect to your Volusion store. You must have a "Pro" level (or higher) account with Volusion for this to be available.
Step 1: Enable the API
Log into your Volusion account Dashboard and choose Import/Export from the Inventory menu.
Click the Volusion API button under "Data Import".
Under the "Generic" section click the grey "Run" button next to Generic\Orders.
Step 2: Obtain API Credentials
At the top of the page, under the heading Volusion API: Run Generic\Orders, click the orange "Run" button.
A "Download" button will appear next to the "Run" button and to the right of that a URL which is partially hidden, but looks like this:
http://www.YOUR-VOLUSION-STORE-URL.com/net/WebService.aspx?Login=YOUR-EMAIL@email.com&EncryptedPassword=OIJQWDI324ONIDOIJ234OIH3456POJPOIJH2O34OIH534OIH35O4IH4OIH23IH3O&EDI_Name=Generic\Orders
You will need to deconstruct this URL for the next step. It can be broken up at the ? and the & symbols as follows:
API URL:
http://www.YOUR-VOLUSION-STORE-URL.com/net/WebService.aspx
?
Login=
YOUR-EMAIL@email.com
&
EncryptedPassword=
OIJQWDI324ONIDOIJ234OIH3456POJPOIJH2O34OIH534OIH35O4IH4OIH23IH3O
&
EDI_Name=
Generic\Orders
The API URL, Login, and EncryptedPassword can be plugged into your EFS Integration settings in the next step.
Step 3: EFS Integration Settings
Once you have completed these steps you are ready to set up the integration in your Fulfillment Control Panel account. Choose Add Integration from the Integration menu.
Select Volusion from the list of available platforms and click the “Add new Integration” button.
Login
The login will be the login email address from the last step, which is also your Volusion account login email.
Password
The password is the EncryptedPassword from the previous step.
Note: Volusion generates the EncryptedPassword based on your account password. When you change your Volusion password the integration will be broken until you update the settings with your new EncryptedPassword.
API URL
The API URL should be entered exactly as it appears in the previous step, in this format:
http://www.YOUR-VOLUSION-STORE-URL.com/net/WebService.aspx
Status
The status is the status of orders we will retrieve from your Volusion store. It is most common to use “Ready to Ship” for this status, however any status will work.
Volusion Multi Store ID
If you have multiple Volusion stores you can set each integration to add a custom prefix to each order number as it reaches our system. This will allow us to process orders which have the same order number in separate volusion stores.
Scheduling
The next set of options determine the intervals at which we check for new orders and, optionally, send available inventory counts back to Volusion.
The most common scenario is to check for new orders every 30 minutes and sync inventory twice per day.
If you have more than one Volusion store you may assign a “nickname” to each store to better identify options and settings for each one.
Testing the Connection to Volusion
To verify that we can connect to your Volusion store choose View Integrations from the Integration menu. For each integration you have configured you will see a set of options displayed as colored icons. Click the “suitcase” icon to view the items in your Volusion account.
You should see a searchable list of products from your Volusion store.
Note: This list will only show products from Volusion with SKUs that are an exact match to SKUs in your Fulfillment Control Panel account.
If you do not see a list of products and, instead, see an error message it is likely that your API URL, Login, or Password have been incorrectly entered in the Fulfillment Control Panel integration settings.
Configuring Shipping Options
When we retrieve orders from your Volusion store the shipping method is shown as the ID number for that method (501, 201, etc.). You will need to creating mappings to connect these ID numbers to the shipping service you would like us to use.
You can see a list of all these ID numbers by choosing Shipping from the Settings menu of your Volusion Dashboard, then scroll down and click "View All Shipping Methods" under the Advanced section.
Once you know the ID numbers for the shipping methods you are offering your customers you can add the shipping mappings to your integration settings in the FCP.
From your Fulfillment Control Panel account choose View Integrations from the Integration menu and then click the “envelope” icon to view existing shipping mappings.
Carefully type the exact ID number of your shipping method options from Volusion into the Cart Shipping Method field, then choose from the list of available shipping methods. Next, click the “Add Mapping” button, and then click the link in the success message to refresh the list (you will need to do this before you can add another method).
Note: Be careful not to include any extra spacing when you type your ID numbers or this will cause the mapping to fail.
0 Comments