Mapping 3PL Fulfillment Shipment Methods

The “Fulfillment Settings” page allows you to view and edit all of the shipment mappings you have made in one place. Here are the steps to review/edit shipment methods in the “Fulfillment Settings” page:

Note: If you do not see a shipment method from your 3PL listed on this page, then it means that FarApp has not seen any fulfillments with that shipment method come through the system. You can only map shipment methods for fulfillments that have made it into FarApp.

Note: If you have multiple accounts at your 3PL and multiple connectors in FarApp, you currently can't map the shipping methods for secondary accounts using app.farapp.com. Instead, please follow the instructions in the section below for "Mappings for Multiple Accounts at Same 3PL".

  1. In app.farapp.com, click the gear icon at the top right corner of the screen and click “Settings”.
  2. Click “Fulfillment Settings” at the menu at the left under your 3PL.
  3. If there are multiple 3PLs/accounts, choose the correct 3PL and account using the drop downs at the top. This will display a table with the shipment methods on fulfillments that have imported to FarApp from that 3PL/account. Any orders that come in with new shipment methods will add entries to this table that will need to be mapped.

Here is a direct link to the page: https://app.farapp.com/settings#/3pl_settings/fulfillment_sync/shipment_settings

Refresh Your NetSuite Shipment Methods

The “Fulfillment Settings” page provides you with the ability to reload the shipment methods you have in NetSuite. Here are the steps to accomplish this:

  1. In app.farapp.com, click the gear icon at the top right corner of the screen and click “Settings”.
  2. Click “Fulfillment Settings” at the menu at the left under your 3PL.
  3. Click “Reload NetSuite Shipment Methods” at the top of the screen. Please note that it will take a few seconds for the update to show up in app.farapp.com.

Here is a direct link to the page: https://app.farapp.com/settings#/3pl_settings/fulfillment_sync/shipment_settings

 

Mappings for Multiple Accounts at Same 3PL

In certain situations you may need to map your shipment methods to/from your backend system (e.g. NetSuite) to your 3PL using the IO Map Editor found here:https://www.farapp.com/secure_ExtAjaxController/IOMapEditor.

Mapping shipment methods from your backend system to your 3PL:

  1. Click “Add”. In the new row, set the following values:
    Account -> default
    Type -> ShipmentMethod
    Source -> Your 3PL name (e.g. ShipWorks or Shipwire)
    Target -> Your backend system name (e.g. NetSuite)
    Source Value -> default
    Target Value -> Your default 3PL shipment method
    This default setting will be used on any orders that are exporting from your backend system to your 3PL with shipment methods that haven’t been mapped.
  2. Click “Reload” in the left pane. This loads the shipment methods from orders that have exported from your backend system into FarApp destined for your 3PL. When orders with new shipment methods are imported, you’ll want to reload them so that you can map them.
  3. Click “Unmapped” in the left pane. This filters the shipment methods to ones you haven’t mapped yet.
  4. Hover over one of the headers in the top row, you’ll see an arrow. Click the arrow and under Columns, check “Storefront”.
  5. Click the Storefront header to sort by Storefront.
  6. Look for any rows that have a Storefront value matching your backend system’s name.
  7. Double-click the row which will copy it to the middle pane.
  8. In the middle pane, for the new row (it should be at the bottom) make sure the Account is “default”, the Type is “ShipmentMethod”, the Source is your backend system’s name, and the Target is your 3PL’s name. Click anywhere on the row to select it.
  9. Set the Target Value to the appropriate 3PL shipment methods. You’ll want to make sure it’s a valid value for your 3PL.

Mapping shipment methods from your 3PL to your backend system:

  1. Click “Add”. In the new row, set the following values:
    Account -> default
    Type -> ShipmentMethod
    Source -> Your 3PL name (e.g. ShipWorks or Shipwire)
    Target -> Your backend system name (e.g. NetSuite)
    Source Value -> default
    Target Value -> UNMAPPED
    This default setting will make it so that fulfillments importing from your 3PL with unmapped shipment methods will report an error. You’ll then be able to log into FarApp and map them.
  2. Click “Reload” in the left pane. This loads the shipment methods from fulfillments that have imported from your 3PL into FarApp so far. When fulfillments with new shipment methods are imported, you’ll want to reload them so that you can map them.
  3. Click “Unmapped” in the left pane. This filters the shipment methods to ones you haven’t mapped yet.
  4. Hover over one of the headers in the top row, you’ll see an arrow. Click the arrow and under Columns, check “Storefront”.
  5. Click the Storefront header to sort by Storefront.
  6. Look for any rows that have a Storefront value matching your 3PL’s name.
  7. Double-click the row which will copy it to the middle pane.
  8. In the middle pane, for the new row (it should be at the bottom) make sure the Account is “default”, the Type is “ShipmentMethod”, the Source is your 3PL’s name and the Target is your backend system’s name. Click anywhere on the row to select it.
  9. If you’ve added any new shipment methods in your backend system, click Reload in the right pane.
  10. Double-click the matching row in the right-pane for the backend system shipment method that should be on the fulfillment. This will set the “Target Value” column for the row you have selected in the middle pane.

Comments