...
This integration is a FTP-based integration.
Integration model
...
| Table of Content Zone | ||||
|---|---|---|---|---|
| ||||
|
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 this a format. Omni proxy will keep on polling the FTP for new files and creates the order in WMS. Customer address ,and SLA is 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:
Customer Cancellation
Seller Cancellation(in Testing phase currently)
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 will start 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 at omni.support@increff.com to cancel the order.
...
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 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
For each Noon order, one B2C order gets created in WMS as above mentioned.
Noon’s picklistId will be set as “parentOrderCode” in WMS. (if picklist wise order creation is opted)
The picklist and picking in WMS for Noon marketplaces will be similar to other marketplaces.
Once the item is picked, the item comes to the packing desk and the user will scan the item as usual.
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.
The same barcode can be scanned in the AWB popup they get after they click on the “Print Invoice & Shipping label“ button.
The same barcode can be used to track the order in WMS and also to create a Manifest.
Now, the user will switch to the Noon application for the rest of the processing (for invoice generation and manifest on the Noon app).
Now, the user follows the process of manifest creation which happens in any normal order processing.
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.
All the above steps mentioned are mandatory, any miss will result in inconsistent data and will lead to issues.
...