Delivery Slot Promising at Shopify Checkout: How Rate Tools Like ShipperHQ and nShift Integrate, and Where Live Capacity Fits in 2026

Delivery slot promising at checkout means showing a shopper only the delivery dates and time windows the operation can actually keep. On Shopify, third-party tools add those options through carrier-calculated shipping rates, delivery customization Functions or, on Plus, checkout UI extensions. Rate tools such as ShipperHQ and nShift build the options from configured rules and carrier data, while capacity-based promising, which Locus provides through Delivery Promise Management, checks live vehicle, route and cut-off capacity before a window is shown. The two answer different questions, “which options and prices fit this cart?” and “can the network hold this window?”, and the integration pattern decides whether they work together.

Why Slot Promising at Checkout Matters: The Business Case

A slot is a commitment, and shoppers and retailers both pay when it breaks.

• In Locus’s November 2025 consumer survey of 1,000 US and 2,000 UK consumers, only 9% (US) and 7% (UK) of consumers believed retailers always meet fast or guaranteed delivery commitments.
• The same survey found that 93% of US consumers say delivery performance affects their view of a brand, and missed delivery windows were the top US last-mile complaint at 21%.
• AlixPartners’ 2026 home delivery survey found that more than half of consumers would stop buying from a retailer after one or two missed deliveries, and that delivery reliability has overtaken price in importance.
• FedEx’s 2026 Future of Logistics Intelligence report, which surveyed 700 leaders, found that only 18% can always intervene when a delivery goes wrong, so a promise checked before it is made matters more than a fix afterwards.

The checkout is where the promise is made, so it is where capacity needs to be known.

Why Locus Leads for Capacity-Based Slot Promising

Rate and checkout tools decide which options a cart sees. Locus is built to decide which windows the network can keep, and three things set it apart.

Recognized by analysts and selected after evaluation. Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its analyst recognition page. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s press release says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.

A promise checked against every leg. Delivery Promise Management checks each slot against live capacity from the cut-off at the origin warehouse, through the linehaul, to the vehicle at the door, and a window reaches checkout only when every leg clears. Own-fleet legs are checked against the day’s actual vehicles and routes, and carrier legs against their capacity and service rules. Feasible slots return in under a second by service level, so tiers can be priced, and when a slot is refused the cause comes back: route full, cut-off passed or no fleet rostered.

Tested against a real order book. In a test against a full week of a retailer’s order book with capacity deliberately tightened, 98.5% of orders received a delivery window the network could keep, the remaining 1.5% were refused rather than given a window it could not hold, and every re-planning pass held the windows already committed. Orders left without a slot fell from 3.6% to 1.5% once live re-optimization ran.

Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries. Locus’s public pages document a slots operation and promise retrieval, confirmation and update in its order API, but they do not document a native Shopify connector, so the Shopify patterns below are integration designs to build and confirm, not a published connector.

How Slot Promising Works at Shopify Checkout

Shopify gives third parties three routes into the delivery step, and each has limits that shape what a slot tool can do. The six steps below follow a shopper through checkout.

1. The shopper reaches the delivery step

Shopify’s CarrierService posts the cart, destination and items to your public callback URL. The store must be on the Advanced plan or higher on yearly billing, have the feature as a paid add-on or be a development store, and the app needs the write_shipping scope.

2. The app asks the promise engine

Your callback passes the destination, items, service levels and order size to the capacity check. A rate tool applies rules and carrier data at this step, and a capacity engine such as Locus’s slots operation would be called instead or as well.

3. The engine checks every leg

Cut-off at the origin, the linehaul and the vehicle or carrier at the door are checked against live capacity, so only feasible windows survive. A rules-based tool checks lead times, cutoffs, blackout days and transit limits at this step instead.

4. Options return inside the timeout

Rates return as an array with a service name, service code, currency and total price, and optional minimum and maximum delivery dates. Shopify’s read timeout is 10 seconds under 1,500 requests a minute, 5 seconds up to 3,000 and 3 seconds above that, there is no retry, and a timeout or error switches checkout to the shop’s backup rates.

5. The shopper picks and the window is confirmed

Shopify’s date-picker tutorial shows a checkout UI extension saving the chosen date to a metafield, and extensions on the shipping step are Plus-only. The app then confirms the window with the promise engine so that it is held, not just displayed.

6. Changes are tested before they reach a driver

Re-plans that would break a confirmed window are discarded, and orders running behind are flagged early enough to move up the queue. Rule-based date tools stop before this step, and planning-linked promising continues through it.

Two other Shopify limits matter. The delivery customization Function can rename, sort and hide delivery options, but the documentation describes no way to add rates, so it filters what other tools supply. And identical rate requests are served from cache for 15 minutes after a success, so slot availability that changes within minutes needs a design that varies the request or accepts short-lived staleness.

ShipperHQ vs nShift vs Capacity-Based Promising: Key Differences

Vendor-stated counts differ between pages, so confirm any figure you plan to cite. ShipperHQ’s 2026 shipping intelligence platform is in early access, and nShift’s AI ETA is an optional service with a broader rollout to follow. Both vendors build dates from rules and carrier data, which suits carrier-fulfilled parcel promises. Their pages stop short of live fleet capacity, which matters most for owned-fleet and scheduled delivery.

