Overview
Sellercloud offers two methods to automate your Amazon Multi-Channel Fulfillment (MCF):
Configure rules with the Ship via FBA action through the Order Rule Engine.
Use a Ship via FBA post-order plugin installed and configured by Sellercloud Support.
The Ship via FBA action allows you to automate Amazon Multi-Channel Fulfillment (MCF) through the Order Rule Engine. By adding this action to a rule, you can automatically submit eligible orders to Amazon for fulfillment without relying on custom post-order plugins. The action's settings allow you to define how fulfillment requests should be processed, including whether local inventory should be prioritized, how kits are handled, how shipping speeds are selected, when orders should be split, and how ineligible items or failed fulfillment requests should be managed.
Sellercloud's Ship via FBA post-order plugins provide another way to automate Amazon MCF fulfillment. Based on predefined plugin logic, the system automatically evaluates inventory availability, determines whether products should be fulfilled from local inventory or FBA inventory, and submits eligible orders to Amazon for fulfillment after order creation.
Do not use a Ship via FBA Rule Engine action and a Ship via FBA post-order plugin at the same time. Running both automation methods may result in the same order being submitted to Amazon more than once.
Ship via Order Rule Engine
You can configure the Ship via FBA action through the Order Rule Engine to prioritize local inventory, process kits, split orders when necessary, determine shipping speeds, and define how Sellercloud should handle ineligible items or failed fulfillment requests. Once an order meets the conditions defined in your rule, Sellercloud evaluates the order according to the action settings and submits eligible items to Amazon. All fulfillment decisions, order splits, and Amazon responses are recorded in the order notes and the Rule Engine Execution Log.
Requirements and Considerations
Before you create a Ship via FBA rule, verify that your Amazon integration and FBA inventory are properly configured.
The action requires:
A configured Warehouse Channel that connects your Amazon account to its corresponding FBA warehouse in Sellercloud. This mapping allows Sellercloud to identify available FBA inventory and route fulfillment requests to the correct Amazon fulfillment network.
Products with valid FBA SKUs in an Amazon account that serves the order's Ship To country. Orders can only be submitted when products have valid FBA SKUs and available FBA inventory in an Amazon account that matches the order's destination country.
Available FBA inventory for the products being fulfilled. The action is designed to submit only items that Amazon can fulfill from available FBA inventory. If the client setting Do not validate merchant SKU when shipping via FBA is enabled, Sellercloud skips the inventory validation step and submits the order directly to Amazon.
Keep the following considerations in mind:
If you currently use a post-order plugin that automatically ships orders via FBA, disable it before enabling a Ship via FBA rule.
Ship via FBA does not support Walmart orders, WFS, and other fulfillment networks.
Orders that are Partially Shipped, Fully Shipped, On Hold, Cancelled, or already submitted to another drop-ship source are skipped automatically.
Digital products are never submitted to Amazon and always remain on the original order.
APO/FPO/DPO addresses and unsupported destination countries are not eligible for fulfillment.
The Blank Box and Block Amazon Logistics options are only supported for eligible US Amazon accounts using Selling Partner API.
-
The Ship via FBA action does not automatically exclude:
FBA-channel orders - If the rule should only process non-Amazon orders, leave Process FBA Orders disabled.
Local Store or Wholesale orders - If needed, add a Channel Is Not In condition to your rule.
Create Ship via FBA Rule
To create a rule that includes the Ship via FBA action:
Navigate to Settings > Orders > Rule Engine > Manage Rules, and click the plus sign in the Rules panel to create a new rule.
Enter the Rule Name and click the arrow to proceed.
Click the plus sign in the Conditions panel to add a top-level condition.
Specify the Condition Name and Condition Type, and click Add. Once done adding conditions, click the arrow to proceed.
Click the plus sign in the Actions panel.
Add an Action Name, select Ship via FBA for Action Type, and configure all required Action Settings.
Once done, click Add and select the Save button to create the new rule.
A common setup for non-Amazon orders includes the following configuration:
Conditions:
Channel is not FBA, Local Store, or Wholesale.
Shipping Address Country is the US.
Payment Status is Charged.
Actions:
Ship via FBA;
Items FBA Can't Ship: Split them off;
Outcome for the Split-Off Order: Set On Hold.
Action Settings
The Ship via FBA action includes the following settings:
SETTING |
DESCRIPTION |
Check Local Warehouses First |
Checks selected warehouses before evaluating FBA inventory. Items that can be fulfilled locally remain local instead of being sent to Amazon. |
Items FBA Can't Ship |
Choose whether to split ineligible items into a separate order or skip the entire order. |
Outcome for the Split-Off Order |
Leave the order unchanged, place it On Hold, or add it to an Order Group. |
Split by Amazon Account |
Creates separate MCF orders when inventory is located in different Amazon accounts. |
Kits |
Controls how kit products are handled during fulfillment:
|
Shipping Speed |
Maps shipping services and order characteristics to Amazon fulfillment speeds. By default, Sellercloud applies the following mappings:
|
Always Use Speed |
Overrides the shipping speed mapping and always uses the selected speed. |
Retry at Standard if Amazon Rejects the Speed |
Resubmits the request once using Standard speed if Amazon rejects the selected speed. |
Blank Box |
Controls Amazon's blank-box packaging option. |
Block Amazon Logistics |
Controls whether Amazon Logistics can be used to deliver the order. |
On Failure: Set On Hold |
Places the order On Hold when submission fails. |
On Failure: Reset Ship-From To |
Resets the Ship From warehouse when fulfillment fails. |
On Failure: Add To Order Group |
Adds failed orders to a selected Order Group. |
You can modify existing mappings or add custom keyword rows to support additional shipping methods.
Review Results
After the Ship via FBA action runs, Sellercloud records the fulfillment outcome and any responses received from Amazon.
When Amazon accepts a fulfillment request, Sellercloud updates the order, sets the Drop Ship Status to Requested, assigns the appropriate FBA warehouse, and saves the Amazon request and response files.
If Amazon rejects the fulfillment request, Sellercloud applies the configured failure actions and records the reason in both the order notes and the Rule Engine Execution Log.
Use the following locations to review processing results and troubleshoot issues:
Order Notes for item eligibility decisions, order splits, shipping speed selection, and Amazon responses.
Toolbox > Action Documents for Amazon request and response files.
Rule Engine > Execution Log for rule execution details and failures.
Selling Partner API logs for outbound Amazon requests.
Related Settings
The following settings can affect how the Ship via FBA action behaves:
SETTING |
DESCRIPTION |
Ship via FBA Defaults |
Company Setting. Defines channel-specific defaults for Blank Box and Block Amazon Logistics. When the action is configured to use channel defaults, Sellercloud applies the settings configured on this page for the order's sales channel. |
Run Order Rules and Post order plugin after split order |
Client Setting. Determines whether orders created through splitting are reprocessed by the Rule Engine. This is particularly important when Ship via FBA is used together with workflows that split orders before they are submitted to Amazon. |
Do not validate merchant SKU when shipping via FBA |
Client Setting. Skips FBA inventory validation before submitting a fulfillment request. When enabled, Sellercloud submits the order to Amazon without verifying whether sufficient FBA inventory is available. |
Ship via Post-Order Plugins
A post-order plugin can also offer an automated Amazon Multi-Channel Fulfillment process. Sellercloud supports various generic plugins designed to automatically evaluate inventory availability, determine whether products should be fulfilled through Amazon, and submit eligible orders to Amazon MCF without manual intervention. These plugins are built to verify the default warehouse quantity of every item in each order. If there is no quantity, they check if that SKU has an AFN counterpart (Amazon Fulfilled shadow or parent) that has quantity in an FBA warehouse. You have the option to choose from pre-existing options or request additional customizations/new plugins tailored to your specific requirements.
Open a ticket with Sellercloud Support to have such plugins installed and configured on your server, or if you wish to explore other plugin customization options.
FBA SplitByCompany With Kit Support Format is Sellercloud's most advanced Ship via FBA post-order plugin. It supports standard products, kit products, local-inventory-first fulfillment strategies, and fulfillment across multiple Amazon companies.
By default, this plugin excludes:
Local Store
FBA
Wholesale
Walmart Marketplace orders
However, to override the hardcoded logic and determine which channels should be skipped, you can create and use the optional custom setting ChannelsToExcludeFromFBAPOP to add comma-separated Channel IDs.
The following Custom Company Settings are required:
ConsiderLocalWHInvBeforeFBAInPostOrderPlugin - Select value True or False. If set to True, the plugin will check the value in FBMWarehouseIDsToConsiderBeforeShippingViaFBA and will try to allocate the order to the nearest warehouses set there, before checking FBA inventory. When set to False, the plugin will ignore all local warehouse inventory and will check FBA inventory directly.
FBMWarehouseIDsToConsiderBeforeShippingViaFBA - List of local FBM warehouses to check, if the above setting is True. The warehouse IDs must be separated by a semicolon.
This plugin aims to keep kit shipments whole, so if one kit item is available in local storage and also in the FBA warehouse, and the other kit item is available only in FBA, then the plugin will ship it via FBA, even if the ConsiderLocalWHInvBeforeFBAInPostOrderPlugin setting is enabled.
If there are multiple items in the order that should be shipped via FBA, those items are split and combined into a single new order (rather than separate ones). However, if two items in the order are available in the FBA inventory of two different companies, the plugin will then split them accordingly and ship each item via the company where the respective items are in stock.
All kit components should be eligible for shipment through the same company's FBA services. If one component has available FBA inventory in a SKU from Company A, and the second component has available FBA inventory in a SKU from Company B, then the plugin will not ship the kit via FBA.
This plugin also takes your Company’s Ship via FBA Defaults settings into account. For further information, refer to the Amazon Multi-Channel Fulfillment – Feature Constraints article. You can also utilize the following Optional Custom Company Settings:
ShipAllMCFOrdersAsPriority - Values True or False. If the value in the company of the order is set to True, orders will be sent with a shipping method Priority.
DoNotAllowShippingViaFBAForInternationalOrders - Values True or False. If you set the value to True, international orders will not ship via FBA.
DoNotShipViaFBA_ChannelIds - The ChannelID is a numeric value (full list of Channel IDs). This setting is used to list channels to be skipped in addition to the channels that the plugin is hard-coded to skip (LocalStore, FBA, Wholesale, and Walmart Marketplace). In contrast to ChannelsToExcludeFromFBAPOP, this setting aims to add further restrictions. As of v1.0.2.3, ChannelsToExcludeFromFBAPOP can be used to override those restrictions instead.
Rush Orders will be sent with shipping method Expedited, unless overwritten by the shipping service selected on the order. If the shipping service selected on the order is 1D (one day), Overnight, or NextDay - the order will be sent as Priority. If the shipping service selected on the order is Priority, 2ND, or 2D - the order will be sent as Expedited.
Company Plugin Setup
The example below illustrates the configuration and setup for Sellercloud’s FBA SplitByCompany With Kit Support Format post-order plugin in your company:
Navigate to Settings > Companies > Manage Companies and open a company.
From the Toolbox, choose Defaults.
Click Edit.
In the Order Post Action Plugin dropdown, you may see FBA Format, but note that this plugin ignores kits. It is recommended to select the more advanced plugin version FBA SplitByCompany With Kit Support Format, described above.
Click Save.
Plugin Setup via Order Rules
Another option to execute a Post Order plugin is to configure a set of rules via Sellercloud’s Order Rule Engine.
Client Setting Enable Rule Engine Action For Post Order Plugin must be enabled for this workflow!
Create a Saved View with orders to Ship via FBA, and then add a new rule:
Navigate to Settings > Orders > Rule Engine > Manage Rules.
Click Add New Rule.
Enter the Rule Name and enable the Process FBA Orders checkbox.
Click the arrow to proceed to Conditions.
Add a new condition via the + sign. Enter the Condition Name, select Condition Type - Order Saved View, add Comparison Operator, choose User, and select a Saved View.
Click Add and proceed to Actions.
Enter the Action Name, choose Action Type - Execute Post Order Plugin, and select the FBA Format plugin. Click Add.
Click the Save button to create the new rule, and remember to enable it.