Noon Expands Its Seller APIs With Product Creation, Real-Time Orders and Fulfilment Automation

Noon has introduced a significantly expanded API platform that gives sellers and integration providers more ways to automate how products, inventory, pricing and orders are managed across the marketplace.

The updated API documentation indicates that Noon is moving beyond basic stock and order synchronization toward a more complete seller-integration ecosystem. Sellers can now connect their ERP, PIM, OMS or warehouse system with Noon to automate several important parts of marketplace operations.

Here are the major new capabilities and what they mean for sellers.

Sellers Can Create and Update Products Through the API

One of the most important additions is Noon’s new Content API.

Sellers and integrators can now programmatically:

• Retrieve Noon’s product categories.
• Discover the mandatory and optional attributes for each category.
• Create new products and variants.
• Update existing product information.
• Submit English and Arabic content.
• Upload and order product images.
• Monitor content completeness.
• Track image-review and quality-control status.
• Retrieve specific reasons when a product is rejected or remains inactive.

Previously, large catalog onboarding often required sellers to work through Seller Lab or prepare product files manually. The new API makes it possible to create products directly from an ERP, PIM or marketplace-integration platform.

What this means for sellers

Sellers with hundreds or thousands of products can automate much more of the Noon listing process. Product information can be maintained in one central system and synchronized with Noon without repeatedly entering the same information.

The quality-control visibility is particularly useful. Instead of simply knowing that a product is not live, sellers can identify whether the problem is caused by missing attributes, invalid values, incomplete Arabic content, rejected images or Noon’s QC process.

This should make catalog onboarding faster and reduce the manual effort needed to diagnose failed listings.

Country-Level Pricing and Product Activation

Noon’s Pricing API allows sellers to retrieve and update prices across the UAE, Saudi Arabia and Egypt.

The API supports:

• Selling-price updates.
• MSRP or reference-price updates.
• Bulk price synchronization.
• Initial pricing for newly created products.
• Activating or deactivating products independently in each country.

A seller could, for example, activate a product in the UAE while keeping it inactive in Saudi Arabia, with separate pricing for each market.

What this means for sellers

International and multi-country sellers can manage Noon pricing from their existing commerce or ERP system.

Instead of maintaining separate spreadsheets or manually changing prices in Seller Lab, businesses can automatically calculate and publish country-specific prices. This is particularly valuable when exchange rates, costs, margins or promotions cause prices to change frequently.

Noon has also documented separate transfer-pricing APIs for its cross-border operations, giving eligible global sellers a way to manage cross-border product and transfer-price information programmatically.

Warehouse-Level Inventory Synchronization

The Stock API allows sellers to read and update inventory using a combination of Partner SKU and warehouse.

Sellers can:

• Set the exact available quantity for a product.
• Update multiple products in one request.
• Maintain different quantities across multiple warehouses.
• Set inventory to zero to stop additional sales.
• Compare Noon’s recorded quantity with their ERP or warehouse system.

Stock updates are absolute. If a seller submits a quantity of 20, Noon sets the available quantity to 20 rather than adding 20 to the previous quantity.

What this means for sellers

Accurate inventory is especially important on marketplaces where overselling can lead to cancellations, fulfilment problems and account-performance issues.

The API allows sellers to push stock whenever inventory changes in their ERP, OMS or warehouse. Fast-moving businesses no longer need to depend entirely on periodic manual uploads.

It also enables inventory to be managed independently for each fulfilment warehouse.

Better Visibility Into Why Products Are Not Live

Noon has introduced an Offer API that provides a consolidated view of a product’s marketplace status.

For a seller SKU, the API can return:

• Current price.
• Available stock.
• Country.
• Activation status.
• Actual live status.
• Issues preventing the offer from appearing to customers.

This distinction is important because an offer can be activated by the seller but still not be visible on Noon due to missing content, stock, pricing or another marketplace restriction.

What this means for sellers

Integrators can build catalog-health dashboards showing which products are live and which require attention.

Sellers can also verify whether a recently submitted stock or pricing update has taken effect. This helps identify listing problems before they result in lost sales.

Real-Time Seller-Fulfilled Order Processing

Noon’s expanded Fulfilled by Partner Integration, or FBPI, APIs allow sellers operating their own warehouses to automate the order-fulfilment process.

When a customer places an order, Noon can send a webhook notification to the seller or its integration provider. The seller’s system can then retrieve the complete order through the API.

The available order information includes:

• Noon order and item references.
• Partner SKU.
• Marketplace and country.
• Fulfilment warehouse.
• Currency and item price.
• Order and item status.
• Cancellation information.
• Limited customer delivery information.

If an ordered item is unavailable, the seller can mark that specific item as out of stock before creating the shipment.

The API also provides order-listing functionality, which can be used to reconcile orders in case an event or webhook is missed.

What this means for sellers

New Noon orders can flow directly into the seller’s ERP, OMS or warehouse-management system without manual downloads.

Warehouse teams can begin picking and packing shortly after an order is placed, while order acknowledgements and availability decisions can be communicated back to Noon automatically.

This should reduce fulfilment delays and the human errors associated with manually transferring orders between systems.

Shipment, AWB and Shipping-Label Automation

The FBPI APIs also cover several shipment operations.

Sellers can:

• Request Noon Logistics AWB numbers.
• Preallocate AWBs in bulk.
• Create a shipment for an order.
• Assign items to a shipment.
• Use Noon Logistics or their own courier.
• Attach a courier AWB.
• Retrieve shipment details and shipping labels.
• Replace or add AWB information when scanning problems occur.
• Cancel eligible shipments.
• Create sandbox orders for integration testing.

What this means for sellers

The order can move from confirmation to shipment creation inside the seller’s own warehouse workflow.

