Description
The Order Management provides support for Order processing starting from order placement by the customer to its delivery. This is based on the fulfilment mode which is predefined by seller SUPC level.
[Refer: Get Seller Config API(/Seller/config) ]
There are following fulfilment modes in the system:
- Dropship
- Oneship
- Oneship Plus (OC+)
- SD+
- Vendor Self
Note: Each fulfilment model consists of various stages, such as
- PFF – Pending for fulfilment
- PRNT – Printed
- MFG – Item is added
- BARP – Barcode printed
- AHOS – Added to HOS
- ASTN – Added to STN
- SHP – Courier enables tracking
- FFD – Delivery
- CLD – Cancelled
Dropship
Order processing including printing labels and invoices and then packing the orders is taken up by seller. Snapdeal assigns and arranges courier for sellers. Sellers are responsible for handing over the packages to courier partners on time. Courier partners are then responsible for delivery.
Steps
- Order taken by snapdeal
- Send notification to seller
- Courier assigned by snapdeal
- Seller prints pack-slip and invoice
- Seller packs the product
- Seller creates a manifest
- Physical handover of items to courier agencies
- Product shipment
- Product delivery
Order processing steps for Dropship
1. Get pending order details.
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
Manual: In this case, invoice is generated for orders manually. Bulk: In this case, invoice is generated in bulk.
Advance upload: In this case, a csv file is uploaded by vendor and invoice is selected from the list.
Auto: In this case, invoice number is generated randomly.
Refer:
[Refer to section on invoice options and IMEI/Serial No. mandates.]
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
Invoice Options
None: If the invoice is prepared by snapdeal, vendor can select none option as fulfilment type.Manual: In this case, invoice is generated for orders manually. Bulk: In this case, invoice is generated in bulk.
Advance upload: In this case, a csv file is uploaded by vendor and invoice is selected from the list.
Auto: In this case, invoice number is generated randomly.
IMEI/Serial No
IMEI: For products, such as mobile phones IMEI number is required. Serial No.: For computer accessories, such as hard drive, charger, serial number is required.Refer:
- orders/new for getting IMEI Serial flags and details if already entered
- /orders/suborder/bulk/imei
- /orders/invoice
[Refer to section on invoice options and IMEI/Serial No. mandates.]
3. In case of multiple suborders in one order there is a provision to split order. This is an optional step and should be used only if seller cannot club all suborders and ship them together.
[Refer: /orders/split ]
4. In case pending order cannot be fulfilled by promised ship date/manifest by date then order needs to be marked out of stock. Please note that this may result to a penalty on seller. Refer to snapdeal policies for more details.
[Refer: /orders/suborder/bulk/status]
5. After checking above one needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in Pending for fulfilment state. On successfully printing packslip and invoice, package will move to PRNT state.
[Refer: /orders/print ]
6. Reprinting of pack-slip and invoice can be done for future reference.
[Refer: /orders/reprint]
7. After and order has been printed, and physically packed, then items needs to be added to manifest. After adding a package to manifest the state of items moves to “MFG”.
[Refer: /dropship/manifest/]
Note: Items belonging to only one courier can be clubbed into a single manifest.
8. There is a provision to create a new manifest or add items in already open manifest.
Note: Once a manifest has been printed, its marked closed and more items cannot be added to a manifest
[Refer: /dropship/manifest/]
[Refer: /dropship/manifest/{id}]
9. Once items have been added to manifest for handover to courier, print out of manifest needs to be taken.
[Refer: /dropship/manifest/print]
10. For future reference reprinting option is available for manifests.
[Refer: /dropship/manifest/reprint ]
11. Historical details of manifest can be pulled using get manifest api. Items belonging to manifest can also be looked by proving manifest code.
[Refer: /dropship/manifest/{manifestCode}/orders]
[Refer: /dropship/manifest]
12. After handing over the packages to couriers, courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api. [Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api. [Refer: /suborders/cancelled ]
[Refer: /orders/split ]
4. In case pending order cannot be fulfilled by promised ship date/manifest by date then order needs to be marked out of stock. Please note that this may result to a penalty on seller. Refer to snapdeal policies for more details.
[Refer: /orders/suborder/bulk/status]
5. After checking above one needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in Pending for fulfilment state. On successfully printing packslip and invoice, package will move to PRNT state.
[Refer: /orders/print ]
6. Reprinting of pack-slip and invoice can be done for future reference.
[Refer: /orders/reprint]
7. After and order has been printed, and physically packed, then items needs to be added to manifest. After adding a package to manifest the state of items moves to “MFG”.
[Refer: /dropship/manifest/]
Note: Items belonging to only one courier can be clubbed into a single manifest.
8. There is a provision to create a new manifest or add items in already open manifest.
Note: Once a manifest has been printed, its marked closed and more items cannot be added to a manifest
[Refer: /dropship/manifest/]
[Refer: /dropship/manifest/{id}]
9. Once items have been added to manifest for handover to courier, print out of manifest needs to be taken.
[Refer: /dropship/manifest/print]
10. For future reference reprinting option is available for manifests.
[Refer: /dropship/manifest/reprint ]
11. Historical details of manifest can be pulled using get manifest api. Items belonging to manifest can also be looked by proving manifest code.
[Refer: /dropship/manifest/{manifestCode}/orders]
[Refer: /dropship/manifest]
12. After handing over the packages to couriers, courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api. [Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api. [Refer: /suborders/cancelled ]
Oneship
Oneship is designed to aggregate products from different sellers ordered by customers at a designated snapdeal location, known as Oneship centre. In Oneship, when a customer places an order, Inbound Couriers will collect the products from sellers and stores them to the respective Oneship centres. From there, Outbound Couriers pick the orders and deliver them to the respective customers.
Steps
- Order taken by snapdeal
- Send notification to seller
- Courier assigned by snapdeal
- Seller print pack-slip and invoice
- Seller packs the product
- Seller creates Hand Over Sheet (HOS)
- Physical handover of items to courier agencies
- Courier stores items to Oneship center of respective region
- Product shipment (marked by courier)
- Product delivery (marked by courier)
Order processing steps for Oneship
1. Get pending order details.
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
3. In case of multiple suborders in one order there is a provision to split order. This is an optional step and should be used only if seller cannot club all suborders and ship together.
[Refer: /orders/split ]
4. In case pending order cannot be fulfilled by promised ship date/HOS by date then order needs to be marked out of stock. Please note that this may result to a penalty on seller. Refer to snapdeal policies for more details.
[Refer: /orders/suborder/bulk/status]
5. After checking above one needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in PFF state. On successfully printing packslip and invoice, package will move to PRNT state.
[Refer: /orders/print]
[Refer: /orders/reprint]
7. After an order has been printed, and physically packed, then items needs to be added to HOS. On adding packages to HOS, items will move into “AHOS” state.
Note: Items belonging to different Oneship centres cannot be clubbed into one HOS.
[Refer: /oneship/hos/]
8. There is a provision to create a new HOS or add items in already open HOS.
[Refer: /oneship/hos/{id}]
9. Once items have been added to HOS for handover to courier, print out of HOS needs to be taken. On printing HOS is marked closed and more items cannot be added into the HOS.
[Refer: /oneship/hos/print]
10. For future reference, reprinting option is available for HOSs.
[Refer: /oneship/hos/reprint ]
11. Historical details of HOS can be pulled using get HOS api. Items belonging to HOS can also be looked by proving HOS code.
[Refer: /oneship/hos]
[Refer: /oneship/hos/{code}/orders]
12. After handing over the packages to couriers, courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api.
[Refer: /suborders/cancelled ]
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
3. In case of multiple suborders in one order there is a provision to split order. This is an optional step and should be used only if seller cannot club all suborders and ship together.
[Refer: /orders/split ]
4. In case pending order cannot be fulfilled by promised ship date/HOS by date then order needs to be marked out of stock. Please note that this may result to a penalty on seller. Refer to snapdeal policies for more details.
[Refer: /orders/suborder/bulk/status]
5. After checking above one needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in PFF state. On successfully printing packslip and invoice, package will move to PRNT state.
[Refer: /orders/print]
[Refer: /orders/reprint]
7. After an order has been printed, and physically packed, then items needs to be added to HOS. On adding packages to HOS, items will move into “AHOS” state.
Note: Items belonging to different Oneship centres cannot be clubbed into one HOS.
[Refer: /oneship/hos/]
8. There is a provision to create a new HOS or add items in already open HOS.
[Refer: /oneship/hos/{id}]
9. Once items have been added to HOS for handover to courier, print out of HOS needs to be taken. On printing HOS is marked closed and more items cannot be added into the HOS.
[Refer: /oneship/hos/print]
10. For future reference, reprinting option is available for HOSs.
[Refer: /oneship/hos/reprint ]
11. Historical details of HOS can be pulled using get HOS api. Items belonging to HOS can also be looked by proving HOS code.
[Refer: /oneship/hos]
[Refer: /oneship/hos/{code}/orders]
12. After handing over the packages to couriers, courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api.
[Refer: /suborders/cancelled ]
Oneship Plus (OC+)
As Oneship, in this model also, rider picks up the items from seller and drops it to OCPlus center before passing it to the courier partners. The difference here is - the item which is picked up from the seller is not packed at seller end. However, it is packed in OCPlus center before passing it to courier partners. From there, it is delivered to the customer.
Steps
- Order taken by snapdeal
- Send notification to seller
- Courier assigned by snapdeal
- Seller prints barcode
- Seller pastes the barcode on the orders
- Seller creates Stock Transfer Note (STN) sheet
- Items are handed over to courier
- Courier brings the package to the OC+ center
- The barcode on the shipments are scanned and details of the orders are displayed on the system.
- Order is verified and QC is done at the same time (manually).
- Shipments are packed and pack slip is pasted on them. Shipments are sorted based on their courier and manifest is created for the orders.
- Manifest is printed.
- Shipments are handed over to the courier.
- The courier delivers the product to the customer.
Order processing steps for OC+
1. Get pending order details.
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
3. In case pending order cannot be fulfilled by promised ship date/STN by date then order needs to be marked out of stock.
[Refer: /orders/bulk/status]
[Refer: /orders/suborder/bulk/status]
4. After checking above one needs to print the bar code, paste the barcode on the order and create STN sheet. This step can be taken only when order is in PFF state. Item will move to BARP state after print barcode action.
[Refer: /orders/print]
5. After an order has been printed, and barcode pasted on the product, then items needs to be added to STN sheet(Stock Transfer Note). On adding packages to STN, items will move into “ASTN” state. Note: Items belonging to different Oneship+ centres cannot be clubbed into one STN.
[Refer: /ocplus/stn/ ]
6. There is a provision to create a new STN or add items in already open STN.
[Refer: /ocplus/stn/{seller}/{ocLoc}/{code} ]
7. Once items have been added to STN for handover to courier, print out of STN needs to be taken.
[Refer: /ocplus/stn/print ]
8. For future reference, reprinting option is available for STNs.
[Refer: /ocplus/stn/reprint ]
9. Historical details of STN can be pulled using get STN api. Items belonging to STN can also be looked by proving STN code.
[Refer: /ocplus/stn/{stnCode} ]
10. After handing over the packages to couriers, bar code scanning, order verification, shipment printing and manifest printing is done at OC+ center.
11. Reprinting of pack-slip and invoice can be done.
[Refer: /orders/reprint]
12. Courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api. [Refer: /suborders/cancelled ]
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
3. In case pending order cannot be fulfilled by promised ship date/STN by date then order needs to be marked out of stock.
[Refer: /orders/bulk/status]
[Refer: /orders/suborder/bulk/status]
4. After checking above one needs to print the bar code, paste the barcode on the order and create STN sheet. This step can be taken only when order is in PFF state. Item will move to BARP state after print barcode action.
[Refer: /orders/print]
5. After an order has been printed, and barcode pasted on the product, then items needs to be added to STN sheet(Stock Transfer Note). On adding packages to STN, items will move into “ASTN” state. Note: Items belonging to different Oneship+ centres cannot be clubbed into one STN.
[Refer: /ocplus/stn/ ]
6. There is a provision to create a new STN or add items in already open STN.
[Refer: /ocplus/stn/{seller}/{ocLoc}/{code} ]
7. Once items have been added to STN for handover to courier, print out of STN needs to be taken.
[Refer: /ocplus/stn/print ]
8. For future reference, reprinting option is available for STNs.
[Refer: /ocplus/stn/reprint ]
9. Historical details of STN can be pulled using get STN api. Items belonging to STN can also be looked by proving STN code.
[Refer: /ocplus/stn/{stnCode} ]
10. After handing over the packages to couriers, bar code scanning, order verification, shipment printing and manifest printing is done at OC+ center.
11. Reprinting of pack-slip and invoice can be done.
[Refer: /orders/reprint]
12. Courier agency will update the status of orders after processing.
13. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
14. In case of cancellation check the status using get cancelled orders api. [Refer: /suborders/cancelled ]
SD+
In this fulfilment mode, snapdeal stores the seller items in its warehouse even before an order placement and keeps notified the seller about pending and delivered orders.
Steps
- Order taken by snapdeal
- Checks the inventory of the item in the snapdeal warehouse
- Inform the respective seller about order placement
- Snapdeal processes the orders in SD+ Warehouses
- Snapdeal handovers the items to courier
- Courier ships the item
- Courier delivers the item
- Snapdeal notifies to the seller
Vendor Self
This fulfilment mode seller is completely responsible for order fulfilment from order processing, to delivery and updating snapdeal at each step. Seller is required to update various steps involved in order processing to snapdeal.
Steps
- Order is taken by snapdeal
- Notify seller about order
- Seller decides courier agency
- Seller prints pack-slip and invoice
- Seller does product packaging
- Seller creates Manifest
- Seller dispatches the item via courier
- Seller confirms delivery of orders to snapdeal
Order processing steps for Vendor self
1. Get pending order details.
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input,Updating the tracking details.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
[Refer: /orders/trackingDetails ]
3. In case pending order cannot be fulfilled by promised ship date date then order needs to be marked out of stock.
[Refer: /orders/suborder/bulk/status]
4. After checking above seller needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in PFF state. The state of the order will move to PRNT state post this action.
[Refer: /orders/print]
5. Reprinting of pack-slip and invoice can be done.
[Refer: /orders/reprint]
6. After and order has been printed, and physically packed, then items needs to be added to manifest.
[Refer: /vendorself/manifest ]
7. There is a provision to create a new manifest or add items in already open manifest.
[Refer: /vendorself/manifest/{id} ]
8. Once items have been added to manifest for handover to courier, print out of manifest needs to be taken.
[Refer: /vendorself/manifest/print]
9. For future reference, reprinting option is available for manifests.
[Refer: /vendorself/manifest/reprint]
10. Historical details of manifest can be pulled using get manifest api. Items belonging to manifest can also be looked by proving manifest code.
[Refer: /vendorself/manifest/{code}/orders]
11. After manifestation seller needs to mark the status of the items as delivered on successful delivery of the order to the customer.
[Refer: /orders/bulk/status]
12. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
13. In case of cancellation check the status using get cancelled orders api.
[Refer: /suborders/cancelled ]
2. Check for prerequisites before printing labels and invoice. This can include, Invoice, IMEI input,Updating the tracking details.
[Refer: /orders/suborder/bulk/imei ]
[Refer: /orders/invoice ]
[Refer to section on invoice options and IMEI/Serial No. mandates.]
[Refer: /orders/trackingDetails ]
3. In case pending order cannot be fulfilled by promised ship date date then order needs to be marked out of stock.
[Refer: /orders/suborder/bulk/status]
4. After checking above seller needs to print the labels and pack-slip of the pending orders. This step can be taken only when order is in PFF state. The state of the order will move to PRNT state post this action.
[Refer: /orders/print]
5. Reprinting of pack-slip and invoice can be done.
[Refer: /orders/reprint]
6. After and order has been printed, and physically packed, then items needs to be added to manifest.
[Refer: /vendorself/manifest ]
7. There is a provision to create a new manifest or add items in already open manifest.
[Refer: /vendorself/manifest/{id} ]
8. Once items have been added to manifest for handover to courier, print out of manifest needs to be taken.
[Refer: /vendorself/manifest/print]
9. For future reference, reprinting option is available for manifests.
[Refer: /vendorself/manifest/reprint]
10. Historical details of manifest can be pulled using get manifest api. Items belonging to manifest can also be looked by proving manifest code.
[Refer: /vendorself/manifest/{code}/orders]
11. After manifestation seller needs to mark the status of the items as delivered on successful delivery of the order to the customer.
[Refer: /orders/bulk/status]
12. In-transit and delivery statuses can be checked using completed orders api.
[Refer: /orders/completed ]
13. In case of cancellation check the status using get cancelled orders api.
[Refer: /suborders/cancelled ]
In all Order management APIs StartDate and endDate should be in epoch formate. difference between StartDate and endDate should not be more than 7 days inclusive of both startDate and endDate.endDate alone is not allowed without startDate.startDate alone is allowed without endDate. startDate Default Value is Current Date and endDate Default Value = Current Date-7 days
Note :
For all the Order Apis we need to give X-Seller-Authz-Token,X-Auth-Token,clientId as Header parameters
order management state transition table
| Order State | Details | Seller Actions |
|---|---|---|
| Pending for Fulfillment (PFF) | These are verified orders which are waiting for fulfillment. Seller can print invoice and packslip and after physical packaging, seller needs to create handover sheets and physically handover the orders to logistics partners. | Mark Out of Stock: If order cannot be fulfilled in time, seller needs to mark the order out of stock. Order will be cancelled for the seller. Refer: API - POST /orders/suborder/bulk/status Next state: Cancelled (CLD) Fill Order Details : For Certain orders, seller may be required to provide following details before taking a print of packslip and invoice: 1.IMEI No/ Serial. This is valid in mobile phones and other similar electronics products. Refer: API - POST /orders/suborder/bulk/imei 2.Invoice No. in case seller is on Manual invoice mode. Refer: API - POST /orders/invoice 3.Courier and Tracking No. in case of Vendorself where seller is responsible for arranging logistics for delivery. Refer: API - POST /orders/trackingDetails Split Packages : In certain cases snapdeal recommends sellers to ship multiple suborders together in one order. In case seller is unable to ship all in one package, seller can split and ship them separately. Refer: API - POST /orders/split Print Invoice and Packslip/ Print Barcodes : If order can be fulfilled seller is required to print packslip and invoice in case of Dropship, Oneship and Vendorself modes. In case of Oneship+, seller is required to print Barcodes. Next States: PRNT, BARP(for Oneship+ only) Refer: API - POST /orders/print |
| PRNT/BARP (Invoice & Packslip/ Barcode Printed) | Invoice and Packslips /Barcode are printed. | Split Packages : In certain cases snapdeal recommends sellers to ship multiple suborders together in one order. In case seller is unable to ship all in one package, seller can split and ship them separately. Refer: API - POST /orders/split Reprint Invoice and Packslip : Seller can take Re-print of Invoice & Packslip / Barcode. Refer: API - POST /orders/reprint Add to Handover/Manifest/STN : After printing packslip and Invoice/ barcodes seller is confirms the ready for handover to logistics by adding packed orders to handover (in case of Oneship), Manifest ( in case of Dropship and Vendorself) & STN (in case of Oneship +). Next State: MFG (in Case of Dropship & Vendorself), AHOS (in case of Oneship) & ASTN (in case of Oneship+) Refer: Creating Handover: Refer: API - POST /oneship/hos API - POST /vendorself/manifest API - POST /dropship/manifest API - POST /ocplus/stn Adding Orders to Handover: Refer: API - POST /oneship/hos/{id} API - POST /vendorself/manifest/{id} API - POST /dropship/manifest/{id} API - POST /ocplus/stn/{id1}/{id2}/{id3} |
| Added to Handover Sheets (AHOS/ASTN/MFG) | The orders which have been added to Handover/Manifest/STN sheet. | Print Handover : Once a Manifest/HOS/STN is prepared with all the items that are ready to be handed over to logistics partners, seller needs to take a print out and while physical handover, one copy is to be given to logistics partner and one copy signed by logistics partner’s pickup agent shall be kept by the seller. Refer: API - POST /oneship/hos/print API - POST /vendorself/manifest/print API - POST /dropship/manifest/print API - POST /ocplus/stn/print Reprint Handover : For future reference, handover/manifest/stn sheets can be re-printed Refer: API - POST /oneship/hos/reprint API - POST /vendorself/manifest/reprint API - POST /dropship/manifest/reprint API - POST /ocplus/stn/reprint |
| Shipped (SHP) | The Orders which have been marked shipped by logistics partners | Mark Delivered : In case of Vendorself mode, seller is required to mark the shipped items delivered. Refer: API - POST /orders/bulk/status Next State : These items will move to intermediate state where snapdeal will verify the delivery |
| Delivered(FFD) | Delivered(FFD) The orders which have been delivered to courier partners | N/As |