Delivery Date Predictions in the Shopify Fulfillment Network
The Shopify Fulfillment Network (SFN) distributes merchant inventory across Shopify-certified warehouses in North America, positioning stock closer to buyers to reduce shipping time, cost, and carbon emissions. SFN recently extended this model to support affordable two-day delivery across the United States, which requires accurate delivery date estimates based on real-world logistics constraints.
SFN operates as an app within the Shopify platform, not as a bespoke integration. This design lets any third-party logistics (3PL) provider plug into the same infrastructure. The delivery date feature was built by three teams: one created a set of GraphQL APIs in the Shopify core that any 3PL can use to upload pre-computed delivery dates; another integrated those dates into the storefront, displaying them on product detail pages and at checkout; and a third built the SFN system that calculates and uploads its own dates through those APIs.
What Goes Into a Delivery Date
Rather than forcing 3PLs to express their operations through fine-grained platform primitives like operating days or processing capacity, Shopify lets each 3PL compute and upload its own delivery dates. This preserves fidelity for each network's particular processes. For SFN, the predicted date depends on four categories of input.
Inventory Location
Distance between the fulfillment center holding the item and the buyer's destination drives transit time. Delivery estimates therefore depend on which warehouses currently stock each SKU.
Product Characteristics
Items that are heavy, oversized, or hazardous may exclude certain carrier services. The delivery date must be based on a carrier that can legally and physically handle the merchandise.
Fulfillment Center Operations
Warehouse calendars include statutory holidays and exceptional closures such as severe weather. On operating days, staff time for picking and packing plus physical package processing limits affect when an order can ship. Reduced staffing from events like illness can lower capacity and lengthen processing times.
Carrier Schedules and Limits
Carriers such as UPS and USPS have their own holidays, modeled as transit days (package movement between hubs) and delivery days (final-mile delivery). Pickup schedules matter too: orders placed after the day's last pickup wait until the next one. Carriers may only dispatch a truck if there is sufficient volume, and truck dimensions impose a cap on pickup volume. These constraints influence carrier selection. Carriers publish expected Time in Transit; the first transit day is the day after pickup, and the last is delivery day. Some carriers deliver on Saturdays even though they do not move packages within their network on that day.
From Calculations to Uploads
SFN combines all these factors when deciding which fulfillment center processes a shipment and which carrier service transports it. On a regular interval, it selects a warehouse and carrier that optimize for sustainable two-day delivery for every merchant SKU to every US zip code, then uploads the resulting delivery date schedules to the Shopify platform.
The data volume is substantial, but much of it is shared across SKUs. SFN produces multiple schedules: each schedule reflects delivery dates for inventory available at the same set of fulfillment centers with similar physical characteristics like weight and dimensions. Every SKU maps to one schedule, and SKUs from different shops can share a schedule.
Real-Time Lookups at the Edge
When a buyer views a product page or reaches checkout, the delivery date shown is a direct lookup of the pre-computed schedule for that item to the destination address. The SFN app uploads these schedules and SKU mappings using the delivery date APIs, keeping the storefront lookup fast—under 100 ms.
The date displayed at checkout is sent back to SFN during order fulfillment, where it governs warehouse routing and shipping label selection, ensuring the fulfillment process meets the promised delivery date.
