ShipStation Integration

Integration Steps

SellerCloud is integrated to ShipStation as a Custom Store.

  1. In Ship Station go to Connect a Selling Channel. Then, select Custom Store from the options.
  2. Enter the credentials needed to connect to SellerCloud. URL to Custom XML Page:
    The 'xx' can be replaced with your server id. For example if your SellerCloud URL is usually the 'zz' is your server id.
    • The Username and Password should be the credentials to SellerCloud with which you wish to ship.
    • Most of the status' can be left as is besides the 'Paid Status' which should be set to 'InProcess'
  3. Go to the Orders page, and Sync the store, then the order should come in. The sync button can be found on the top right of the page,  left of the settings button.
  4. Upon Shipping the order, a call will be sent to SellerCloud, with all pertinent data, and the order will be marked as shipped in SellerCloud. By default the orders which ShipStation pulls from SellerCloud, have a last modified date between the start date and end date which ShipStation send in the request. They also fit the following criteria:
    •  Order is Charge (or the order is set to Allow Shipping Even if Not Paid)
    •  DropShip status should be None
    • Order Status should be InProcess
    If there are specific orders that you would like to be sent to Shipstation, you can make a saved seach to select the orders which you would like to send to ShipStation.
    1. Create an Order Saved Search with the filters you would like to be used when sending orders to ShipStation
    2. Create custom setting: "ShipStation Saved SearchID". (custom settings are located in your company Toolbox > Custom Settings)
      Note: This is the Saved Search ID, not the name of the search. Please contact SellerCloud Support in order to check for the correct ID.
    3. Put the search ID of the search which you would like to use in that setting.
    4. As long as there is a search Id in that setting, we will use that search to pull the orders.

    You can see the requests sent by Shipstation in the action documents on the order.
    Note: IF the items in the order are UNKNOWN then the order will NOT go through to ShipStation.

Integration of Multiple ShipStation Accounts

SellerCloud offers a way to integrate multiple ShipStation accounts. Follow the steps carefully and request assistance from SellerCloud Support if necessary.

  1. Create a new SellerCloud Employee for each ShipStation account you would want to link.
    Important: This Employee UserName and Password will be used when setting up the custom store on ShipStation.
  2. Create Saved Searches for the orders that you'd like to pull for each Shipstation Account
  3. Each ShipStation account should be linked to its own company. If the accounts are not company specific, you should create companies to keep the necessary info in.
  4. For each ShipStation account:
    • In the company created for this account, create the custom setting:  "ShipStation Saved SearchID" (this will require Client Setting Enable Custom Company Settings to be enabled)
    • In this setting put the saved search ID for the orders that are required for this account. (SellerCloud support can help with getting the ID's for clients). 
    • On the employee in SellerCloud that is being used in Shipstation, set the companyID to the company being used to pull the orders.
Please note: If you are using multiple accounts, and you are using login credentials that do not belong to a company that has a saved search set, all orders for that client will be sent. 

Fields sent to ShipStation

    1. Shipstation OrderID and OrderNumber are both mapped to the SellerCloud OrderID.
    2. Internal Notes contain the ShipBy date (OrderShippingPromiseDate) if one was provided by the channel.
    3. We pass through if its a gift order, and if there is a gift message.
    4. CustomField1 = OrderSource (and Subtype if there is one)
    5. CustomField2 = OrderSourceOrderID
    6. CustomField3 = SellerCloud CompanyName
    7. Shipping & Billing Address, TimeOfOrder, Shipping & Payment method etc. are all mapped as would be expected
      = Mapped as standard. 

    How did we do?