Connecting Amazon FBA to Cin7 Core creates an external fulfilment location that can hold Amazon stock, receive fulfilment orders and return stock and tracking updates to Cin7 Core. Amazon Multi-Channel Fulfilment (MCF) extends the same network to orders from non-Amazon channels such as Shopify or WooCommerce. A reliable setup depends on consistent SKUs, accurate product mapping, a controlled initial stocktake, channel-specific fulfilment rules and regular exception monitoring. Cin7 Core can automate much of the order and inventory flow, but inbound FBA shipments remain managed in Seller Central, shipping authorisation cannot be fully automated for external fulfilment orders, and FBA returns need a separate process.
Key takeaways:
- Connect the Amazon selling channel and FBA fulfilment service as related but distinct parts of the workflow.
- Treat the FBA connection as a dedicated external Cin7 Core inventory location; do not mix it with stock held in your own warehouse.
- Match SKUs before enabling automatic product mapping or stock updates.
- Complete an initial stocktake to establish the correct FBA quantity in Cin7 Core before live orders begin to flow.
- Use MCF to fulfil Shopify, WooCommerce and other off-Amazon orders from Amazon stock, with packaging and carrier rules set per channel.
- Test cancellations, split shipments, stockouts, failed addresses, tracking and returns—not only a successful order.
Selling through Amazon while also operating a website, wholesale channel or marketplace account can create a deceptively difficult inventory problem. The same units may be visible to several channels, orders arrive in different formats and fulfilment may take place in your own warehouse, at Amazon or through another 3PL.
Without a clear system of record, teams start comparing reports, adjusting stock manually and discovering discrepancies only after an order has failed. Connecting Amazon FBA and MCF to Cin7 Core brings those flows into one inventory and order management process—but only when locations, products and channel rules are configured deliberately.
This guide explains how FBA and MCF fit together, how to connect them to Cin7 Core and how to keep multichannel inventory accurate after go-live.
What is the difference between Amazon FBA and MCF?
Amazon FBA and Amazon MCF use Amazon’s fulfilment network, but they serve different order sources.
Fulfilment by Amazon (FBA) stores stock in Amazon fulfilment centres and picks, packs and ships Amazon marketplace orders. When connected to Cin7 Core, FBA is represented as an external inventory location. Cin7 Core can track the stock held there, create fulfilment orders and receive shipment and tracking updates.
Amazon Multi-Channel Fulfilment (MCF) uses that FBA inventory to fulfil orders placed outside Amazon. A customer may buy from your Shopify store, WooCommerce site or another supported sales channel; the order enters Cin7 Core and can then be sent to Amazon for fulfilment.
The simplest way to picture the relationship is:
- A sales channel creates an order.
- Cin7 Core records the order and determines the fulfilment location.
- Amazon FBA or MCF receives the fulfilment request.
- Amazon picks, packs and ships the goods.
- Cin7 Core receives stock, status and tracking updates.
FBA is therefore the warehouse and fulfilment connection. MCF is the route that allows eligible off-Amazon orders to use that network.
What the Cin7 Core Amazon setup can synchronise
A correctly configured connection can bring several operational flows together:
- Amazon orders can be downloaded into Cin7 Core.
- Products can be matched between Amazon and Cin7 Core.
- FBA stock can be represented in a dedicated external location.
- Stock quantities can be synchronised manually or on a schedule.
- Cin7 Core sales can generate external fulfilment orders.
- Fulfilment status and tracking information can flow back to Cin7 Core.
- Off-Amazon orders can be routed to MCF where supported.
That creates a far better foundation for synchronising orders, inventory and finance than managing each channel independently.
However, “connected” does not mean every process is automatic. The current native workflow has boundaries that need to be designed around:
- Amazon Seller Central is still used to manage inbound FBA shipments.
- External fulfilment orders require the Ship stage to be authorised manually; AutoShip does not fully authorise them.
- The native FBA integration does not currently process returns back into Cin7 Core.
- An FBA connection uses one external location in Cin7 Core.
- Regional MCF features, unbranded packaging and carrier options vary and must be checked against current Amazon and channel rules.
These are manageable limitations, but they need named owners and documented processes.
Before you connect Amazon to Cin7 Core
The technical connection is not the first step. Prepare the data and operating decisions first.
Confirm account access and permissions
You need an eligible Amazon professional seller account and Seller Central access. The Cin7 Core user completing the setup also needs the relevant Fulfilment by Amazon integration permission. Depending on your Cin7 Core plan, the integration may need to be enabled or purchased through the subscription area.
If MCF will be used, confirm that it is available in the country where the Amazon account operates and that the account is enabled for Multi-Channel Fulfilment.
Decide which system owns each part of the process
Document responsibility before building the integration:
| Process | Typical system of record |
|---|---|
| Product and SKU master | Cin7 Core, after data is standardised |
| Amazon listing content | Amazon Seller Central or listing tool |
| FBA physical stock | Amazon, reflected in a Cin7 Core external location |
| Multichannel sales orders | Cin7 Core |
| FBA inbound shipments | Amazon Seller Central |
| Fulfilment and tracking | Amazon, returned to Cin7 Core |
| Accounting and settlements | Accounting platform, supported by Cin7 Core processes |
Your architecture may differ, but ownership must be explicit. Two systems independently changing the same quantity or product record is a common cause of sync problems.
Clean and align SKUs
Cin7 Core can automatically match Amazon products by SKU. That is efficient only when the identifiers are reliable.
Before switching on automatic mapping:
- compare every Amazon Seller SKU with the corresponding Cin7 Core SKU;
- identify duplicate or reused codes;
- document bundles, kits and multipacks;
- separate parent and child variation logic from stock-bearing SKUs;
- confirm units of measure;
- check whether the same product is listed in more than one marketplace;
- decide how discontinued and zero-stock items should be handled.
If product codes do not match cleanly, use manual mapping until the catalogue has been reviewed. Our overview of integrating Cin7 Core with Amazon covers the wider commercial and finance decisions that should accompany this exercise.
Map locations and fulfilment rules
List every place inventory can physically sit: your own warehouses, stores, Amazon fulfilment centres and other 3PLs. Then define which channels may sell from each location.
Do not use the external FBA location for orders that will be shipped from your own warehouse. Cin7 Core reserves special behaviour for external fulfilment locations, including restrictions on bins and shipment authorisation.
If more than one fulfilment partner is involved, create a complete 3PL integration plan so that stock ownership, order routing and adjustments remain visible across the network.
How to connect Amazon FBA to Cin7 Core
The exact screens and labels can change, but the current setup follows this sequence.
Step 1: Connect or confirm the Amazon sales channel
If the Amazon marketplace is already connected to Cin7 Core, the FBA service can use that existing Amazon connection. If it is not, first connect the Amazon store and configure how products, orders, customers, tax and stock should be handled.
The Amazon store integration and FBA fulfilment integration perform different jobs. The store connection handles marketplace sales and catalogue information; the FBA connection handles external stock and fulfilment orders.
Step 2: Add the FBA fulfilment service
In Cin7 Core, go to Integrations → Fulfilment by Amazon, select the option to add a connection and either:
- use the existing Amazon store connection; or
- connect manually using the Amazon seller details and marketplace.
Select an existing warehouse location only if it is appropriate to become the external FBA location. Otherwise, allow Cin7 Core to create a new location. Only one location is available for each FBA connection.
Step 3: Review the external location
Once connected, Cin7 Core creates or designates an external fulfilment location. Review it under the location settings and confirm that users understand its purpose.
An external location:
- cannot contain bins;
- cannot be renamed or deleted while the service remains connected;
- should be used only for goods Amazon will ship;
- can be synchronised through a stocktake;
- does not allow shipping to be fully auto-authorised.
Avoid moving or adjusting stock against this location casually. Every manual change should correspond to a real event or a controlled reconciliation.
Step 4: Configure FBA behaviour
Open the FBA connection’s Setup tab and review each available option, including:
- the price tier used for downloaded products;
- whether fulfilment orders begin On Hold or proceed to shipment;
- manual or automatic order processing;
- automatic or manual product matching;
- whether missing FBA products may be created in Cin7 Core;
- automatic stock-sync frequency and start time.
Cin7 Core’s stock auto-sync is set to Never by default, so do not assume quantities will remain aligned until a frequency has been selected. The right cadence depends on order volume and whether any other application can change FBA stock.
Step 5: Map the catalogue
Use the FBA Catalog tab to review product matches. Automatic matching uses SKU values, while manual mapping lets you select the correct Cin7 Core product.
Resolve every unmapped or ambiguous item before enabling live order flow. Pay particular attention to:
- Amazon multipacks mapped to single-unit SKUs;
- bundles whose component stock is controlled elsewhere;
- the same SKU used in several marketplaces;
- FNSKU, ASIN and Seller SKU being mistaken for one another;
- products that exist in Amazon but not in Cin7 Core.
If the option to create missing products is used during the initial sync, review the resulting zero-stock items and add correct costing data before they affect reporting.
Step 6: Complete the initial FBA stocktake
The initial stocktake establishes the quantity Cin7 Core believes is held at Amazon.
In Cin7 Core:
- Go to Inventory → Stocktake and adjustments.
- Create a stocktake for the external FBA location.
- Start the stocktake and select Sync.
- Review the quantities imported from Amazon.
- Enter unit costs where required for zero-stock products.
- Investigate unexpected differences.
- Complete the stocktake.
Do this before live fulfilment orders are released. If Cin7 Core has too little stock, it may prevent a pick from being authorised. If it has too much, Amazon may reject a fulfilment request because the item is not actually available.
Step 7: Test an FBA order end to end
Create or import a low-risk test order and confirm:
- the correct customer, tax and product are used;
- the external FBA location is selected for the pick;
- the pick and pack stages behave as expected;
- authorising Ship creates a fulfilment order;
- the order reaches Amazon;
- Amazon accepts the address and service;
- shipment and tracking updates return to Cin7 Core;
- inventory reduces once, in the correct location;
- the accounting result is correct.
Cin7 Core can automate picking and packing in certain configurations, but the Ship stage for external fulfilment must still be authorised manually. Build that approval into the daily workflow instead of treating it as an integration failure.
How to configure Amazon MCF for off-Amazon channels
MCF becomes available through a connected FBA integration. It lets orders from supported non-Amazon channels use the same Amazon-held stock.
Step 1: Connect each sales channel to Cin7 Core
Connect Shopify, WooCommerce or the relevant sales channel and define how orders enter Cin7 Core. Confirm product mapping, tax, payment status, customer details, order status and stock-location rules for each channel.
A well-planned multichannel Cin7 setup prevents one channel from publishing stock that another channel has already consumed.
Step 2: Assign the FBA location to MCF orders
For an off-Amazon order to use MCF, its sale or pick location must be the external FBA location. This can be driven by channel configuration, product defaults or an operational decision during order review.
Be careful with mixed fulfilment orders. If some lines are held internally and others at Amazon, Cin7 Core separates them into different packages and fulfilment paths. Test this scenario explicitly.
Step 3: Set packaging rules by channel
In the Amazon MCF section of the FBA Setup tab, select the default packaging option for each sales channel.
Unbranded or “blank box” packaging can create a more consistent customer experience for orders placed on your own website. Availability and eligibility depend on country, fulfilment centre, product dimensions and current Amazon support. Cin7 Core may expose the feature more narrowly than Amazon itself, so confirm the live options in your account.
Some marketplaces restrict Amazon-branded packaging. Check every channel’s current policy rather than assuming that one MCF setting is safe everywhere.
Step 4: Choose the permitted carrier type
Some channels restrict the use of Amazon Logistics. Where supported, MCF can be configured to use a non-Amazon carrier instead. Amazon may apply an additional fee, and blocking its logistics network can affect availability or delivery speed.
Set this rule per channel and verify current Amazon pricing and marketplace policies before go-live.
Step 5: Test the complete MCF flow
Place a controlled test order through each off-Amazon channel. Confirm that it:
- downloads into Cin7 Core once;
- maps to the correct product;
- uses the FBA external location;
- creates one MCF fulfilment request;
- applies the correct packaging and carrier rule;
- returns tracking to Cin7 Core and the originating channel;
- reduces the correct stock balance;
- creates the expected finance records.
Repeat the test for a cancellation, invalid address, insufficient stock, split shipment and mixed-location order.
How to prevent overselling and inventory drift
Inventory sync is not a one-time implementation task. Amazon stock can change because of sales, transfers, receiving, removals, losses, damaged units, reserved inventory and adjustments.
Choose a sensible stock-sync frequency
Cin7 Core allows FBA stock to be synchronised manually or at a scheduled daily, weekly or monthly interval. High-volume multichannel businesses generally need closer monitoring than a slow-moving single-channel catalogue.
A faster sync does not compensate for poor architecture. If another application is also sending orders to Amazon or updating channel quantities, document its role or remove the overlap.
Use stock buffers where appropriate
Publishing every available unit to every channel leaves no protection against latency, reservations or damaged stock. A buffer can reduce overselling, particularly for fast-moving or low-quantity products.
The appropriate buffer may vary by SKU, lead time, velocity and channel priority. Treat it as an inventory policy rather than a universal percentage.
Monitor exceptions every day
Create a daily queue for:
- failed or rejected fulfilment orders;
- unmapped products;
- negative or unexpected stock;
- orders waiting for manual Ship authorisation;
- missing tracking;
- cancelled orders that may already be processing;
- stocktake differences;
- returns and reimbursements awaiting manual treatment.
The goal is not to eliminate every exception. It is to make sure exceptions are visible, owned and resolved before they affect customers or accounts.
Reconcile operations with finance
Amazon marketplace orders, FBA fees, MCF charges, refunds, reimbursements and settlement deposits do not naturally form one simple invoice-payment pair. Design how this information reaches the accounting system and how settlement totals are reconciled.
If the stock process is accurate but settlement accounting remains manual and unclear, the integration is only partly complete.
Common Amazon–Cin7 Core integration mistakes
Connecting before cleaning SKUs
Automatic matching can spread a catalogue error quickly. Resolve product identity first, then automate.
Treating FBA stock as an ordinary warehouse
The external location has special rules and represents stock controlled by Amazon. Using it for internal fulfilment or arbitrary adjustments makes the balance unreliable.
Skipping the initial stocktake
The connection does not guarantee that Cin7 Core starts with the correct quantity. Establish the opening position before releasing orders.
Allowing several systems to control fulfilment
If a channel app sends the order directly to Amazon while Cin7 Core also creates an MCF request, the customer can receive the order twice. Define one route for each channel.
Assuming returns are automated
The native FBA connection does not currently support returns. Document how returned, damaged, reimbursed and sellable stock is reviewed and posted back to Cin7 Core.
Ignoring regional and marketplace rules
MCF availability, blank-box eligibility, carrier restrictions, surcharges and marketplace policies change. Validate them for each country and channel during implementation and periodically after go-live.
Getting the setup right the first time
Amazon FBA and MCF can give a multichannel business fast fulfilment without duplicating inventory across separate networks. Cin7 Core adds the control layer: one place to see orders, map products, route fulfilment, monitor stock and connect the result to finance.
The value comes from the design around the connection. Consistent SKUs, dedicated locations, an accurate opening stocktake, clear channel rules and daily exception ownership are what turn the integration into a dependable operation.
For a new deployment, BlueHub’s Cin7 Core implementation service can cover process design, configuration, data migration, integration and end-to-end testing. If Amazon and Cin7 Core are already connected but stock or orders do not reconcile, a free Cin7 Core system review can identify mapping, workflow and data-integrity gaps.
If you want to connect Amazon FBA or MCF without risking live orders, speak to a BlueHub expert about your marketplaces, sales channels and fulfilment model.
Frequently asked questions
- Can Cin7 Core connect directly to Amazon FBA?
Yes. Cin7 Core has a native Fulfilment by Amazon integration. FBA is created or mapped as an external inventory location, allowing Cin7 Core to synchronise stock, generate fulfilment orders and receive status and tracking information. - What is Amazon MCF in Cin7 Core?
Amazon Multi-Channel Fulfilment allows Amazon to fulfil orders placed on non-Amazon channels, such as Shopify or WooCommerce, using inventory held in the FBA network. In Cin7 Core, the order is assigned to the external FBA location and sent to Amazon as a fulfilment order. - Do Amazon and Cin7 Core SKUs have to match?
Matching SKUs make automatic product mapping much safer because Cin7 Core uses SKU values to find corresponding products. If codes differ, products can be mapped manually. Do not enable broad automatic matching until duplicates, bundles, multipacks and variations have been reviewed. - How often does Cin7 Core sync FBA inventory?
Stock can be synchronised manually, and automatic sync can be scheduled daily, weekly or monthly. The default auto-sync setting is Never, so a frequency must be selected deliberately. The appropriate cadence depends on sales velocity, stock risk and whether other systems can affect Amazon quantities. - Can Cin7 Core automatically send Shopify orders to Amazon MCF?
Cin7 Core can import Shopify orders and route them to Amazon MCF through the external FBA location. Some pick, pack and processing steps can be automated, but the external fulfilment Ship stage must still be authorised manually. Test the exact workflow before relying on it for live orders. - Can MCF orders use unbranded packaging?
Amazon MCF supports unbranded packaging in eligible regions, fulfilment centres and product categories. The options available through Cin7 Core may be limited by region and are still subject to Amazon and marketplace rules. Confirm eligibility in the live account for each sales channel. - Does the Cin7 Core FBA integration manage inbound shipments and returns?
Inbound shipments are currently managed through Amazon Seller Central rather than Cin7 Core. The native FBA integration also does not currently support returns, so the business needs a separate documented process for returned stock, damage, reimbursements and adjustments. - Why do FBA and Cin7 Core stock levels differ?
Differences can be caused by an incomplete opening stocktake, SKU mapping errors, Amazon reservations, damaged or lost units, delayed updates, another system sending orders, cancellations or manual adjustments. Compare the external location with Amazon, review integration logs and trace the timing of each stock-changing event. - Can one order be partly fulfilled by Amazon and partly from our warehouse?
Yes, Cin7 Core can separate externally fulfilled items from stock held internally, creating different packages and fulfilment paths. Because this increases operational and customer-service complexity, test mixed-location orders, split tracking, shipping charges and cancellations before go-live. - How should we test an Amazon FBA or MCF integration?
Test product mapping, opening stock, Amazon and off-Amazon orders, cancellations, invalid addresses, insufficient stock, split shipments, mixed locations, tracking, tax, fees and accounting. Include failure scenarios and confirm who monitors and resolves each exception after launch.
