Noon Direct Ship FBP

Modified on Thu, 18 Nov 2021 at 07:01 PM

Noon is one of the major Marketplace of Middle East Countries. 

Different Models on Noon Marketplace

  • Direct Ship FBP - Seller owns the inventory and kept it in Seller's Warehouse. The seller will process the Customer's Order. 
  • FBN (Fulfilled by Noon) - Seller owns the inventory but kept it in Noon Warehouse. Noon Team will process the Customer's order. 
  • Crossdock (JIT model) - Seller sends the inventory to Noon Warehouse against a Bulk Order. Seller will Invoice to Noon.   

Assure is integrated with Noon Direct Ship FBP model through FTP-based integration.

Inventory update

  • Assure will send the inventory update on the Noon FTP folder whenever there is a change in inventory for any SKU.
  • Each file can contain up to 100 SKUs. Every notification will create a new file and Noon will have to archive the files after reading.
  • Noon can take 40-60 min to update those inventories because of the constrain at Noon's end.

Order creation

  • Once the customer places the order, Noon will create a picklist at a fixed interval. The picklist will be pushed to the FTP folder. 
  • Assure will poll the FTP for new files and create the order in Assure. Customer address and SLA are not shared by Noon and hence Assure will set a default address and SLA for every order.
  • For every different order code in Noon's picklist file, there will be a unique Assure order Id in and will be processed through the B2C order flow.

Order Processing Steps

  1. Once the customer places the order, Noon will create a picklist at a fixed interval. The picklist will be pushed to the FTP folder.
  2. Noon’s PicklistId will be set as Parent Order Code in Assure.
  3. The picking in Assure for Noon's order will be processed as per the standard Assure Picking process.
  4. After the picking, the user will pack the order in Assure as per Standard Assure Packing Process. The system will generate a barcode that contains the information of Parent order ID and Partner ID. The user needs to paste the generated barcode on the packet. 
  5. The same barcode will scan in the AWB popup. The barcode can be used to track the order in Assure and to create Manifest.
  6. The user will switch to the Noon application for the invoice generation and manifest on the Noon app as per the Noon standard process.
  7. After processing the order on Noon App, the user will create the manifest in Assures and scan the generated Barcode in the AWB section. After scanning every barcode, the user will close the manifest.
  8. The user will Handover the order as per the Standard Assure Handover process.
  9. All the above steps mentioned are mandatory, any miss will result in inconsistent data and will lead to issues.

Order Cancellation

  • Seller will know the cancellation detail of any order when user will start processing the order on Noon App.
  • Order cancellation will be on the order level. Partial Cancellation is not allowed.

SLA for orders

Noon doesn't provide SLA details and customer details. Assure creates the order with Default Customer Address, SLA of 2 days + from order time. The same information will be flown to the client’s ERP.

Return Order Flow

Return orders will be directly returned to the Noon warehouse. Based on the contract of the seller with Noon, the shipment can be kept at the Noon warehouse itself or sent back to the seller warehouse.

The seller can get two types of returns

  • RTO (Return to origin)
  • Customer Return

The return expectations in both cases can be downloaded from the Noon seller panel and can be uploaded in the Assure application in the required format.


  • This return order will be directly sent to the seller warehouse. 
  • The warehouse user will need to do the handover process using the Noon application. 
  • Then the return order will be processed using the Noon application. 
  • The user will need to mark qc pass or fail in the Noon app.
  • Once it's done the user can process the RTO in the Assure application.

Customer Return

  • This type of return will go to Noon’s warehouse.
  • It will be processed in Noon's warehouse.
  • Based on the qc status of the item, it will be sent to the seller warehouse.
  • Once it reaches the seller warehouse, the user will do the handover process using the Noon app.
  • It’s optional to process the return order on the Noon app.
  • They can directly go to the Assure app for return order processing.

Return order processing grid

Order noReturn TypeNoon-app handover processing requiredNoon-app return order processing requiredAssure return order processing required
O2Customer ReturnYesOptionalYes


  • Noon has the constraint of updating the inventory every 40 min - 60 min. This can lead to excess orders in Assure as the customer will have the visibility of inventory that might have already been used by other marketplaces in Assure.
  • Price updates along with cataloguing will be taken care of by the seller at Noon. Assure doesn’t have the capability to do the cataloguing on the Noon marketplace.
  • Noon doesn't have a mechanism to push an invoice so the warehouse will have to use two applications (Assure and Noon) while processing the order. 
  • Noon will provide the AWB pre-printed roll which can be mapped to an order in the run time using the Noon application. Currently, Assure doesn’t have the capability to input AWB numbers from the WMS UI.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article