Import sales and send to Amazon MCF automatically
Using Amazon MCF streamlines your fulfillment process. With the settings described in this article, make the workflow from sale to delivery even smoother, automating the import of sale orders from your eCommerce channels and passing them directly to Amazon MCF for fulfillment.
Prerequisites
Fulfillment by Amazon integration must be connected, which requires a Connection license to be included in or added onto your subscription.
Connect sales channels
Amazon FBA settings
The first series of settings to configure are found within your Fulfillment by Amazon integration in Cin7 Core. Locate them by going to Integrations → Fulfillment by Amazon, select your marketplace, and then the Setup tab.
- Select Every day for auto-sync stock with FBA to ensure orders are synced ready for timely delivery.
- Select a specific time to sync stock with Amazon FBA. We recommend setting a time that is the least busy in your business schedule.
- Process fulfillment orders should be disabled, so that orders are automatically sent to Amazon MCF as soon as the shipment for the order is authorized, rather than processed in Core.
- Create FBA fulfillment orders with Shipped status, to ensure fulfillment orders are sent to Amazon MCF and not kept 'on hold'.
- Next, configure the Amazon MCF settings to select default packaging and logistics values for sales orders coming from your connected eCommerce channels and marketplaces.
Sales channel integration settings
Next, you will need to configure some settings from your eCommerce channel or marketplace integration settings. Some of these are applicable to every channel, and some are dependent on your number of fulfillment locations. Shopify has special settings.
The following setting applies to all channels which send orders to Amazon MCF for fulfillment. Pick, pack, and ship process mode for online sales should be set to auto pick + pack or auto pick + pack + ship. This will automatically pick and pack the article from your fulfillment location.
Steps for Shopify
Shopify settings allow you to map your Amazon FBA warehouse to a Shopify location while maintaining your other location mappings.
In Shopify, add a new location for Amazon FBA.
In Cin7 Core, go to your Shopify integration, load locations from Shopify, and map the FBA location in Shopify to the corresponding location in Core.
Single fulfillment location settings
If your eCommerce/marketplace integration is only fulfilled from a single location, your FBA location, set Location for online sales as your FBA location. This setting can be found on the Setup tab of your sales channel integration.
Multiple fulfillment location settings
If you fulfill orders for this sales channel both from your FBA location but also one or more other locations, we recommend using Core's order routing functionality and route to the FBA location accordingly.
Note: If you have multiple fulfillment locations for your integration, but only certain products are stocked at the FBA location, then you can set Link WooCommerce/Magento to Cin7 Core location to All locations. This setting is only applicable for WooCommerce and Magento.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB