In this article
Overview
The Amazon FBA Inbounds connector is primarily used when you are pulling inbound transfer orders from Amazon to Pipe17. The transfers are created in Amazon directly, and can be pulled into Pipe17 to sync the shipping request out to other warehouse channels or an ERP
Supported flows
-
Basic
- Pull locations from Amazon
- Pull transfer orders from Amazon
- Pull receipts from Amazon
Flow example
Getting Started
- Ensure that you have a Pipe17 account created
- Make sure you are licensed to use the Pipe17 Amazon FBA Inbounds Connector. If you're not certain, reach out to your Pipe17 rep
Connector Setup
Get connected to the Amazon FBA Inbounds connector
-
- In Pipe17, go to the "Integrations" tab on the left side of your Pipe17 portal, and click "Add Integration"
- Select the Amazon FBA Inbounds connector
- Input your marketplace
- If you have access to multiple Seller Central accounts, make sure you are logged into the correct one. Click the "Connect" button, and if prompted, log into the Amazon Seller Central account you want to connect.
- A Seller Central window will open in your browser, prompting you to Authorize Pipe17. Click "Confirm" to give Pipe17 the requested Amazon Seller Central Account permissions.
- Once credentials are successfully entered, and the connector status shows "Connected" click over to the "Settings" tab within the connector. Step through the settings below
Settings configuration
Enabling and disabling flows can be configured with the options at the top of the settings page. The settings on the bottom portion of this page are more specific configurations for each flow
Follow for our suggested setup process for most common use cases
-
Pull receipt information from Amazon
- Pulls in receipts available after the last successful pull. Receipts are processed each hour based on presence of expected or partially received arrivals in Pipe17
-
Pull FBA inbound orders from Amazon and use them to create Pipe17 Transfer orders
- Pulls transfer orders available since last successful pull from Amazon
- Specific settings (bottom half of same page)
- Filters:
- Use the date filter in section below to input a date if something other than the date the connector was installed is required. This will tell Pipe17 to only pull from that date onward
- Option to use the filter below this to input a specific order ID for Pipe17 to pull instead of allowing all orders since the date to be ingested
- Process FBA inbound orders if transportation option is not selected
- By default, we don't pull orders until the transportation / carrier info is selected
- Process FBA inbound orders if source location or destination address cannot be resolved
- While pulling FBA inbound orders, Pipe17 will resolve source and destination locations for such order. If resolution can not be performed (e.g. locations are not configured, missing or ambiguous), then by default Pipe17 will not pull the order. However if this switch is enabled, order will be pulled and assigned Draft status - to indicate that proper locations information will have to be provided by user
- Automatically mark created transfers as fulfilled when source location is not linked with the fulfillment channel
- When this mode is enabled, FBA inbound order will be marked as fulfilled and ready to collection of receipt information. Use this mode when fulfillment of FBA inbound is done outside of Pipe17
- Filters:
-
Pull locations from Amazon
- Cannot be disabled once enabled, but should always be enabled to allow Pipe17 to see locations/warehouse list from Amazon
Testing
Connector | Step | Configuration | Test Step | Expected Result |
Amazon | Pull TO/inbound |
1. Ensure locations are properly linked (a) link NetSuite Ecom and ERP locations to MCF location (b) then create a NEW location manually, directly on the 3PL location using integration = MCF, ID = any value; ensure 3PL location zip code matches the ship from zip code on the TO VIDEO LINK. Also, make sure to link NetSuite Ecom and ERP locations to this 3PL location - this ensure the connector know which location to use when creating the TO in NS. 2. Enable flow in Amazon MCF connector settings to pull inbound shipments from Amazon |
1. Create inbound in Amazon 2. Create shipping label - at this step is when an FBA order number is assigned, and order can be pulled into Pipe17 |
TO is pulled to Pipe17 |
NetSuite ERP | Push TO | 1. Enable flow in NetSuite ERP connector settings to push transfer orders to NetSuite 2. Modify mappings for: custom form ID, subsidiary ID, shipping method ID |
None - automatic | TO created in NetSuite without error |
<3PL> | Push shipping request | *Simultaneous as above flow 1. Modify filter in <3PL> connector settings if filtering to specific # 2. Enable flow in <3PL> connector settings to push shipping requests to <3PL> |
None - automatic | Shipping request is automatically generated in Pipe17 and sent to <3PL> |
<3PL> | Pull fulfillment | 1. Enable flow in <3PL> connector settings to pull fulfillments from <3PL> | 1. Fulfill order in <3PL> | Fulfillment info + tracking number shows in Pipe17 TO |
NetSuite Ecommerce | Push fulfillment | 1. Enable flow in NetSuite Ecommerce connector to push item fulfillments to NetSuite | None - automatic | Item fulfillment created against TO in NetSuite |
Amazon | Pull receipt | 1. Enable flow in Amazon MCF connector to pull receipts from Amazon | Receive order in Amazon | |
NetSuite Ecommerce | Push receipt | 1. Enable flow in NetSuite ecommerce connector to push receipt to NS | None - automatic | Order gets received in NS |
Comments
0 comments