Logistics Service Design and Transportation Fundamentals

Logistics service providers and the C&FA service-design problem

Logistics service providers make a supply chain operational by providing distribution, carrying-and-forwarding, warehousing, inventory handling, trucking, and related services. In India, the provider landscape includes a few very large players, such as Indian Railways, but also many small and medium distributors, clearing-and-forwarding agents, warehouse operators, and truckers. Service design must therefore align the work a provider performs, the risk it assumes, and the compensation it receives.

The C&FA role: Logistics Solutions and Josh Denims

Logistics Solutions was a family-managed Ahmedabad logistics enterprise whose core competence was coordinating distribution and carrying-and-forwarding agency (C&FA) operations rather than owning a large transport fleet or warehouse network. Its activities included distribution management, warehousing/stocking, inventory holding, dispatch coordination, and C&FA work across pharmaceuticals, food, FMCG, consumer durables, and garments.

Each client was run as a separate agency for accounting and operations. Efficient working-capital use yielded roughly $36$–$40$ working-capital cycles per year: high turnover from limited capital.

Josh Denims selected Logistics Solutions to be its Gujarat C&FA after evaluating reputation, financial strength, infrastructure, professional management, and technology. The dedicated agency was Raj Distribution Services (RDS). Denim garments had numerous size, colour, zipper, pocket, and style variations, creating a large number of stock keeping units (SKUs). High SKU variety and fashion-driven demand shifts make inventory tracking, accurate fulfilment, and variant availability central service requirements.

Initial distribution design

The original chain was:

$$\text{Josh manufacturer} \rightarrow \text{RDS (C\&FA)} \rightarrow \text{distributor} \rightarrow \text{retailer} \rightarrow \text{consumer}$$

There were $10$ distributors and $180$ approved retail outlets in Gujarat. Distributors performed a valuable buffering role: they held inventory, extended credit, managed retailer-demand fluctuations, and absorbed operational and financial risk. This reduced the operating burden on Josh and RDS.

Freight was negotiated annually using previous-year shipment volume and depended on distance and shipment volume. Each distributor received roughly $250$ cases monthly, so the network handled about:

$$10 \times 250 = 2{,}500 \text{ cases per month}$$

Distributors received $21$ days' credit from Josh, but RDS collected and deposited their payments. Because RDS's compensation was fixed, a rise in workload could reduce agency profit even if Josh paid other transportation-related expenses.

Removing distributors: a service-design change

Josh eliminated distributors to simplify the chain, control distribution more directly, reduce system cost, and capture distributor margin. The redesigned chain was:

$$\text{Josh manufacturer} \rightarrow \text{RDS (C\&FA)} \rightarrow \text{retailer} \rightarrow \text{consumer}$$

RDS now had to serve all $180$ retailers across $14$ districts rather than $10$ distributors. Retailers ordered smaller quantities—$10$ to $35$ cartons per month; around half ordered $15$ or fewer; average order was $20$ cartons. Monthly movement became approximately:

$$180 \times 20 = 3{,}600 \text{ cartons per month}$$

About two-thirds of those shipments required repacking:

$$3{,}600 \approx 1{,}200 \text{ direct cartons} + 2{,}400 \text{ repacked cartons}$$

What changed operationally

The crucial distinction is that the redesign did not necessarily make trunk LTL transport much more complex—retailer demand would still be consolidated at the C&FA location—but it shifted repacking, last-mile service, retailer relationship management, and credit management to RDS.

Margin and incentive misalignment

Josh could capture the $7\%$–$10\%$ distributor margin, but RDS's remuneration did not change while its administrative and operating responsibility increased. This is a classic incentive alignment failure: a chain redesign allocates additional tasks and risk to one partner without matching compensation.

RDS's decision was therefore not purely short-term profit. It had to weigh additional manpower/administrative cost against strategic benefits: association with a prestigious brand, market credibility, learning for younger managers, and potential future business. Options included renegotiating the relationship, discontinuing it if unsustainable, entering trucking directly or through a partnership to control retailer service, and leveraging other agency lines under Logistics Solutions.

Exam tip: When an intermediary is removed, do not assume its margin is “saved” without cost. Identify the inventory, credit, repacking, relationship, delivery, and risk functions that must be reassigned—and ensure payment follows responsibility.

Key takeaways

