Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-block-list.php on line 199

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/rlsnetnt/public_html/blog/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/rlsnetnt/public_html/blog/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home2/rlsnetnt/public_html/blog/wp-includes/class-wp-theme.php:9) in /home2/rlsnetnt/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1673
{"id":1229,"date":"2013-12-20T07:44:02","date_gmt":"2013-12-20T07:44:02","guid":{"rendered":"http:\/\/rai.net.in\/blog\/?p=1229"},"modified":"2013-12-20T11:00:38","modified_gmt":"2013-12-20T11:00:38","slug":"logistically-yours","status":"publish","type":"post","link":"https:\/\/blog.rai.net.in\/logistically-yours\/","title":{"rendered":"Logistically Yours"},"content":{"rendered":"

The success of e-tailing is intertwined with the quality of logistic support; robust, responsive and lean is the need of the hour. Storai, in conversation with Anil Khanna, MD, Blue Dart Express Ltd. profiles Blue Dart\u2019s ecommerce service. <\/b><\/p>\n

\"Market_Place-1\"<\/a><\/p>\n

\u201cThe play for any express logistic service provider, within ecommerce, is in the non-travel vertical. Since the entire gamut of e-commerce is not addressable for us, Blue Dart has identified the e-tailing market. By creating simplified solutions for our customers, we have a dominant market presence.\u201d Says Anil Khanna, MD, Blue Dart Express Ltd.<\/p>\n

E-tailing in India has taken off on the back of Cash on Delivery.\u00a0 Credit card penetration is still less than 30% (at a population level) and there are concerns about revealing card details online.\u00a0 Cash on delivery ensured that customer adoption of e-commerce was high \u2013 but it also increased the operational load on the e-tailer and the logistics partner.\u00a0 At the same time, COD provides companies like DHL with a platform to differentiate themselves:\u00a0 they are able to demonstrate better control over key risk points such the inherent risk of fraud, counterfeit, mutilation and theft.<\/p>\n

\u201cIn order to cater to the demands of the growing e-tailing industry, Blue Dart introduced the COD service as an additional payment option to customers. The invoice value of the shipment is collected from the consignee in the form of cash at the time of delivery. The cash collected from the consignee is returned to the e-tailer to close the transaction thus completing the entire system.\u201d<\/p>\n

Blue Dart has partnered with Yes Bank to offer MPOS solutions \u2013 a mobile device based GPRS connectivity to facilitate debit\/credit card payments.\u00a0 This POS device when connected to any smartphone device can be used as a POS terminal to facilitate card payments.<\/p>\n

Coverage v.s COD v.s. Logistics model<\/h2>\n

For e-tailers coverage is the key to growing sales.\u00a0 While full service logistics providers like Blue Dart cover most of the cities and towns, for regions below the Taluka level,\u00a0 they still need to tie up with local service providers.<\/p>\n

This has meant that e-tailers have to manage multiple partnerships and balance growth with operational efficiency.\u00a0 Out of this compulsion a natural progression of inventory models (and the corresponding logistics partner) has emerged:\"Market_Place-3\"<\/a><\/p>\n

Anil says, \u201cThe most common business model is the vendor based business mode; \u00a0as it is not very capital intensive. After receiving a set number of orders, the e-tailer purchases products from a local distributor, and then transports them to his own facility for packing and shipping. The advantage is that the e-tailer doesn\u2019t have capital tied up in inventory or unneeded warehouse space, has all the shipping records on hand, and has a good idea of the distributor\u2019s stock. The disadvantage is that the e-tailer is very dependent upon his distributor\u2019s supplies, and may not be able to accurately reflect available inventory to his shoppers before they purchase.\u201d<\/p>\n

Warehousing is another business model followed by e-tailers. As the e-tailing business grows in revenue as well as product offerings, e-tailers prefer to switch to the warehousing model where the e-tailer develops its own warehouses to store inventory and is ready to dispatch as soon as he receives an order. \u201cThis approach is investment intensive, since e-tailers are paying for both warehouse space, and have capital tied up in inventory on the shelves. But it allows the best quality of customer service, since shipping and inventory records are maintained in-house.\u201d, says Anil.<\/p>\n

The choice of model depends largely on the size of the company and the amount of capital available; while large, well capitalized e-tailing players (e.g. Flipkart) have their own logistics divisions, the smaller ones work with multiple logistics providers. As the e-tailing industry is slowly pivoting to a marketplace model \u2013 most mid sized e-tailers are choosing to outsource their logistics to a market place model.<\/p>\n

Range of Logistics options<\/h1>\n

Logistics companies also have a\"Market_Place-4\"<\/a> natural hierarchy in the industry.<\/p>\n