8. Digital Platforms, E-Commerce and Last-Mile LogisticsIntroduction and ContextLogistics has traditionally been organized around relatively stable flows between known business partners: a manufacturer shipped to a distributor, a distributor supplied a retailer, and the retailer served the consumer. Digital commerce has altered this pattern. Orders now originate from marketplaces, mobile applications, social-commerce channels, stores, subscription services and business-to-business portals. Inventory may be distributed across factories, regional warehouses, retail outlets, micro-fulfilment centres and third-party sellers. The final delivery may be performed by a parcel carrier, a crowd-sourced driver, a store employee or a customer collecting the order from a locker. This environment makes information architecture as important as physical infrastructure. A logistics system must determine where inventory is located, which stock is genuinely available, how an order should be promised, which facility should fulfil it, how transport should be orchestrated, and how the customer will be informed. It must also manage failed deliveries, substitutions, cancellations, exchanges and returns. Digital platforms provide the connecting layer. They match buyers and sellers, coordinate capacity and demand, expose services through application programming interfaces (APIs), collect operational data and support transactions. Their value, however, is not created by technology alone. Platform governance, data quality, service design, commercial incentives, cybersecurity and operational discipline determine whether digital connectivity produces reliable logistics performance. Learning ObjectivesAfter studying this chapter, the reader should be able to: 1. Explain the structure and strategic role of digital marketplaces and logistics platforms. 2. Distinguish e-commerce fulfilment, omnichannel fulfilment, parcel systems and digital freight brokerage. 3. Design information flows for distributed inventory and order orchestration. 4. Evaluate last-mile delivery models using service, cost, capacity and sustainability criteria. 5. Analyse platform business models, governance issues, risks and performance measures. 6. Apply these concepts to a practical e-commerce logistics case. From Transactions to Logistics PlatformsA digital platform is an organizational and technological arrangement that enables interactions among two or more participant groups. In logistics, these groups may include consumers, merchants, carriers, drivers, warehouses, customs agents, payment providers and technology partners. A platform does not necessarily own the assets used in the transaction. Its primary function may be coordination, matching, information exchange, transaction settlement or orchestration. A marketplace connects buyers with sellers. An e-commerce marketplace may hold inventory itself, allow independent sellers to list products, or combine both arrangements. A digital freight platform connects shippers requiring transport with carriers possessing vehicles and capacity. A last-mile platform may allocate delivery tasks, optimize routes, provide driver applications and communicate estimated arrival times. These are different platform categories, but they share several characteristics: - participants require a common digital interface;
- data must be exchanged in standardized and timely form;
- the platform establishes rules for participation and performance;
- value increases when more relevant participants use the system; and
- trust must be created through identity, ratings, contracts, payment controls and dispute resolution.
The platform business model is often described through network effects. A larger buyer population can attract more sellers; more sellers can improve assortment and attract more buyers. In freight, more shippers may attract carriers, while a larger carrier pool improves service availability for shippers. Network effects are not automatically beneficial. Congestion, poor-quality sellers, fraudulent listings, unreliable capacity or excessive complexity can reduce value as participation grows. Consequently, platform operators must manage the quality and structure of the network rather than merely maximize user numbers. E-Commerce Fulfilment and the Omnichannel ChallengeE-commerce fulfilment is the process through which an electronic order becomes a delivered product. It includes order capture, payment authorization, inventory allocation, picking, packing, dispatch, transportation, delivery confirmation and, where relevant, return processing. The process is information-intensive because the customer expects a precise promise before the physical operation has begun. The basic order lifecycle is: 1. The customer selects products and submits an order. 2. The commerce system validates price, payment, address, tax and availability. 3. An order management system determines the fulfilment location and delivery promise. 4. The warehouse or store receives a fulfilment request. 5. Items are picked, packed, labelled and handed to a carrier or collection point. 6. Transport events are recorded and communicated to the customer. 7. Delivery, exception handling and post-delivery service are completed. Omnichannel fulfilment extends this model across stores, websites, applications, marketplaces, contact centres and social channels. The customer experiences one brand, even though the transaction may involve several systems and facilities. Common operating models include ship-from-warehouse, ship-from-store, click-and-collect, buy-online-pick-up-in-store, store-to-store transfer, drop-shipping and marketplace fulfilment. The central difficulty is that inventory visibility is not the same as inventory availability. A system may show ten units in a store, but some may be damaged, reserved for another customer, undergoing cycle counting or physically misplaced. Effective available-to-promise calculations therefore consider on-hand stock, reservations, inbound supply, safety stock, expected shrinkage and fulfilment lead time. Distributed inventory creates flexibility but also increases the need for accurate master data, location discipline and real-time event capture. Information Architecture for Distributed InventoryA suitable architecture normally separates the systems that perform different responsibilities while ensuring that they exchange consistent data. A typical arrangement includes: - a digital commerce or marketplace layer for product discovery, pricing and checkout;
- an order management system (OMS) for order validation, allocation, splitting, cancellation and orchestration;
- an inventory or distributed order management layer for availability and sourcing decisions;
- warehouse management systems (WMS) for receiving, storage, picking, packing and shipping;
- a transportation management system (TMS) for carrier selection, planning, tendering and freight settlement;
- a delivery-management system for route optimization, driver tasks, proof of delivery and customer communication;
- a customer relationship or service system for complaints, refunds and enquiries; and
- an analytics layer that combines transactional and event data.
APIs commonly support real-time interaction, while electronic data interchange (EDI), file transfer and event streams remain important in established supply networks. The architectural principle is not that every event must be instantaneous. Rather, the timing and accuracy of information must be appropriate to the decision being made. A customer promise may require near-real-time availability, whereas a historical freight invoice can be processed in a batch. Important information objects include product identifiers, locations, inventory status, customer addresses, delivery windows, order lines, shipment labels, carrier services, tracking events, invoices and return authorizations. Data standards are essential because a product described as “available,” “allocated,” “picked” or “delivered” must have consistent meaning across organizations. An order orchestration engine applies business rules. It may select the nearest facility, minimize split shipments, protect high-demand inventory, meet a service-level agreement, or choose the lowest total cost. The cheapest individual shipment is not necessarily the cheapest fulfilment decision. A split order may increase parcel and handling cost, while a distant shipment may increase transport time and carbon impact. The relevant objective is often total fulfilment cost subject to service constraints. Parcel Systems and Last-Mile DeliveryParcel logistics differs from full-load transport because it handles many small consignments with high stop density, standardized labels and extensive sorting. A parcel network may include collection points, consolidation centres, regional hubs, delivery depots, lockers and final delivery routes. Information systems generate labels, scan parcels at transfer points, identify exceptions and provide tracking events. The last mile is the movement from a local facility or final transportation node to the recipient. It is frequently the most complex and expensive stage because deliveries are dispersed, addresses may be uncertain, recipients may be absent and customers often demand narrow time windows. Urban congestion, parking constraints, building access and security restrictions further complicate execution. Delivery models include home delivery, parcel lockers, pickup points, scheduled delivery, same-day delivery, crowdsourced delivery and collection from retail stores. Each model represents a trade-off. Home delivery offers convenience but may generate failed attempts and low drop density. Lockers consolidate deliveries and improve recipient flexibility but require suitable locations and customer adoption. Same-day service can create differentiation but requires local inventory, reliable cut-off times and sufficient order density. Delivery orchestration coordinates the sequence from shipment release to proof of delivery. It includes carrier selection, capacity reservation, route construction, driver assignment, navigation, recipient communication, exception management and settlement. Route optimization may use vehicle capacity, delivery windows, travel time, driver hours, road restrictions and service priority. Optimization is therefore a constrained operational decision, not simply a search for the shortest distance. Customer visibility should be based on meaningful events rather than indiscriminate data volume. Useful milestones include order accepted, inventory allocated, packed, handed to carrier, out for delivery, delivery delayed, delivered and returned. Estimated time of arrival should be recalculated when new evidence changes the expected route or stop sequence. Overly precise but unreliable promises damage trust more than appropriately broad and accurate windows. Digital Freight PlatformsDigital freight platforms are used in brokerage, spot-market matching, contract tendering, shipment visibility and freight payment. A shipper posts a load with origin, destination, equipment, weight, timing and special requirements. Carriers offer capacity or accept a tender. The platform may verify credentials, calculate rates, issue documents, monitor GPS or telematics data and support payment. The main value proposition is reduced search and transaction cost. Shippers gain access to a wider carrier pool and potentially faster capacity discovery. Carriers may reduce empty running and improve asset utilization. Yet a platform must address asymmetric information: the shipper may not know whether capacity is reliable, and the carrier may not know whether loading conditions, waiting time or payment practices are acceptable. Ratings, insurance verification, digital contracts, performance history and transparent rules help reduce this uncertainty. Freight platforms can be asset-light, asset-enabled or vertically integrated. An asset-light platform coordinates independent transport providers. An asset-enabled operator may combine software with contracted or owned capacity. A vertically integrated model controls more of the physical operation. The choice affects capital requirements, service control, scalability and exposure to operational risk. Returns and Reverse Information FlowsReturns are not merely a reverse movement of goods. They are a decision process involving authorization, customer eligibility, transport method, inspection, disposition, refund and inventory status. A return may be restocked, repaired, refurbished, recycled, liquidated or discarded. Each disposition affects financial recovery and customer experience. A returns-management process should capture the reason for return, product condition, serial or batch information, original order, refund status and expected disposition. Return data can reveal product defects, misleading descriptions, packaging weaknesses or sizing problems. Thus, reverse logistics information should flow back to merchandising, procurement, quality and product-design functions. A well-designed system separates physical receipt from financial resolution. A customer may receive a refund when the parcel is scanned by an approved carrier, upon receipt at a processing centre, or only after inspection. The policy must balance fraud risk, customer convenience and working-capital impact. Clear authorization rules and exception controls are particularly important for high-value goods. Platform Governance, Trust and PerformancePlatform governance defines who may participate, which data are visible, how prices and commissions are determined, how performance is measured and how disputes are resolved. Governance is a strategic issue because platform power can influence seller access, carrier earnings, customer choice and market competition. Key governance questions include whether the platform uses participant data to compete with participants, whether ranking algorithms are explainable, how fraudulent reviews are handled, and whether participants can export their operational data. Contract terms should clarify service standards, liability, insurance, payment timing, data ownership, intellectual property and termination rights. Performance should be measured across four dimensions. Customer measures include promise accuracy, on-time delivery, order completeness, delivery success and complaint resolution. Operational measures include order cycle time, pick accuracy, first-attempt delivery, route adherence, inventory accuracy and return processing time. Financial measures include fulfilment cost per order, cost per stop, commission revenue, carrier utilization and recovery value from returns. Sustainability measures include emissions per parcel, delivery density, packaging intensity and failed-delivery miles. A useful governance principle is to optimize the end-to-end outcome rather than an isolated departmental target. For example, maximizing warehouse utilization may increase delivery distance; minimizing delivery cost may reduce customer retention; and maximizing marketplace assortment may increase counterfeit or unreliable listings. Balanced metrics and cross-functional accountability are therefore essential. Applied Case: Northstar Home RetailBackgroundNorthstar Home Retail is an illustrative regional retailer selling household products through stores, a website and two external marketplaces. It operates a central distribution centre and 45 stores. The website displays store inventory, but inventory files are updated every four hours. Orders are allocated mainly to the central distribution centre, even when a nearby store has stock. Situation and ProblemDuring a promotional period, order volume increased sharply. Customers received delivery promises that could not be met because store inventory was inaccurate and warehouse capacity was constrained. Some orders were split into multiple parcels, while other orders were cancelled after payment. The company also had limited visibility of third-party carrier events and handled returns through email and spreadsheets. AnalysisThe problem was not simply insufficient transport capacity. Northstar lacked a unified inventory status model, a clear order-orchestration policy and integrated event visibility. Its systems treated “on hand” as “available,” did not reserve stock consistently, and could not compare the total cost of alternative fulfilment locations. Returns data were not connected to the original order, preventing analysis of product and service problems. Approach and SolutionNorthstar introduced a distributed order-management layer. Store stock was classified as available, reserved, damaged, display-only or under verification. Orders were allocated using rules that considered promised delivery date, proximity, split-shipment cost, store processing capacity and product handling requirements. Stores received simplified pick-and-pack tasks through a mobile application. Carrier APIs were integrated with the order system so that shipment creation, scan events, delivery status and exceptions were visible to customer service. The company offered pickup points and lockers for selected urban areas and used delivery windows rather than unsupported exact-time promises. A returns portal generated authorization records, linked each return to its order line and captured disposition decisions. A performance dashboard tracked promise accuracy, inventory accuracy, first-attempt delivery, split-order rate, fulfilment cost and return cycle time. Governance rules specified which sellers could use marketplace fulfilment and required minimum tracking and cancellation performance. OutcomeThe redesigned process improved decision quality by creating a common view of inventory and order events. More importantly, it allowed Northstar to identify the causes of poor service rather than merely report late deliveries. The case illustrates that omnichannel capability depends on process and data governance as much as on adding delivery options. Learning Points1. Distributed inventory creates value only when stock status is trustworthy. 2. Order orchestration should evaluate service and total cost together. 3. Customer visibility depends on integrated operational events. 4. Returns provide diagnostic information, not only cost. 5. Platform participation requires explicit standards and accountability. Risks, Limitations and Professional ConsiderationsDigital logistics platforms introduce operational and strategic risks. System outages can prevent order release, label generation or payment confirmation. Cyberattacks may expose addresses, payment data, driver identities or commercial rates. Poor master data can create systematic promise failures. Algorithmic allocation may disadvantage small sellers or favour platform-owned inventory without transparent justification. Privacy requires particular care in last-mile systems because delivery addresses, geolocation, behavioural data and proof-of-delivery images can identify individuals. Data should be collected for legitimate purposes, protected through access controls and retained only as long as justified. Organizations must also comply with applicable consumer-protection, electronic-transactions, taxation, labour, transport and data-protection requirements. Automation does not eliminate managerial responsibility. Route algorithms require accurate constraints; artificial-intelligence forecasts require monitoring for bias and drift; and automated refunds need controls against abuse. Human escalation remains necessary for vulnerable customers, safety incidents, disputed deliveries and exceptional commercial decisions. Common implementation mistakes include digitizing fragmented processes without redesigning them, treating every real-time integration as valuable, ignoring seller and carrier incentives, measuring only delivery cost, and launching narrow delivery promises before capacity is proven. Pilot programs, data-quality controls, fallback procedures and phased integration reduce these risks. Emerging Directions and Best PracticesCurrent development is moving toward composable commerce, event-driven integration, predictive ETA, autonomous parcel sorting, robotics in micro-fulfilment, digital twins of distribution networks and AI-assisted customer service. Urban logistics is also experimenting with consolidation centres, cargo bikes, parcel lockers and coordinated delivery zones. These developments may improve density and visibility, but they do not remove the need for sound process design. Organizations should adopt the following practices: - define a single business meaning for each inventory and shipment status;
- maintain authoritative product, location, customer and carrier master data;
- design order orchestration around total cost and promised service;
- use APIs and event standards with documented ownership and fallback procedures;
- expose accurate, useful milestones rather than excessive technical detail;
- integrate forward and reverse logistics data;
- establish platform rules for quality, security, liability and dispute resolution;
- test algorithms against exceptional and vulnerable-user scenarios; and
- review performance through customer, operational, financial and sustainability measures.
Chapter SummaryDigital platforms connect participants, information and transactions across contemporary logistics networks. Marketplaces coordinate buyers and sellers, digital freight platforms match transport demand with capacity, and delivery platforms orchestrate parcel and last-mile activities. E-commerce fulfilment requires coordinated order capture, inventory allocation, warehouse execution, transport and customer communication. Omnichannel operations add complexity because inventory is distributed across stores, warehouses and external sellers. The order-management layer is central to this environment. It must distinguish physical stock from genuinely available stock, select fulfilment locations, manage split orders and communicate reliable promises. Parcel and last-mile systems depend on scanning, routing, delivery events and exception management. Returns require reverse information flows and disposition decisions. Platform governance determines trust, accountability, data rights and participant quality. Successful implementation combines architecture, analytics, process redesign, cybersecurity, privacy and balanced performance measures. Key TermsDigital platform: A digital system and governance arrangement that enables interactions among multiple participant groups. Marketplace: A platform that connects buyers with sellers and supports discovery and transactions. Network effect: The change in platform value resulting from changes in the number or quality of participants. Omnichannel fulfilment: Coordinated fulfilment across channels such as stores, websites, applications and marketplaces. Order management system: A system that validates, allocates, orchestrates and monitors customer orders. Distributed order management: Coordinated sourcing and fulfilment of orders from multiple inventory locations. Available-to-promise: The quantity and timing of inventory that can credibly be committed to a customer. Warehouse management system: Software controlling warehouse receiving, storage, picking, packing and dispatch. Transportation management system: Software supporting transport planning, tendering, execution and settlement. Last mile: The final movement of a shipment to the customer or collection point. Delivery orchestration: Coordinating carriers, routes, drivers, events, exceptions and customer communication. Parcel network: A system of nodes, sortation processes and transport links handling individual consignments. Digital freight platform: A platform matching shippers and carriers and supporting freight transactions. Proof of delivery: Evidence that a shipment reached the intended recipient or location. Reverse logistics: The movement and management of goods from the customer back toward recovery, repair or disposal. Platform governance: Rules governing participation, data, ranking, performance, payment and disputes. API: A defined interface that allows software systems to exchange data or invoke functions. Event-driven integration: An architecture in which systems communicate operational occurrences as events. First-attempt delivery: Successful delivery on the first planned delivery attempt. Fulfilment cost: The total cost of processing, handling and delivering an order under a defined scope. Review QuestionsShort Answer Questions1. What distinguishes a digital marketplace from a digital freight platform? 2. Why is inventory visibility not necessarily the same as inventory availability? 3. Identify four major functions of an order-management system. 4. What information should a returns process capture? 5. Why are delivery events important for customer visibility? Long Answer Questions1. Explain how omnichannel fulfilment changes inventory and order-management requirements. 2. Discuss the role of APIs, event data and master data in a digital logistics architecture. 3. Evaluate the principal trade-offs among home delivery, lockers, pickup points and same-day delivery. 4. Explain how platform governance affects trust, competition and service quality. 5. Discuss the risks and controls associated with AI and automation in last-mile logistics. Analytical / Application Questions1. A retailer has accurate warehouse stock but unreliable store stock. Design an order-allocation policy that uses stores without damaging promise accuracy. 2. A carrier platform has many registered drivers but frequent failed pickups. Identify likely information and governance causes and propose performance measures. 3. An e-commerce company is considering free same-day delivery. Analyse the inventory, density, capacity, customer, financial and sustainability conditions that should be satisfied before launch. 22. Multiple Choice Questions with AnswersQuestion 1Which function is most directly associated with distributed order management? A. Designing product packaging artwork B. Selecting the most suitable fulfilment location for an order C. Recruiting warehouse security personnel D. Calculating corporate income tax Correct Answer: B. Selecting the most suitable fulfilment location for an order Question 2Why can a store showing ten units on hand still be unable to fulfil a new order? A. On-hand stock may include reserved, damaged or misplaced units B. All store inventory is automatically allocated to carriers C. Customer orders never use store inventory D. Parcel systems cannot process quantities above five units Correct Answer: A. On-hand stock may include reserved, damaged or misplaced units Question 3Which situation best illustrates a network effect in a freight platform? A. A larger relevant carrier pool improves capacity options for shippers B. A warehouse reduces its electricity consumption C. A driver prints a paper delivery label D. A retailer changes its product colour range Correct Answer: A. A larger relevant carrier pool improves capacity options for shippers Question 4What is the principal purpose of meaningful shipment events such as “out for delivery” and “delivered”? A. To replace all physical transport activities B. To provide useful operational and customer visibility C. To guarantee that every delivery is profitable D. To eliminate the need for inventory records Correct Answer: B. To provide useful operational and customer visibility Question 5Which decision best reflects total fulfilment-cost thinking? A. Always ship from the nearest facility regardless of split shipments B. Always select the carrier with the lowest quoted rate C. Compare handling, transport, split-order and service consequences together D. Allocate every order to the largest warehouse Correct Answer: C. Compare handling, transport, split-order and service consequences together Question 6A returns system records only the refund amount. Which important capability is missing? A. Linking the return to product condition and disposition B. Calculating employee attendance C. Creating advertising slogans D. Selecting office furniture Correct Answer: A. Linking the return to product condition and disposition Question 7Which is a platform-governance issue? A. Whether participant performance standards and dispute rules are transparent B. Whether a parcel has a barcode printed on it C. Whether a warehouse floor is painted blue D. Whether a customer prefers morning coffee Correct Answer: A. Whether participant performance standards and dispute rules are transparent Question 8Why are failed deliveries especially significant in last-mile logistics? A. They can create additional travel, cost, capacity use and customer dissatisfaction B. They automatically improve route density C. They eliminate the need for proof of delivery D. They reduce the number of delivery events to zero Correct Answer: A. They can create additional travel, cost, capacity use and customer dissatisfaction Question 9Northstar’s practice of treating all on-hand store stock as available primarily creates which risk? A. Unreliable promises and later order cancellation B. Excessive accuracy in customer communication C. Automatic reduction in return volume D. Guaranteed lower transport emissions Correct Answer: A. Unreliable promises and later order cancellation Question 10Which control is most appropriate when introducing AI-based route or allocation decisions? A. Remove all human escalation channels B. Use the algorithm without monitoring after deployment C. Test constraints and outcomes, monitor drift and retain exception handling D. Allow the model to change contractual service rules without approval Correct Answer: C. Test constraints and outcomes, monitor drift and retain exception handling
|