Connect Amazon FBA Inbounds to Pipe17

The Amazon FBA Inbounds connector pulls inbound transfer orders from Amazon into the app. Transfers are created directly in Amazon and pulled into the app so the shipping request can be routed to other warehouse channels or an ERP. Use this connector when Amazon FBA inbound shipments need to drive downstream fulfillment in your other connected systems.

Key capabilities:

Pull warehouse and fulfillment center locations from Amazon.
Pull FBA inbound orders from Amazon as transfer orders in the app.
Pull receipt information from Amazon as inventory arrives at fulfillment centers.

Setup

Before you begin:

Have a Pipe17 account.
Confirm you are licensed for the Amazon FBA Inbounds connector. Contact your Pipe17 representative if you are unsure.
Have admin access to the Amazon Seller Central account you want to connect.

To connect Amazon FBA Inbounds:

Sign in to the app and select Integrations in the left navigation.
Click Add Integration.
Select the Amazon FBA Inbounds connector.
Enter your Marketplace.
Confirm you are signed in to the correct Seller Central account, then click Connect. If prompted, sign in to the Amazon Seller Central account you want to connect.
In the Seller Central authorization window that opens, click Confirm to grant the requested permissions.
Verify the connector status displays Connected.
Open the Settings tab within the connector and configure the flows described in the next section.

Settings

Enable or disable individual flows at the top of the settings page. Flow-specific configuration appears in the lower portion of the same page.

Pull receipt information from Amazon Pulls receipts available since the last successful pull. Receipts are processed each hour based on the presence of expected or partially received arrivals in the app.

Pull FBA inbound orders from Amazon and use them to create Pipe17 transfer orders Pulls transfer orders available since the last successful pull from Amazon. Configure the flow-specific settings below.

Setting	Description	Default
Date filter	Pulls orders created on or after this date.	The date the connector was installed
Order ID filter	Pulls only the specified Amazon order ID instead of all orders in the date range.	Off
Process FBA inbound orders if transportation option is not selected	When enabled, orders are pulled before the transportation or carrier info is selected in Amazon.	Off — orders are only pulled after carrier info is selected
Process FBA inbound orders if source location or destination address cannot be resolved	When enabled, orders are pulled even if the app cannot resolve the source or destination location, and they are assigned Draft status until the missing location information is supplied.	Off — unresolvable orders are not pulled
Automatically mark created transfers as fulfilled when source location is not linked with the fulfillment channel	When enabled, the FBA inbound order is marked fulfilled and ready for receipt collection. Use this when fulfillment of the inbound shipment occurs outside the app.	Off

Pull locations from Amazon Pulls the warehouse and fulfillment center list from Amazon. This flow should remain enabled so the connector can resolve Amazon locations. Once enabled, it cannot be disabled.

Flows

Flow	Direction	Notes
Locations	Amazon → Pipe17	Required so the connector can resolve Amazon warehouse and fulfillment center locations. Cannot be disabled once enabled.
Transfer orders	Amazon → Pipe17	Pulls FBA inbound orders and creates corresponding transfer orders in the app. By default, orders are only pulled after carrier information is selected in Amazon.
Receipts	Amazon → Pipe17	Pulled hourly based on expected or partially received arrivals.

Flow example

The table below shows an end-to-end flow that uses the Amazon FBA Inbounds connector to drive a transfer order through NetSuite and a 3PL, then records the receipt back into NetSuite when the inbound is received at Amazon.

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 the MCF location; (b) create a new location manually, directly on the 3PL location, using integration = MCF and ID = any value. Ensure the 3PL location ZIP code matches the ship-from ZIP on the transfer order. See video walkthrough. Link the NetSuite Ecom and ERP locations to this 3PL location so the connector knows which location to use when creating the TO in NetSuite. 2. Enable the flow in the Amazon FBA Inbounds connector settings to pull inbound shipments from Amazon.	1. Create the inbound in Amazon. 2. Create the shipping label — at this step an FBA order number is assigned and the order can be pulled into the app.	Transfer order is pulled into the app.
NetSuite ERP	Push TO	1. Enable the flow in the NetSuite ERP connector settings to push transfer orders to NetSuite. 2. Modify mappings for custom form ID, subsidiary ID, and shipping method ID.	None — automatic.	Transfer order is created in NetSuite without error.
3PL	Push shipping request	Runs simultaneously with the NetSuite ERP push. 1. Modify the filter in the 3PL connector settings if filtering to a specific number. 2. Enable the flow in the 3PL connector settings to push shipping requests to the 3PL.	None — automatic.	Shipping request is generated in the app and sent to the 3PL.
3PL	Pull fulfillment	Enable the flow in the 3PL connector settings to pull fulfillments from the 3PL.	Fulfill the order in the 3PL.	Fulfillment information and tracking number appear on the transfer order in the app.
NetSuite Ecommerce	Push fulfillment	Enable the flow in the NetSuite Ecommerce connector to push item fulfillments to NetSuite.	None — automatic.	Item fulfillment is created against the transfer order in NetSuite.
Amazon	Pull receipt	Enable the flow in the Amazon FBA Inbounds connector to pull receipts from Amazon.	Receive the order in Amazon.	Receipt is recorded against the transfer order in the app.
NetSuite Ecommerce	Push receipt	Enable the flow in the NetSuite Ecommerce connector to push receipts to NetSuite.	None — automatic.	Order is received in NetSuite.

Troubleshooting

FBA inbound orders are not being pulled into the app
By default, the connector waits until a transportation option and carrier are selected on the Amazon shipment before pulling the order. Confirm the shipping label has been created in Amazon, or enable Process FBA inbound orders if transportation option is not selected if you need orders pulled earlier in the workflow.
Transfer orders arrive in the app with Draft status
Draft status indicates the source or destination location could not be resolved at the time of pull. Verify that the relevant Amazon and warehouse locations are configured and mapped, then update the transfer order with the correct locations.
Connector status shows Disconnected after authorization
The Selling Partner authorization token may have expired or been revoked in Seller Central. Reauthorize by opening the connector and clicking Connect again, then confirm the status returns to Connected.
Amazon locations are missing from the app
Confirm that Pull locations from Amazon is enabled in the connector settings. This flow is required to resolve source and destination locations on inbound transfer orders.
Receipt quantities do not match shipped quantities
Amazon reconciles received units over several days after delivery. Wait at least 72 hours after the shipment changes to a receiving state before investigating. If a discrepancy remains after the shipment is closed in Amazon, open a reconciliation case in Seller Central and contact Pipe17 support with the transfer order ID.

Need Help?

If you need additional assistance:

Use Ask Pippen, our AI agent, located at the top of the app page.
Submit a support request with as much relevant detail as possible. Learn how to submit a request.
For urgent issues, email us directly at support@pipe17.com.