Sync Stock on Amazon and noon Across Two Warehouses (UAE)

To sync stock on Amazon and noon across two warehouses in the UAE, keep one master count per warehouse, subtract a buffer for each channel, and push the result to each marketplace every time stock changes. noon lets you set FBP stock per warehouse. For Amazon.ae, confirm in Seller Central whether location-level stock is available to your account.

This guide gives the steps, a worked example with hypothetical numbers, and the signs that an oversell has already happened.

What does each marketplace let you do with two warehouses?

noon is the clearer of the two. It has two models: fulfilled by noon (FBN) and fulfilled by partner (FBP), according to the noon seller onboarding FAQ. For FBN you send stock to noon warehouses with an ASN. For FBP you create your own FBP warehouse, then add inventory against each listing.

The noon catalog listing page guide says the Stock column is your aggregate FBN and FBP stock. It also says to change FBP stock for the correct warehouse if you use multiple warehouses for the product.

Amazon is less certain for the UAE. Amazon's SP-API guide describes location-level stock for Fulfilled by Merchant SKUs. It is a global document, so check it applies to amazon.ae. Amazon's Multi-Location Inventory page covers US sellers only and says the program is not available for FBA inventory.

One FBPI rule matters for planning. noon says a warehouse running under FBN or FBP cannot be converted to FBPI. You need a new, dedicated integration warehouse. Onboarding includes testing against noon staging, including inventory updates.

How do you sync stock on Amazon and noon from two warehouses in the UAE?

Use one master stock sheet or system, and treat the marketplaces as display screens for it. Here is the process.

1. Name the warehouses. Call them WH-A and WH-B. Every stock movement carries one of those codes. Say WH-A is in Dubai and WH-B is in Sharjah.
2. Count sellable units only. Exclude damaged units, units on hold, and returns not yet checked. noon itself puts FBN returns through quality checks and restocks only saleable items. Do the same.
3. Map each warehouse to channels. Decide whether each SKU is pooled (either warehouse can serve either channel) or dedicated (WH-A for noon, WH-B for Amazon). Dedicated is easier to run. Pooled lowers the chance of a stock-out.
4. Create the noon FBP warehouses. Add both, then add inventory against each listing per warehouse.
5. Set up Amazon. Look in Seller Central on amazon.ae for the way to hold stock by location. If it is not there, publish one total quantity for the SKU and let your master sheet decide which warehouse ships.
6. Set a buffer per channel. See the next section.
7. Choose what triggers a sync. See the section on frequency.
8. Test with one SKU. Place a small test order on each channel. Confirm the master count, the noon Stock column and the Amazon quantity all move as expected.

How do you set a stock buffer per channel?

Publish less than you hold. The formula is: published stock = sellable units in the warehouses assigned to that channel, minus units reserved for open orders, minus the channel buffer.

Here is a hypothetical example. A seller has 100 units of one SKU: 60 in WH-A and 40 in WH-B. Ten units are reserved for open orders from the seller's own website.

The buffer is bigger on noon in this example because the seller decided that a noon cancellation costs more than a lost Amazon sale. That is a business choice, not a rule from either platform. Base yours on how fast the SKU sells and what a cancellation costs you.

Raise the buffer when:

• a SKU sells fast and stock updates are slow,
• the SKU is on promotion,
• the two warehouses are in different emirates and transfers take time,
• you have had oversells on that SKU before.

Lower it when the SKU sells slowly and your sync runs on every order.

How often should stock sync?

Sync on every stock event if your tools allow it. If they do not, use a short fixed interval. Neither Amazon nor noon publishes a recommended sync frequency in the sources we reviewed, so treat the table below as practice, not platform policy.

Event-based sync matters most with two channels and two warehouses. A single sale on Amazon changes what noon should show. If that update arrives late, noon can sell the same unit.

For noon FBPI, your system updates inventory through the API, so frequency is in your hands. Amazon's guide lists several ways to update location-level stock: Supply Sources API, Listings Items API, Feeds API, a feed upload in Seller Central, or Manage All Inventory.

How do you spot an oversell before it costs you?

An oversell shows up as a cancellation for stock you thought you had. On noon, that has direct consequences.

noon's direct ship performance page counts orders you reject or mark "lost" before handover. It expects the cancellation rate to stay under 2.5% in any 7-day period, and late shipment rate under 3%. noon's cancellation policy says charges apply to rejected or cancelled orders and hurt performance. It also says the Processing Time you set in Seller Lab cannot be extended for an existing order.

The noon statement report lists a cancellation fee (CNCL) for seller-initiated cancellations such as out-of-stock. It also lists an Alternate Seller Fulfillment Fee (ALTF) when another seller fulfils an order you missed. Fee amounts vary, so check Seller Lab.

Run this check every morning:

• Any SKU with negative stock in the master count.
• Any SKU where the noon Stock column differs from your master by more than your buffer.
• Any SKU where Amazon quantity and the noon figure together exceed what you hold.
• Orders on both channels for the same SKU within a few minutes.
• Cancellations marked out-of-stock in the last 7 days, against the 2.5% limit.

When stock is truly gone, reject the order promptly. noon's direct delivery guidelines say orders must be rejected promptly when stock is unavailable, and high rejection rates can lead to penalties or store suspension.

What mistakes break two-warehouse sync?

• Counting returns as sellable. Hold them in a separate status until checked.
• Mixing up "at noon" and "in my warehouse". FBN and FBA stock is not yours to ship. Keep it in its own column.
• Updating the wrong noon warehouse. The catalog guide says to change stock for the correct warehouse. A mistake here shifts stock between locations.
• Using the same buffer everywhere. A fixed buffer for every SKU is too much for slow items and too little for fast ones.
• Ignoring transfers. Units moving between WH-A and WH-B belong to neither until received.
• Trusting one platform's number. The noon Stock column is an aggregate of FBN and FBP. It is not your master count.

Where does software fit?

Spreadsheets work for a handful of SKUs. Once two warehouses and two marketplaces move daily, manual edits fall behind. An inventory tool keeps one count per warehouse and pushes updates out. Quickship's Inventory module supports multi-warehouse stock and Amazon, noon and Shopify sync. It is software only. Your warehouses, staff and shipments stay yours.