What to Look for in a Slot Promising Integration

Where it runs in checkout

Ask whether it uses carrier-calculated rates, a Function, a checkout extension or an app, and which Shopify plans each route requires. Plan conditions are the most common surprise, since extensions on the shipping step need Plus.

What a slot is based on

Check whether availability comes from rules and carrier data or from live capacity, and whether per-slot capacity can be set or computed. A configured cap holds on a normal day and breaks on the days that matter.

Timeout and caching design

Ask how the tool answers inside the callback timeout, what happens under a 3 second limit at peak volume and how it handles Shopify’s rate cache.

Refusal and alternatives

Look for a reason when a slot is refused and an alternative offered, so a full route sends the shopper to the next best window and not to a blank.

Link to planning

Check that a confirmed window flows into routing and that re-plans cannot break it, since a promise that planning does not know about is only a label.

Slot Promising in Action: Real-World Results

A worked example on illustrative numbers. The figures below are illustrative, not benchmarks, so replace them with your own order and capacity data. A delivery zone has a configured cap of 200 orders a day across its slots, but real capacity varies with vehicles and routes: 200 on a normal day, 150 when two vehicles are down and 260 on a peak day. Daily demand is 190, 190 and 240 orders. A broken promise costs $12 in reshipping, support and credits, and an order refused when capacity existed costs $15 in lost contribution.

The configured cap breaks 40 promises on the short day, costing $480, and turns away 40 orders on the peak day, costing $600. The live check keeps every promise and offers the 40 short-day shoppers another slot. The cap is not wrong on a normal day, which is why a rate tool’s rules and a capacity check often run together.

An ASEAN apparel retailer. The retailer had no trustworthy checkout date and carriers that each reported their own status codes. With one harmonized status standard synced to its order and warehouse systems and a network-aware delivery date at checkout, WISMO and returns queries fell by more than 40%, and carrier onboarding dropped from 3 months to 3 days. Read the apparel case study.

A North American retailer. The retailer consolidated six systems into one, with $1M+ in savings, 80%+ less manual dispatch and 99%+ on-time delivery, while its ERP and WMS stayed the systems of record. Read the retailer case study.

Common Checkout Slot Mistakes to Avoid

Treating a date range as a promise. A minimum and maximum delivery date from rules or carrier history is an estimate, so ask what the network can actually hold.

Setting slot caps once. A cap that ignores vehicles, routes and cut-offs breaks on short days and wastes capacity on peak days, so review it against live capacity.

Ignoring the callback timeout. A slow capacity check is replaced by backup rates, so measure response time under peak load, not on a quiet afternoon.

Choosing by checkout plugin alone. Rate tools and capacity checks do different jobs, so decide which question you need answered before comparing features.

How Locus Approaches Slot Promising at Checkout

Locus, the world’s first Decision-Intelligent, Agentic TMS, checks each slot against live capacity and plans routes against 250+ real-world constraints through its Route Planning System. It runs eight agents (Orchestrator, Capacity, Carrier, Dispatch, Hub, Customer, Settlement and the Mycroft co-pilot) inside six governance mechanisms, including autonomy levels and an execution sandbox. Its order API documents a slots operation, and promise retrieval, confirmation and update with serviceability maps, so a storefront or OMS can ask for feasible windows at order capture, and its tracking page lets customers reschedule after checkout. Locus’s public pages do not document a native Shopify connector, rate-tool integrations or callback timing under Shopify’s limits, so during evaluation ask how a Shopify carrier-service callback or checkout extension would call the slots API, what response times it sees at your volume and whether a reference store is live. To see how Locus would promise windows at your checkout, schedule a demo.

For e-commerce and logistics leaders asking how to promise delivery slots at Shopify checkout, Locus offers a capacity check that complements rate and checkout tools, so the options a shopper sees are ones the network can hold and the promise carries through to planning and dispatch.

Frequently Asked Questions

How does delivery slot promising work at Shopify checkout? Shopify posts the cart to a carrier-service callback and expects rates back, with optional minimum and maximum delivery dates. Date or slot selection is app-built, and checkout UI extensions on the shipping step need Shopify Plus.

What is the difference between ShipperHQ, nShift and capacity-based promising? ShipperHQ and nShift build delivery options, dates and, for ShipperHQ, slots from configured rules and carrier data. Capacity-based promising checks live vehicle, route, cut-off and carrier capacity before a slot is shown.

Does ShipperHQ support time slots on Shopify? Its documentation states time slots on Shopify, with slots defined by weekdays, hours and zones and limited to table-rate or store-pickup carriers. The Shopify calendar needs its Enterprise plan with Enhanced Checkout.

Does nShift offer delivery slot selection? nShift’s checkout product page states delivery options, estimated delivery times and an AI-predicted ETA. Its Shopify listing mentions delivery date and time without detail, so confirm slot selection with the vendor.

Can Locus integrate with Shopify checkout? Locus documents a slots and promise API but no native Shopify connector. A carrier-service callback or checkout extension could call the API, so confirm the design, response times and a live reference with Locus.

How fast does a slot check need to be at Shopify checkout? Shopify’s carrier-service callback times out after 3 to 10 seconds depending on request volume, with no retry. Locus’s Delivery Promise Management returns feasible slots in under a second.