Noon Inventory Sync: Keeping Seller Lab Stock Accurate

Noon inventory sync is really two jobs, not one. You are keeping the quantity you declare for Fulfilled by Partner items in your own warehouse honest, and separately watching the quantity noon itself counts for Fulfilled by noon items sitting in its fulfilment centres. The two are updated in completely different ways, and most sellers who get caught out have confused one for the other. Here is how each is maintained in Seller Lab, why processing time belongs in the same conversation as stock, and what a stale count costs on noon in the UAE and Saudi Arabia.

FBP stock and FBN stock are two different counts

noon's help centre is blunt about the FBN side: your FBN stock is managed by noon, so you cannot change it on the FBN stock report, and adding stock means creating an ASN and transferring units to a noon warehouse (managing stock and prices). If you run both models on the same SKU, treat them as two locations: units in a noon fulfilment centre cannot be picked for an order from your own website.

How to update FBP stock in Seller Lab

For a single SKU: open Catalog, select it, scroll to Stock Information, pick the FBP warehouse the stock sits in, then enter the quantity and processing time and click Save Changes. A new SKU needs a warehouse added first. For anything above a handful of lines, use the import instead (FBP stock update import):

1. Go to Catalog, then Imports, and start a new import.
2. Set the import type to Stock and the sub-type to FBP Stock update.
3. In the customize step, select the warehouse, then click Request Export.
4. Fill the stock_gross column with the new count, and processing_time where you want to change it. noon's stock and prices guide gives the format as same_day, 1_day, 2_days, 3_days, 4_days; its delivery estimate article writes the same column as 1_day, 2_day. The two disagree on the plural, so copy the tokens from the export noon generates for your account.
5. Return to Seller Lab, start the import, upload or paste the file, and submit.

Two details from noon's troubleshooting are worth copying into your process. The most common failure is a mismatch between psku_code and partner_sku, which usually hits all-numeric SKUs or SKUs with special characters, and the documented fix is to delete the partner_sku column and import on psku_code alone. noon also advises pasting values into the template rather than saving the downloaded file first. It does not say why, only that pasting the values directly can prevent issues, and it suggests the paste tab for anything under 500 rows. Save as XLSX or CSV; XLS is not accepted.

If you would rather not touch files, noon's API platform page describes an interface covering catalogs, orders, fulfilment and event notifications, and points integrators at its developer documentation and a support case form (noon API platform).

Processing time is part of the sync

A correct quantity with an unachievable handover promise still produces a cancellation. noon defines processing time as the time you need to prepare the package for pickup or drop-off, and it feeds straight into the estimated shipping date shown to the buyer (delivery estimates for FBP orders):

• Pickup mode: ESD = order date + processing time + noon's pickup time.
• Drop-off mode: ESD = order date + processing time.
• Quick Fulfill requires handover of DirectShip orders within 6 to 24 hours. It can be set at item or warehouse level, or in the stock import by setting the processing time column to quickfulfill.

Three rules catch people out. Processing time cannot be changed for pending or existing orders. A warehouse-level change applies to future offers only, and pushing it across the catalogue needs Reset Processing Time, which only touches SKUs with no processing time of their own. And closed days have to be declared: you add them under Warehouse General Configuration, where noon splits them into Fulfillment Holidays, when no orders are processed, and Logistics Holidays, when there are no pickups or drop-offs (warehouse setup). The same screen sets the delivery model, which follows the warehouse country: noon Domestic Logistics covers UAE, KSA and Egypt warehouses. The UAE private sector has no national weekend to fall back on: the law sets 8 hours a day or 48 a week and leaves the off day to the labour contract (working hours). Eid dates and your own closure days are yours to enter, not noon's to guess.

What a stale count costs on noon

noon measures DirectShip sellers over any given seven day period (DirectShip performance management). This is the standard a stale count hits first, behind the account health you meet when you start selling on noon:

The other standard, a late shipment rate under 3%, is covered alongside Amazon and Shopify in this post's cross-platform companion, how to stop overselling across channels. noon lists the consequences of missing either as stock pulldown, offer deactivation, and store suspension or termination.

