Noon

Owned by Prabal Pandit
Last updated: Dec 08, 2023 by Rahul Singh
6 min read

This document describes the design and SOPs of the integration between Increff Omni and Noon marketplace.

Integration mechanism

This integration is a FTP-based integration.

Integration model

The current integration will enable sellers to use the DirectShip FBP model with Noon marketplace. (The order will be directly shipped to the customer and will not go to the Noon 

warehouse).

Other models which is supported by the Noon are

  1. FBN (Fulfilled by Noon) - No integration APIs available

  2. Crossdock (JIT model) - No integration APIs available

Touchpoints 

  1. Order Creation

  2. Inventory Update

  3. Order Cancellation

  4. Order Packing

  5. Return Flow

Order creation

Order creation is done using FTP integration. There are 2 approaches available for order creation, using Picklist or using Order. The client can choose one of the approaches.

A. Using Picklist Number

  • Once the customer places the order, Noon will create a picklist after a fixed interval and the picklist will be pushed to FTP in a format. Omni proxy will keep on polling the FTP for new files and creates the order in WMS. Customer address and SLA are not provided in this file. Omni 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 Increff order Id in and will be processed through the B2C order flow.

  • Please find the format of the file added in FTP below.

picklist_nr

picklist_item_nr

order_nr

partner_sku

qty

partner_warehouse_code

LP3405155A

1

 

 

3

2497

B. Using Order Number

  • Once the customer places the order, Noon will create and push the order to FTP. Omni proxy will keep on polling the FTP for new files and create the order in WMS.

  • For every different order code, there will be a unique Increff order Id, and will be processed through the B2C order flow.

  • Please find the format of the file added in FTP below.

order_nr

purchase_item_nr

qty

partner_sku

status

partner_warehouse_code

NSAFC0090689

NSAFC00689-4-P1

1

70043103

pending

2497

NSAFC0090689

NSAFC00689-6-P1

1

70020103

pending

2497

Please note, Using Order Number approach has certain additional advantages as some additional flow will be supported there. These flows are:

  1. Customer Cancellation

  2. Seller Cancellation(in Testing phase currently)

  3. Replacemenmt Order Creation

These flows are not supported if client opts for Using the Picklist Number order creation approach.

Inventory update

  • Any inventory change of any sku in WMS will trigger an inventory update notification and only those skus whose inventory are changing will be sent to FTP with a fixed interval of x second. The preferred value of x is 5 , although this is configurable. Noon can read those updates on their preferred frequency. This is the file format.

  • Each file can contain upto 100 skus. Every notification will create a new file and Noon will have to archive the files after reading.

Order Customer Cancellation

A. When Order creation is opted by the client Using Noon Picklist Number

  • No integration is available here.

  • There will be very few order cancellations from the Noon side which the seller will get to know once the seller starts to process the order on the Noon app.

  • Order cancellation will be on the order level. No partial cancellation is there.

  • In case of cancellation, the warehouse team can raise a ticket using Increff Fresh Desk to cancel the order.

B. When Order creation is opted by the client Using Noon Order Number

  • Here the integration is available. In this scenario, Noon will update the status of customer order cancellation in the FTP file, Increff will pull the status and update the same in WMS.

Order Seller Cancellation

A. When Order creation is opted for by the client Using Noon Picklist Number

  • No integration is available here. The order has to be manually canceled at Noon when it is canceled in Increff OMS.

B. When Order creation is opted by the client Using Noon Order Number

  • Here the integration is available. In this scenario, the warehouse team will cancel the order at noon panel, and the status gets updated in the FTP file, and Increff will pull the status and update the same in WMS.

Seller cancellation flow when Order creation is opted by the client Using Noon Order Number is currently in testing phase.

Order Packing

  • Order packing will be done in Increff WMS which will be dummy packing. There will be no communication happening with Noon during this process.

  • The user will have to pack the same order on the Noon app. All warehouse SOPs are mentioned below.

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 Noon warehouse itself or sent back to the seller warehouse.

Seller can get two types of returns

  1. RTO (Return to origin)

  2. Customer Return

The return expectations in both cases can be downloaded from the Noon seller panel and which can be uploaded in the Increff Omni in the required format.

RTO

  • 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 Increff WMS 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 , he/she 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 Increff WMS app for return order processing.

Note : 

  • Here the handover process in the return order flow refers to the handover from logistics to the seller.

  • Customer Return and RTO can be differentiated based on the packaging of the material.

 

Return order processing grid

Order no

Return Type

Noon-app handover processing required

Noon-app return order processing required

WMS return order processing required

O1

RTO

Yes

Yes

Yes

O2

Customer Return

Yes

Optional

Yes

Replacement Order Creation Flow

A. When Order creation is opted for by the client Using Noon Picklist Number

  • Here, the replacement order creation is not supported at Integration.

B. When Order creation is opted for by the client Using Noon Order Number

  • Here, the replacement order creation is supported by Integration. A new order is created for replacement order at Increff. Eg, For forward order No - NSAFC0090689, Exchange Order Number will be EX-NSAFC0090689.

  • Similarly, Order Items will be modified. Here, order item is order_Code + itemNo + P1/P2 (where P1 means first time order, P2 means exchanged 2nd time, and similarly P3 means 3rd time) Eg, Forward order line Item: NSAFC0093200689-4-P1, Exchange Order line item: NSAFC0093200689-4-P2

SOP for Warehouse operations

  1. For each Noon order, one B2C order gets created in WMS as above mentioned.

  2. Noon’s picklistId will be set as “parentOrderCode” in WMS. (if picklist wise order creation is opted)

  3. The picklist and picking in WMS for Noon marketplaces will be similar to other marketplaces.

  4. Once the item is picked, the item comes to the packing desk and the user will scan the item as usual.

  5. After all items are scanned, the user will press the “Complete Packing” button. Once the user gets success , he/she can click on the “Print Invoice & Shipping label” button. The user will get a barcode of order ID and partner ID information. He/She can stick that barcode onto the shipment. 

  6. The same barcode can be scanned in the AWB popup they get after they click on the “Print Invoice & Shipping label“ button.

  7. The same barcode can be used to track the order in WMS and also to create a Manifest.

  8. Now, the user will switch to the Noon application for the rest of the processing (for invoice generation and manifest on the Noon app).

  9. Now, the user follows the process of manifest creation which happens in any normal order processing.

  10. If a user doesn’t want to create a manifest in WMS (as this is a redundant step because he has to do so on the Noon app also), he/she can mark all the orders as COMPLETED in bulk in Increff WMS using the Manual Order completion screen.

  11. All the above steps mentioned are mandatory, any miss will result in inconsistent data and will lead to issues.

Nuances

  • Noon has the constraint of updating the inventory every 40 min - 60 min. 

  • This can produce excess orders in WMS as the customer will have the visibility of inventory which might have already been used by other marketplaces in WMS.

  • Price updates along with cataloging will be taken care of by the client. Increff Omni doesn’t have the capability to do the cataloging on the Noon marketplace.

  • Noon doesn't have a mechanism to push an invoice so the warehouse will have to use two applications (Increff WMS and Noon App) 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, Increff WMS doesn’t have the capability to input AWB numbers from the WMS UI.

  • Increff Omni creates an order with default customer address, SLA of 2 days + from order time, start processing time same as order time as these details are not provided by Noon marketplaces. Same information will be flown to the client’s ERP.