• A C&FA is a coordinating and execution node whose fixed fee can become unprofitable when volume, fragmentation, or retailer-facing work rises.
• Distributor removal shifts hidden functions—risk buffering, credit, last-mile delivery, and relationship management—rather than making them disappear.
• The Josh redesign raised RDS volume from about $2{,}500$ to $3{,}600$ cartons per month and created roughly $2{,}400$ repacked cartons.
• Service design requires aligned scope, risk, incentives, and compensation; brand/reputation can be a legitimate strategic benefit but does not eliminate the need for economic viability.

Cold storage's supply-chain role

Cold storage is an inventory buffer for perishable agricultural commodities. Production is seasonal while consumption is year-round; storage enables produce harvested in a peak season to be released gradually. It connects producers, traders, wholesale markets, and retail markets, reduces spoilage/post-harvest loss, stabilises supply, and can improve farmer price realisation by avoiding distressed sales.

Cold storage is both capital intensive and energy intensive: refrigeration must run continuously, while commodity arrivals and capacity use are seasonal. The business therefore depends on capacity utilisation, energy efficiency, customer relationships, and the fit between commodity inflow/outflow cycles.

Hasmukhbhai's operating model

By 2006, Hasmukhbhai operated four profitable Ahmedabad facilities while many competitors were failing because of high electricity cost, weak utilisation, and poor management. His expansion capacity was about ₹3.5 crore using savings and borrowing; he generally operated around a $25{:}75$ equity-to-debt ratio and relied on close involvement to ensure the business could service debt.

His operations illustrate the service model:

Service revenue was split approximately $40\%$ fruit, $40\%$ pulses, and $20\%$ spices. The main customers were traders and commission agents; concentration was material, with a small number of large clients contributing a large share of category revenue. Their operations across Surat, Pune, Nashik, Jaipur, and Jodhpur could provide a relationship bridge to new locations.

Capacity, pricing, and cost economics

Each storage rack had approximately $288$ cubic feet of volume and could hold up to $7.5$ tons. Pricing depended on volume, weight, and temperature requirement.

Rent was charged for a full month even if goods stayed one day. This stabilises operator revenue, but creates an opening for a competitor that charges by actual days—provided it can offset lower revenue per customer through complementary markets/seasonality and sufficient utilisation.

Electricity was the dominant expense, approximately $45\%$ of total operating cost. Cold stores were classified as services and faced electricity duties of approximately $20\%$, higher than manufacturing. With rents constrained by competition, small tariff increases can materially hurt profitability. Energy-saving levers include tree cover, solar where feasible, and internal separators so work in one area does not cause temperature loss elsewhere.

Seasonality and utilisation

Commodity arrivals differ across the year: jaggery typically arrives in October–November, spices in December–February, and pulses in March–June; fruit varies by variety. Complementarity among commodities can smooth capacity demand.

At Mother Shree Cold Storage, average utilisation was roughly $80\%$. It approached full capacity in summer but fell to $50\%$–$70\%$ during monsoon and early winter. Because fixed capital and refrigeration costs continue, managing this seasonal utilisation swing is central to profit.

Expansion decision: Surat, Pune, or Mumbai

The decision is a trade-off among investment cost, demand potential, competitive intensity, trader-network access, infrastructure, regulation, electricity reliability, seasonal arrivals, and uncertain subsidy/land-price policy. Geographic diversification can reduce concentration risk, but an operator must be able to reproduce utilisation and customer relationships outside the home market.

From cold storage to cold chain

Storage alone does not preserve quality end-to-end. Cold-chain integration combines cold storage with refrigerated (reefer) transportation. Ordinary trucks may be acceptable for a short haul, but longer uncooled journeys can reduce product quality even when storage prevents losses. Reefer vehicles are limited because they require specialised assets and difficult return-load management; nevertheless, integrated storage and transport is the stronger service design for perishables.

Key takeaways

• Cold storage buffers seasonal production against year-round consumption, reducing spoilage and potentially improving agricultural price realisation.
• Its economics are governed by utilisation, electricity cost, rents, commodity-season complementarity, location, and trusted customer relationships.
• A full-month minimum charge stabilises revenue but can be challenged by more flexible pricing if the competitor can maintain utilisation.
• Cold storage should increasingly be designed with cold transport; preservation at the node alone is insufficient for long-haul perishables.

Professionalising a family logistics provider

Shreeji Transport Services grew from a traditional family transport company into a multi-service provider spanning full truckload (FTL), parcel/part load, bonded trucking, warehousing/3PL, and import-export logistics. By 2012–13 it had ₹680 million turnover, $250$ employees (including $200$ drivers), $25$ branches, and $209$ owned vehicles.