Work it through with illustrative figures. Say a Dubai brand takes 210 DirectShip orders in a typical week. At 2.5%, that is about five rejections before it is outside the standard. One fast SKU sells out on the shelf on Thursday afternoon, but the count on noon was last set by a weekly file upload. Six orders land before Sunday's import and all six are rejected: 6 of 210 is 2.86%. One SKU has pushed the week past the standard, and a stock pulldown, one of the penalties noon lists, would make the next week worse by shrinking what you can sell.

Keeping FBN stock in step with ASNs

For FBN, the sync is physical. noon's flow is to build the ASN in Seller Lab from your catalog or from the CSV template with SKU, quantity, dimensions and weight, seal it, then schedule it (ASN and storage). Dates matter more than most sellers expect:

• A sealed ASN can no longer be edited, although it can still be cancelled or scheduled.
• A sealed ASN that is never scheduled expires 60 days after sealing.
• A scheduled ASN expires 2 days after its scheduled date.
• If a slot is missed, rescheduling releases the original slot to other sellers.

Storage is allocated by item class. Standard runs up to 45 x 34 x 26 cm with a maximum shipping weight of 12 kg, Oversize up to 130 x 60 x 50 cm and 30 kg, and anything above that is Bulky. Measure carefully: noon takes length, width and height as the longest, median and shortest sides, so a box is not Standard just because one face fits. If an ASN exceeds your space, click Request Extra Storage during creation and noon approves or rejects it. Unused space cannot be moved between inventory types. Type matters as well as size: HRV (High Retail Value) covers mobile phones, tablets and laptops, and noon's routing rules block some mixes outright. Bulky lines cannot share an ASN with Standard or Oversize ones, and apparel and footwear, a storage type noon operates in the UAE only, needs an ASN of its own (ASN routing rules).

A weekly noon inventory sync routine

1. Count a sample of your fastest FBP SKUs on the shelf in your Dubai or Riyadh warehouse against what Seller Lab shows for that warehouse, not your total across all of them.
2. Check every stock import that ran this week on the Imports page and confirm the quantities actually changed, then clear pending ASNs before they expire and tally received quantities against what you sent.
3. Check the Inventory Health Dashboard. It updates daily and splits into Pricing Improvement, FBP Replenishment and FBN Replenishment, flagging SKUs as Out of Stock, Risk of Out of Stock or Normal Replenishment (inventory health dashboard).
4. Review every cancellation and give each one a cause. An out of stock rejection is a sync failure, not bad luck, and it counts into the DirectShip cancellation rate.
5. Check warehouse status. A warehouse stays Inactive until all four configuration sections are saved, and offers linked to it depend on that.
6. Add the next month's closures as Fulfillment or Logistics Holidays before they arrive, since processing time cannot be changed once an order is pending.

Where this usually breaks

• Updating one warehouse. The import is filtered by warehouse and identifies the location by noon_warehouse_code or partner_warehouse_code. A seller holding stock in Dubai for UAE orders and in Riyadh for KSA exports, edits and imports each one separately, and each export carries its own country_code.
• Raising stock without raising processing time. The count is true, the promise is not, and the late shipment rate takes the hit. Quick Fulfill cuts the handover window to 6 to 24 hours, so a Dubai warehouse that runs a short Friday should not be carrying it on fast-moving SKUs.
• Reporting on exports. The dashboard drops a SKU once you act on it, but noon says it can reappear when the recommendations update, so pull the FBP Replenishment list fresh each morning rather than circulating last week's copy.

Where Quickship fits

Quickship is a software company, so none of this changes who holds your stock. The Inventory Module keeps one stock figure per SKU across your warehouses and sales channels, pushes available quantity out to those channels with noon among its live integrations, and records every receipt, sale, return and transfer in one movement ledger so a missing unit can be traced. For a seller holding DirectShip stock in Dubai and FBN units in a noon fulfilment centre, that is one count behind both rather than two numbers that disagree by Thursday. If you are not live on noon yet, Marketplace Activation covers seller and product registration first. Whatever you run it on, the test is the same one noon applies: a cancellation rate under 2.5% over any seven days, or a Plan of Action emailed to seller@noon.com to get the store back in standing.