Release Notes¶
Flipkart Marketplace Seller APIs
Developer Guide
Last Updated: 3rd July, 2017
The release notes outlines the updates and enhancements in this version of the developer guide.
LICENSE AGREEMENT¶
|
Listing Management Changelog¶
Flipkart Marketplace Seller APIs for Listing Management | Version 3.0
Created: September, 2014
Last updated: 22nd March, 2018
Revision Details¶
What’s New?¶
- New attributes in listings for compliance with Legal metrology (packaged commodities) act. Please find details here
- New Fields
addressLabel
anddatingLabel
have been added for listing create and update payloads
- New Fields
- HSN needs to be mandatorily provided for all listings as the
hsn
attribute undertax
. HSN is an 8 digit product classification which helps determine what the GST tax rate is. Refer to this for more details - HSN code classification
- Tax rate to HSN code details (You can also refer to tax details from your price and stock file on MyListings page)
- HSN needs to be mandatorily provided for all listings as the
- Sellers who wish to ship the product by themselves need to set
shipping_provider
SELLER
: All orders will be shipped to customers by sellersFLIPKART
: All orders will be shipped to customers using Flipkart’s logistic vendorsSELLER_FLIPKART
: All orders will be given to the seller for shipping. If seller is not serviceable in the customer’s pincode, Flipkart’s logistics will do the shippingFLIPKART_SELLER
: All orders will be shipped using Flipkart’s logistics if possible. Else, the order will be given to seller for shipping if seller is serviceable in the customer’s location
- Sellers who wish to ship the product by themselves need to set
Packages refers to the final packaging in which the product will be shipped to the customers. Length, breadth, height and weight of the package refers to the dimensions of the final packaging. This will be used to check if Flipkart can ship these packages and also used to calculating the shipping fee to the seller in the occasion of an order.
Location refers to the various inventory and fulfillment locations of the seller. Updating inventory for a location will make the listing buyable from the location <location_inventory>
Seller can make the listing not buyable from the location by setting the status as DISABLED <>
Seller can create and update hyperlocal listing.
What’s Changed?¶
- Defining physical attributes of a listing:
length
,breadth
,height
andweight
is deprecated. They must now be defined under the entityPackage
. - Defining price attributes of a listing:
mrp
andsellingPrice
is no longer supported. They have been moved to thePrice
entity. - Defining fulfillment attributes of a listing:
procurement_type
,shipping_provider
andprocurement_sla
is no longer supported. They must now be defined under the entityFulfillment
.
What’s Added?¶
Following APIs are now added as part of Listing Management v3:
Order Management Changelog¶
Flipkart Marketplace Seller APIs for Order Management | Version 3.0
Created: 3rd July, 2017
Last updated: 3rd July, 2017
Revision Details¶
What’s New?¶
- Now, you can use the Flipkart Marketplace Interactive APIs tool to explore our APIs in the sandbox
- With this release, we have enabled
Ship Together
as a capability for sellers fulfilling Flipkart orders via Flipkart Marketplace Order Management APIs. Essentially, you can now ship products ordered from same customer in the same order together to them; thus saving your shipping costs significantly. - We now also support
Multi Location
as a capability for sellers i.e. you can now do seller fulfilment operations (EKL / 3PL Pickups / Self Ship Dispatches) from multiple addresses using the same Seller ID. No more hassles of maintaining different seller accounts for managing operations across multiple locations. - We now also allow you to change the secondary packaging dimensions for a shipment during order fulfilment at a Shipment ID level for your orders fulfilled via Order Management APIs i.e. you can update L, B, H, W values for shipments in case they have more than one order Items (ship together shipments) or multiple quantities of same order item.
- Logistics compliance forms generation is also supported via these APIs and you will get the same along with shipping label and invoice.
What’s Changed?¶
Ship Together
capability for sellers - You can now ship products ordered from same customer in the same order together to them; thus saving your shipping costs significantly. The implications are:Order Item ID is no more the primary pivot / identifier on which Order Management APIs work. We have now moved on to the concept of
Shipment ID
.Shipment ID is a unique identifier of the collection of products and their quantity which is to be ultimately delivered to customers; essentially a group of Order Item IDs.
By default, all Shipment IDs will have one Sub-Shipment ID.
- Exception will be Orders on product listings of the type
multi package
(example:Furniture, Large appliances etc.), where the product has multiple packages. We now facilitate shipping of multiple packages together will have multiple sub-shipment IDs corresponding to each of the packages, denoted by their respective Package IDs.
- Exception will be Orders on product listings of the type
Multi Location
capability for sellers i.e. you can now do seller fulfilment operations (EKL / 3PL Pickups / Self Ship Dispatches) from multiple addresses using the same Seller ID. No more hassles of maintaining different seller accounts for managing operations across multiple locations.Location ID
as an input parameter is added across all APIs to facilitate the same.
Updating Secondary Packaging Dimensions for a shipment during order fulfilment at a Shipment ID level for your orders fulfilled via Order Management APIs i.e. you can update L, B, H, W values for shipments in case they have more than one order Items (ship together shipments) or multiple quantities of same order item.
- These can be updated using the attributes
subShipmentID.dimension
parameter during shipping label generation call POST /v3/shipments/labels
- These can be updated using the attributes
Logistics compliance forms generation is also supported via these APIs and you will get the same along with shipping label and invoice. More details here: GET /v3/shipments/{shipmentIds}/forms
- If orders are stuck in processing due to form generation issue, you can unblock such orders by providing the
Acknowledgement No.
to take the fulfilment flow ahead. More details here: POST /v3/shipments/forms/updateAck
- If orders are stuck in processing due to form generation issue, you can unblock such orders by providing the
What’s Added?¶
Following APIs are now added as part of Order Management v3:
- POST /v3/shipments/filter/
- GET /v3/shipments?shipmentIds={} or, GET /v3/shipments?orderItemIds={} or, GET /v3/shipments?orderIds={}
- GET /v3/shipments?orderItemIds={}
- GET /v3/shipments?orderIds={}
- POST /v3/shipments/labels
- GET /v3/shipments/{shipmentIds}/labels
- POST /v3/shipments/{shipmentIds}/labelOnly/pdf
- POST /v3/shipments/{shipmentIds}/labelOnly
- POST /v3/shipments/dispatch
- GET /v3/shipments/{shipmentIds}
- GET /v3/shipments/{shipmentIds}/invoices
- POST /v3/shipments/cancel
- GET /v3/shipments/{shipmentIds}/forms
- POST /v3/shipments/forms/updateAck
- GET /v3/shipments/handover/counts?locationId={location_id}
- POST /v3/shipments/manifest
What’s New or Changed in Push Notifications?¶
Following notifications are now added as part of Order Management v3: