You chose Fulfillment by Amazon (FBA) to focus on growing your business rather than managing warehouse operations. 78% of Amazon sellers use FBA for exactly this reason (AMZ Prep, 2025).
If you’re using middleware platforms, custom API connections, or manual processes to connect FBA with your ERP, you’re managing an additional system layer. You’ve automated order flow, but you’re maintaining integration dependencies between separate systems while missing the operational capabilities that FBA sellers need to scale profitably.
FBA isn’t just “Amazon fulfillment.” It’s a specific operational model with unique requirements that most ERP integrations treat as an afterthought.
Amazon launched MCF to let you use FBA inventory to fulfill orders from Shopify, Walmart, and other platforms. 93% US zip code coverage for same/next-day delivery at $3.64 per item for 4+ item shipments makes this economically viable (Amazon MCF, 2025).
But here’s the operational challenge: your ERP needs to route non-Amazon orders to FBA for fulfillment, track that inventory separately, reconcile MCF fees, and manage the relationship between your available inventory and multiple fulfillment locations. Generic integrations sync Amazon orders to your ERP; they don’t orchestrate multi-channel fulfillment FROM your ERP.
Amazon charges referral fees (8-15% depending on category), FBA fulfillment fees (varying by product size and weight), Inbound Placement Service Fees ($0.21-$6.00 per unit), Low-Inventory-Level Fees ($0.89-$1.11 per unit for under 28 days supply), storage fees (by season and product age), aged inventory surcharges (starting at 181 days), returns processing fees, and dimensional weight pricing that affects 66% of packages (BrandsBro, 2025; Red Stag Fulfillment, 2025).
Many sellers use both FBA and FBM (Fulfillment by Merchant) for different products or during different seasons. 34% of Amazon sellers partner with FBM service providers, and 22% use both FBA and FBM services (AMZ Prep, 2025).
Your ERP needs to handle both fulfillment methods appropriately based on their different operational requirements. FBA orders need automated posting since Amazon already handled fulfillment, while FBM orders need full Business Central fulfillment workflows.
Most businesses approach Amazon ERP integration through middleware platforms. These platforms excel at connecting disparate systems, but they weren’t designed specifically for FBA’s operational requirements.
Generic middleware handles order synchronization well. What they don’t handle well: Multi-Channel Fulfillment orchestration from your ERP, automated inbound shipment planning, FBA-specific fee categorization and posting with transaction-level detail, and intelligent automation that handles FBA and FBM orders based on their different operational requirements.
When Amazon updates its Selling Partner API specifications (which happens regularly), your middleware provider needs to update their integration. When your ERP releases updates, you need to verify middleware compatibility. You’ve added a dependency layer that introduces potential failure points and maintenance overhead.
Most middleware platforms sync revenue totals without breaking down individual fee types. You see that Amazon sent you $42,000 in a settlement, but you don’t see the $3,200 in FBA fees, $850 in storage charges, $1,100 in advertising costs, and $420 in aged inventory surcharges that reduced your actual take-home.
Your accounting team can see total deposits, but they can’t trace fees to specific transactions without manual analysis. This makes it difficult to understand your true costs and assess profitability.
Channel Sales Manager (CSM) is embedded in Dynamics 365 Business Central, addressing FBA’s unique operational requirements without middleware.
CSM converts orders from connected platforms into Business Central orders. For Shopify orders, those Business Central orders can then be fulfilled through Amazon MCF. You define the business rules: which products fulfill through FBA, which ship from your warehouse, and how to handle products available in both locations.
When a Shopify customer orders a product that exists in your FBA inventory, CSM automatically creates the MCF fulfillment request. Amazon handles the pick, pack, and ship. Your customer receives Prime-level delivery speed without knowing the order originated outside Amazon. Your Business Central inventory updates across all channels based on your configured sync schedule.
This isn’t just order routing; it’s unified inventory management where one inventory pool serves multiple sales channels through Amazon’s logistics infrastructure.
CSM captures every Amazon financial event at the transaction level, posting to appropriate general ledger accounts in Business Central. FBA fulfillment fees, storage charges, placement fees, low-inventory penalties, and advertising costs all appear as distinct line items in your financial records.
This provides the detailed financial data your team needs to analyze profitability. You can see exactly which fees are being charged, track how storage fees accumulate on slow-moving inventory, and make informed decisions based on complete cost visibility. With all fee types properly categorized, you have the foundation for profitability analysis using your existing Business Central reporting and analysis tools.
CSM configures FBA and FBM orders differently based on their operational requirements. FBA orders typically auto-post in Business Central since Amazon already handled fulfillment; you’re tracking inventory and financials automatically. FBM orders use Business Central’s full fulfillment workflows since you’re managing the pick, pack, and ship process. You can shift products between FBA and FBM based on seasonality, inventory turns, or fee structures, with CSM applying the appropriate automation for each method.
The system tracks which orders are FBA (auto-posting for financial and inventory tracking) and which are FBM (using Business Central fulfillment workflows). During high-volume periods, you might shift products to FBA to leverage Amazon’s capacity. During slower periods, you might fulfill those same products yourself to avoid storage fees.
This flexibility exists in the configuration. CSM automatically applies the appropriate automation when you change a product’s fulfillment method.
CSM synchronizes FBA inventory levels, inbound shipment status, and warehouse on-hand quantities into Business Central. You see available-to-promise inventory across all locations, which prevents overselling across channels while enabling leaner inventory management.
When you create an inbound shipment to FBA, the system tracks that inventory as “in transit to FBA” until Amazon confirms receipt. Your available inventory for non-FBA orders remains accurate, and your Amazon available quantity updates automatically once FBA receives the shipment.
This inventory visibility extends across all your connected sales channels. When you sell a unit on Walmart, your Amazon available quantity adjusts. When FBA inventory drops below reorder thresholds, Business Central purchasing workflows trigger automatically.
Business Central’s job queue functionality automates routine FBA tasks: inventory synchronization, order retrieval, and shipment confirmations. These processes run continuously in the background without manual intervention.
As you add sales channels (Walmart, BigCommerce, your own Shopify store), CSM extends the same integration model to each platform. Your FBA inventory remains the unified fulfillment pool. Your financial reporting continues to consolidate all channels into Business Central. You’re not managing multiple integrations; you’re managing one system with multiple channel connections.
If you’re doing $500,000+ through FBA, or planning to reach that level, your integration strategy determines whether you scale profitably or plateau under operational complexity:
These aren’t minor convenience features; they’re the operational capabilities that separate FBA sellers who scale profitably from those who hit revenue plateaus because their systems can’t support additional complexity.
When evaluating FBA integration options, you’re choosing between two fundamentally different architectural approaches:
If you’re using Business Central and currently managing FBA through manual processes, basic API connections, or middleware platforms, assess your current integration approach:
Channel Sales Manager addresses these FBA-specific requirements as a fully integrated component of Business Central. You can explore CSM’s capabilities through Microsoft AppSource or request a demonstration focused on your FBA volume and operational needs.
FBA gives you access to Amazon’s logistics infrastructure. Fully integrated Business Central functionality gives you the operational foundation to use that infrastructure profitably across multiple sales channels, with full financial visibility and unified inventory management.
Using Business Central and running FBA operations? Request a CSM demonstration focused on Multi-Channel Fulfillment, fee tracking, and financial visibility specific to your FBA volume and operational requirements.
SUITE ENGINE | We connect your business with modern software from Microsoft.
Simplified processes. All in one place.
Payment Processing | eCommerce Connectors | and more …