Family members had previously managed locations independently, causing duplicated truck purchases and uncoordinated strategy. Professionalisation changed governance from “who handles which city?” to clear functional and business ownership. A management information system (MIS) then made route-wise, segment-wise, and vehicle-wise profitability measurable, turning experience into evidence-based control.

Why revenue is not enough

Performance improved from 2006 to 2011—revenue CAGR $15\%$, profit-after-tax CAGR $22\%$, and return on capital employed from $14\%$ to $18\%$; more than $25\%$ of vehicles were debt-free. Yet rising receivables ($77$ to $90$ days), loss-making routes, $15\%$ idle capacity, and high overhead showed why growth does not guarantee profitability.

Exam tip: In asset-heavy logistics, turnover and fleet size are not the objective. Margin, route contribution, turnaround, utilisation, receivables, and return on capital determine whether growth creates value.

Route-wise profitability

FTL generated more than $60\%$ of revenue. A traditional belief was that longer routes must be more profitable because vehicles stay loaded for longer. Analysis of one month and $772$ trips disproved this: Chennai–Bengaluru, though shorter than Chennai–Mumbai, generated better contribution margins because freight rates were stronger and turnaround was faster with traffic available in both directions.

Route economics must consider more than distance:

New routes should therefore be tested in MIS before deployment, including destination-market and return-load conditions.

Parcel-service improvement and data quality

The Express Parcel Bakshish scheme rewarded timely driver delivery and increased parcel volume by $20\%$. Delivery time improved from $8.16$ days in April 2012 to $5.9$ days in March 2013. Destination-specific dispatches reduced costly trans-shipment by allowing direct origin-to-destination movement.

However, inconsistent customer-master data—one customer entered under several names—prevented reliable customer profitability analysis and hid potentially high-margin small customers. Thus data quality is strategic: bad master data prevents a logistics firm from understanding customer, route, and segment economics even when it collects large operational data volumes.

Driver incentives: effort versus asset condition

The Paiya Gumao Paisa Kamao scheme aimed to raise utilisation:

The scheme distorted behaviour because older trucks could not regularly reach $7{,}000$ km. Drivers avoided them, increasing idle capacity; drivers assigned older vehicles also had little reason to pursue the threshold. A uniform utilisation metric was therefore unfair when truck condition—not driver effort—constrained performance.

The design question is: should the incentive reward driver effort, or outcomes jointly determined by driver effort and vehicle condition? Incentives should be adjusted for asset capability or paired with fleet-condition improvement so they do not concentrate work on newer vehicles.

Managerial controls adopted

• Conduct a three-year comparative review and revamp underperforming bonded trucking.
• Focus on overdue receivables above $180$ days.
• Share monthly performance reports with customers to build credibility.
• Give all directors MIS access so decisions use the same facts.
• Set monthly targets for the gross-profit goal.
• Evaluate new routes through MIS before rollout.
• Make truck ownership strategic: hiring can yield better return on investment than ownership, despite the prestige of an owned fleet.

Key takeaways

• MIS enables route, segment, vehicle, and customer profitability control; professionalisation replaces intuition-only management.
• Long distance does not guarantee profit: rate, two-way load availability, and turnaround can make a shorter route superior.
• Service-time incentives and direct dispatch can improve parcel volume and delivery, but data quality is necessary to see true customer profitability.
• A common driver utilisation target can create perverse incentives when asset condition differs across vehicles.

Why rail service quality matters for cement

Cement plants locate near limestone rather than consumption centres, so bulk logistics determines competitiveness. Rail can move long-distance bulk loads economically, but road has gained share because it offers flexibility, smaller shipment sizes, and door-to-door service. Rail's logistics-service challenge is to act as a third-party logistics (3PL) provider offering reliable, integrated customer solutions rather than merely moving wagons.

Rajashree Cement's Malkhaid plant had capacity of $4.2$ million tons per year and served Bangalore, a major bulk cement market, using rail to Dodballapur. Cement companies' rail concerns included unsuitable wagon shortages, inefficient loading/unloading, weak inter-zonal coordination, and poor visibility of wagon availability/movement. These service failures can push even long-distance bulk traffic to road.

Dedicated assets and the closed rail circuit

The Own Your Wagon scheme allowed industrial customers to invest in dedicated wagons, improving wagon availability and providing a $22.5\%$ freight subsidy. Rajashree invested ₹600 million:

Annual freight savings were about ₹73 million, giving the reported return on investment of roughly $12\%$:

$$\text{ROI} \approx \frac{₹73\text{ million}}{₹600\text{ million}} \times 100 \approx 12\%$$

The closed circuit was:

$$\text{Load at Malkhaid} \rightarrow \text{rail to Dodballapur} \rightarrow \text{unload/distribute to Bangalore} \rightarrow \text{empty rake returns to Malkhaid}$$

A rake is the set of wagons moving as a train. The system used three rakes of $2{,}400$ tons each; each made about seven trips monthly, or about $21$ system trips. The indicative monthly carrying potential is:

$$3 \times 7 \times 2{,}400 = 50{,}400 \text{ tons per month}$$

This supported the stated Bangalore supply of approximately $52{,}000$ tons per month. The route was about $575$ km and required coordination across railway points/zones. Rake-cycle activities included empty-wagon placement, shunting/positioning, loading, locomotive availability, loaded transit, unloading, and empty return. Turnaround is the key asset-productivity measure because it determines trips per rake per month.

Baseline turnaround and capacity alternatives

The baseline cycle averaged $99$ hours:

Rajashree wanted to increase Bangalore supply from $52{,}000$ to $70{,}000$ tons per month. It considered:

1. Increase tons per trip by redesigning wagons and/or adding wagons per rake—requires new rolling-stock capital.
2. Increase trips using additional rakes—requires new stock, potentially adapting surplus oil tankers displaced by pipelines.
3. Increase trips with the same rakes by reducing turnaround from $99$ to a $74$-hour target—an efficiency solution rather than a capital-expansion solution.

The parties selected alternative 3. The largest obvious waste was the average $13$-hour wait after loading: the locomotive that delivered the empty rake was reassigned to another local movement, then a loaded rake waited for a replacement. Pre-loading idle time of $7.5$ hours was a second opportunity.

Engine on Load (EOL) experiment

Under Engine on Load (EOL), the locomotive remained technically available/attached to the rake through loading, avoiding post-loading detachment and a new engine request. Rajashree used its own locomotive for the physical loading movement, while the railway locomotive was kept available in the yard.

The agreement required loading within $3$ hours; time beyond this attracted a ₹3,800 per-hour penalty for Rajashree. The intended result was lower locomotive/wagon detention, a fall in turnaround from $99$ to about $80$ hours, and higher asset productivity:

Trial evidence and why EOL underperformed

The September–December 2003 trial covered $78$ trips: $45$ EOL and $33$ non-EOL. Of the non-EOL trips, $5$ were declined by Rajashree, $26$ by South Central Railway, and $2$ could not be attributed. Even EOL loading exceeded the $3$-hour free time: the fastest was $4$ hours; $9$ trips took $4$ hours, $13$ took $5$, $12$ took $6$, one took $6.5$, five took $7$, one took $8$, and four took $9$ hours.

EOL achieved terminal discipline but transferred delay into transit. The locomotive bringing an empty rake was sometimes too weak to pull the loaded rake through gradients on the route. Because EOL linked the incoming engine to the outgoing service, locomotive changes/adjustments during transit created delay. Thus, the design focused too narrowly on the terminal event rather than the end-to-end service.

Exam tip: A local improvement is not a system improvement if the bottleneck merely migrates. Assess whole-cycle turnaround and origin-to-destination delivery time, not only terminal detention or an individual task time.

Designing a rail logistics service, not an EOL rule

The EOL experiment raises contract, operational, and service-design questions:

Delivery time matters for cargo availability in Bangalore. Turnaround matters because customer-owned wagon assets must complete the circuit productively. A credible rail 3PL is responsible for financial arrangements, timeliness, and seamless material flow—not only individual operational elements.

Wider rail-service improvements for industrial customers

Key takeaways

• Closed-circuit rail logistics turns rake turnaround into a direct capacity and asset-productivity lever.
• Rajashree's $99$-hour baseline was driven notably by $13$ hours of post-load locomotive waiting; reducing it was a lower-capex alternative to buying more wagons/rakes.
• EOL improved terminal readiness but only reduced cycle time to about $92$–$93$ hours because unsuitable engine assignment shifted delay into transit.
• A railway acting as a 3PL should guarantee end-to-end delivery and turnaround, share penalties fairly, provide suitable power and visibility, and offer flexible, integrated logistics services.