Can I connect Noon to Shopify or my stock system?

What the Noon seller API is

An API, short for application programming interface, is a set of doors that lets one piece of software talk to another without a person clicking. Noon's Partner API is the set of doors for noon, the online marketplace used across the UAE, Saudi Arabia and Egypt. Sellers and their software providers use it to run a store without opening Seller Lab, which is Noon's web dashboard for sellers.

The official documentation is public. It is organised into areas: authentication, catalog, content, pricing, stock, offers, fulfillment, warehouses, reports, returns and event notifications. You get credentials by creating a service account inside Noon's Access app, which downloads a key file. Your software signs a login request with that key and then sends its requests. Keep that key file private, and never put it in shared code. Anyone holding it can act on your account within the roles you gave it.

What each part does for a seller

Area	What it lets you do
Stock	Set the available quantity for a SKU, update many SKUs in one call, set to zero to stop selling, read current quantities. Updates set an exact number, they do not add or subtract
Pricing	Read and update selling price, the crossed-out MSRP price, and whether a SKU is active, per country (UAE, Saudi Arabia, Egypt)
Content and catalog	Create or update product listings, with English and Arabic content, check completeness and review status, map SKUs and barcodes
Offer	Read the live offer for a SKU across countries (read only)
Fulfillment by Partner Integration	Receive orders by webhook, create shipments, get tracking numbers, upload invoices
Event notifications	Get pushed an alert when something happens, instead of asking again and again

A SKU is your own code for one product variant. A webhook is a message Noon sends to your system the moment something happens, such as a new order.

Your fulfillment model decides how orders sync

This is the part most guides skip. Noon has two main ways to fulfill. With FBN, short for Fulfilled by noon, your stock sits in a noon warehouse and noon picks, packs and ships. With the partner model, called FBP in the help center and FBPI in the API docs (Fulfilled by Partner Integration), you keep stock in your own warehouse and noon sends you each order.

• FBN: noon manages the stock, and sellers cannot edit FBN stock directly. You send stock in with an advance shipping notice. There is no order feed to build, because you do not fulfill. Your system mostly needs prices, listings and a stock report.
• FBP with API: Noon routes each order to your webhook. Your system reads the order, creates a shipment, attaches a tracking number (noon can generate one), and you book a pickup in Seller Lab. Noon then delivers and handles returns after pickup.

So "sync orders from Noon into my system" only applies if you ship from your own warehouse. If you use FBN, what you want is a sales and fee report, not an order feed.

Can you connect Noon to Shopify?

Shopify is an online store platform. Noon's docs name system integrators, ERPs and order systems as the intended users of the API, and they describe "noon-approved integrators" for the partner model. Shopify is not listed as a built-in channel in the docs, so plan on one of three routes:

1. Spreadsheets. Export from Shopify, reshape, import into Seller Lab. Fine for under a few hundred SKUs.
2. A noon-approved integrator. A software provider that already maintains the connection. Ask Noon seller support for the current list.
3. A small custom connector. Your stock source of truth (Shopify or an inventory system) pushes stock and price changes to the Noon API on a schedule or when something changes. This is what I build for UAE brands that outgrow spreadsheets.

For general tools that connect apps without code, see Zapier vs Make. They can call an API, but a stock sync that must never double-sell needs more care than a simple trigger.

Bulk templates in Seller Lab, no code needed

Seller Lab has spreadsheet imports under Catalog, then Imports. They cover most small sellers.

• New listings: download the New Item Set-up Sheet from Catalog, My Catalog, Add Products, Create Multiple Products. Pick a category, choose the English or English plus Arabic template, fill it in, save as CSV, TSV or XLS, upload. Noon says listings go live within three business days after review. One sheet can carry up to 10,000 partner SKUs.
• Prices: export the price template, fill in the Price, Sale Price and sale date columns (dates as YYYY-MM-DD), upload. Changes appear within 24 hours. Price changes above 30% go to review and may be rejected.
• FBP stock: export the stock sheet, fill the stock_gross and processing_time columns (values like same_day, 1_day, 2_days), upload.

Images need to be JPEG links. Noon accepts direct links or a shared Google Drive folder.

Steps to set up a stock and price sync

1. Register and get approved as a seller, then confirm your SKUs exist on Noon. A SKU must exist before you can set its stock.
2. Create a service account in the Access app and store the key file where only your server can read it.
3. Create a warehouse in Seller Lab if you are on the partner model. Stock is tracked per warehouse code.
4. Test with a handful of SKUs. Noon provides a static sandbox and a sandbox order call for testing the partner order flow.
5. Push stock changes when stock changes, not only once a night. Send exact quantities, since updates set the number.
6. Respect rate limits. Limits are per project and each endpoint has a main and a burst window. The stock read call, for example, allows 1,500 requests per 60 seconds. If you get a 429 error, wait for the window to reset.
7. Log every failure and alert a human. A silent failed sync is how a store sells stock it does not have.

The same rule that applies in any inventory setup applies here: pick one place that owns the stock count. My inventory management system guide explains how to choose it.

A worked example (made-up figures)

A skincare brand in Dubai sells 400 SKUs on its Shopify store and on Noon, shipping from its own warehouse. Shopify holds the stock count. Today a staff member exports a sheet every morning and uploads stock to Noon. Orders on Shopify between uploads can leave Noon showing stock that no longer exists, and about 15 orders a month get cancelled. A connector fixes that by sending the new quantity to Noon within minutes of each Shopify sale, and by sending Noon orders into the same fulfillment queue. The saved cancellations matter more than the saved hours, because Noon applies penalties to sellers who cancel orders.

Ways it goes wrong

• Marking a product out of stock after an order arrives. The help center says a cancelled order cannot be reversed and penalties can apply.
• Pushing a price change over 30% through the sheet and finding it was held for review.
• Sending a wrong warehouse code, so stock lands in the wrong place.
• Letting the key file leak into code that is shared with others.

How I'd approach this

Under about 300 SKUs, I would use the Seller Lab imports and a short daily routine before building anything. Past that, or once cancellations cost real money, I would build a small connector that pushes stock and price from your master system to Noon, and that logs every call. For UAE brands that is the type of work I do: Noon stock and order sync, built around the stock system you already have. Related guides cover choosing an AI and software partner in the UAE and automating repeat work. If you are weighing inventory software in Dubai, a software development company in the UAE or an ERP (a system that runs stock, orders and accounts together), the same rule holds: start from the process, then pick the tool.