For example, once a warehouse employee finishes picking an order, the connected system can request an AWB, create the shipment and obtain the information needed to print the label.

The availability of sandbox orders is also important for technology teams. It allows the complete order and shipment flow to be tested without creating real customer orders or affecting live fulfilment.

Real-Time Event Notifications

Noon’s Event Notifications service allows sellers and integrators to configure HTTPS webhook destinations and subscribe to available business events.

Noon handles delivery retries automatically, with failed notifications retried multiple times using an exponential-backoff schedule.

The notification system uses at-least-once delivery, meaning integrations must safely handle the possibility that the same event may be delivered more than once.

What this means for sellers

Integrations will not need to continuously poll Noon to discover every change.

Important events can be pushed to the seller’s system as they happen, making order and operational workflows faster while reducing unnecessary API calls.

The list of available event types can also be retrieved through the API, allowing Noon to add new notification types as the platform expands.

Bulk Reports and Data Exports

Noon has also documented APIs for asynchronous report generation.

An integration can:

• Retrieve the export categories available to the seller.
• Request an export.
• Monitor its processing status.
• Download the completed report.

What this means for sellers

Large reports can be generated and imported into an ERP, data warehouse or reporting platform without requiring someone to download them manually from Seller Lab.

However, Noon’s public documentation currently returns report categories dynamically and does not publish a fixed list of every dataset available. Sellers and integrators will need to check the categories enabled for their projects.

Secure Onboarding for Integration Applications

In addition to API-JWT service accounts, Noon has documented an OAuth flow for integration providers.

This allows sellers to authorize third-party platforms without relying entirely on manually shared, long-lived credentials. Noon also provides APIs for creating, rotating and removing service-account credentials.

What this means for sellers

Connecting an authorized integration platform should become more secure and manageable. Sellers can provide project access through a controlled authorization flow, while credentials can be rotated or deactivated when necessary.

This is an important foundation for multi-tenant integration platforms serving multiple Noon sellers.

Automatic Manifestation Appears to Be Coming Next

One manual step remains in the FBPI workflow: manifestation.

After creating shipments through the API, sellers currently need to create a manifest in Seller Lab before Noon schedules a pickup. Noon’s documentation specifically states that it is working on an automatic manifestation option that would make this manual step optional.

No public manifestation endpoint is documented yet, so sellers should not treat this capability as currently available. However, its mention in the official documentation indicates that Noon intends to automate this remaining part of the fulfilment workflow in a future release.

A Major Step Toward End-to-End Noon Automation

Noon’s expanded API platform represents a significant improvement for sellers that manage large catalogs, operate multiple warehouses or process substantial order volumes.

The most important development is not any single endpoint. It is the ability to connect the complete operational flow:

Product creation → QC monitoring → pricing → inventory → offer visibility → order import → shipment creation

Some Seller Lab functions are still not exposed through the published APIs. Nevertheless, the currently documented capabilities are sufficient to automate a large portion of day-to-day Noon marketplace operations.

For sellers already using an ERP, PIM, OMS or warehouse-management system, the new APIs should reduce manual work, improve data accuracy and make it much easier to scale their business across Noon’s regional marketplaces.

Purchase Order Visibility for Noon’s FBPO Model

Noon’s updated API documentation also introduces support for Fulfilled by Purchase Order (FBPO).

Unlike FBPI—where sellers receive marketplace orders and prepare shipments for customers—FBPO follows a retail-style workflow. Noon generates a purchase order, the seller reserves the requested inventory and supplies the products against that purchase order. Noon then manages the onward customer fulfilment.

The currently documented API allows an integration to retrieve a specific purchase order using its PO number.

What This Means for Sellers

Businesses operating under Noon’s FBPO model can bring purchase-order information into their ERP, OMS or internal procurement system.

This can reduce manual data entry and help teams view Noon purchase orders alongside purchase orders and marketplace orders received from other sales channels.

However, the publicly documented API coverage is currently limited. Noon has not yet documented APIs for:

• Listing all newly issued purchase orders.
• Accepting or rejecting a purchase order.
• Confirming available quantities.
• Creating an advance shipping notice.
• Updating shipment or delivery status.
• Submitting invoices against a purchase order.

Sellers should therefore currently view the FBPO API as providing purchase-order visibility rather than complete purchase-order automation.

Nevertheless, the inclusion of FBPO in Noon’s new API platform is an important development. It suggests that Noon is laying the foundation for deeper purchase-order integration capabilities.

If Noon releases additional FBPO operations, platforms such as Commercium could potentially automate the complete workflow—from receiving a Noon purchase order and reserving inventory to fulfilment, shipment updates and invoicing.

Connect Noon With Your Existing Systems Using Commercium

The new APIs create significant automation opportunities, but building and maintaining a reliable Noon integration still requires product mapping, inventory controls, webhook processing, error handling and ongoing monitoring.

Commercium helps sellers connect Noon with their ERP, eCommerce store, PIM, warehouse and order-management systems.

With Commercium, sellers can automate:

• Product creation and content synchronization.
• Country-specific pricing.
• Multi-warehouse inventory updates.
• Listing and QC error monitoring.
• Real-time order synchronization.
• Shipment, AWB and fulfilment workflows.
• Connections with other global marketplaces through one platform.

Whether you are starting with Noon or managing a complex multi-channel operation, Commercium can help you build a more reliable and scalable marketplace workflow.

Ready to automate your Noon operations?

Noon Shopify Integration

Noon Business Central Integration

Noon Odoo Integration

Book a Noon marketplace integration demo with Commercium by ConstaCloud

Sources: Noon API Documentation, Content API, Pricing API, Stock API, Offer API, FBPI order flow and Event Notifications.