What it means
Customers who can self-serve their tracking information are significantly less likely to contact support, and those who receive proactive tracking updates report higher post-purchase satisfaction.
Order tracking encompasses every touchpoint between order fulfillment and final delivery: the carrier scan at pickup, transit updates, out-for-delivery notifications, and delivery confirmation. From the merchant's side, tracking data lives in the carrier's system and is surfaced through tracking numbers assigned during fulfillment. From the customer's side, tracking is accessed via a link in a shipping confirmation email or by asking support. The friction between these two realities — customers want instant answers, tracking links are buried in emails — creates a large portion of WISMO support volume. Modern ecommerce brands address this through branded tracking pages, proactive SMS/email notifications at key milestones, and AI support agents that can answer tracking questions conversationally without redirecting customers to a third-party carrier site. Accurate tracking also helps merchants identify fulfillment issues (lost packages, carrier delays) early enough to intervene proactively.
Why it matters
Tracking transparency is a major driver of post-purchase trust. Customers who feel informed about their order's journey are more likely to buy again. Conversely, a lack of tracking visibility is one of the top drivers of support contacts, chargebacks, and negative reviews.
Related concepts, explained
These terms are part of the same idea, so they live here rather than on pages of their own.
Order Status
Order status is a real-time label describing where a customer's order currently sits in the fulfillment pipeline, typically moving through states such as payment confirmed, processing, fulfilled, shipped, out for delivery, and delivered.
Order status is the backbone of post-purchase support. Customers who have paid but not yet received their goods are in a state of uncertainty, and their primary anxiety — where is my stuff? — generates more inbound support volume than any other question in ecommerce. Status labels vary by platform but follow a common lifecycle: the order is placed and payment is confirmed, it enters a processing queue where the merchant picks and packs, it is fulfilled and handed to a carrier, tracked through transit milestones, and ultimately delivered. An AI support agent resolves order status inquiries instantly by querying the order management system directly, returning a human-readable summary that includes the current state, the carrier, and the tracking link — all without a human touching the ticket. For merchants on Shopify, this means the AI can look up any order by order number or email address and report its exact status in real time.
Order status questions are high-volume, repetitive, and completely resolvable by automation. For a Shopify store handling hundreds of orders daily, order status inquiries can represent 40–60% of total support volume. Handling each one with a human costs time and money that AI can eliminate entirely. More importantly, customers who get instant answers are more confident in the brand and less likely to initiate chargebacks or disputes out of frustration over unanswered uncertainty.
Fulfillment Status
Fulfillment status is the operational state of an order within the merchant's warehouse or fulfillment center, indicating whether items have been picked, packed, and dispatched to the carrier — distinct from shipping status, which begins once the carrier has the package.
Fulfillment status describes what has happened on the merchant side of the order lifecycle, before the carrier takes over. The common states are unfulfilled (the order has been paid but not yet picked), partially fulfilled (some items in a multi-item order have shipped while others haven't), and fulfilled (all items have been dispatched to the carrier). For customers watching the clock on an expected delivery, knowing whether their order is unfulfilled versus with a carrier is a meaningful distinction that affects their next action — contacting the merchant if unfulfilled, or tracking the shipment if it has already shipped. An AI support agent that can surface this distinction — and explain it clearly — prevents the frustration of customers who think nothing is happening when the reality is that their order is in the packing queue.
Misaligned expectations about fulfillment create a disproportionate share of support escalations. A customer who ordered two days ago and sees 'unfulfilled' may panic, when in fact their order is within the merchant's stated processing window. AI agents that explain fulfillment status in plain language — 'your order is currently being prepared for shipment and typically ships within one business day' — preempt escalations that have nothing to do with an actual problem.
Tracking Number
A tracking number is a unique alphanumeric identifier assigned by a shipping carrier to a specific shipment, which customers and merchants use to query the carrier's system for real-time location and delivery status updates.
When a merchant fulfills an order and hands it to a carrier, the carrier assigns a tracking number to the parcel. This number is the key that unlocks real-time visibility into the shipment's journey through the carrier's network — from initial scan at the origin facility through transit hubs to the final delivery scan at the customer's door. Tracking numbers follow carrier-specific formats: UPS uses 18-digit codes beginning with 1Z, FedEx uses 12- or 15-digit numbers, USPS uses 22-digit codes. When a customer asks where their package is, they need two things: the tracking number and the carrier, or a direct link to the carrier's tracking page. An AI support agent resolves this in one step by pulling both from the order record and returning a formatted tracking link the customer can click directly.
Tracking inquiries account for a large portion of ecommerce support volume, and they are entirely automatable. Customers who receive a tracking link instantly — without waiting for a human to look up the order and copy-paste the number — have a dramatically better post-purchase experience. For merchants, every tracking inquiry resolved by AI is cost savings and faster resolution time.
Shipping Carrier
A shipping carrier is a logistics company contracted to physically transport packages from the merchant's fulfillment location to the customer's delivery address, providing tracking infrastructure and delivery services at agreed service levels and transit times.
Shipping carriers form the physical bridge between a merchant's warehouse and a customer's door. Major carriers in the US market include USPS, UPS, FedEx, and DHL, each with distinct service levels (ground, express, overnight), pricing structures, and geographic strengths. Regional carriers like OnTrac and LSO serve specific geographic markets at competitive rates. For ecommerce merchants, carrier selection affects delivery speed, shipping cost, package protection, and the quality of tracking data available to customers. From a support perspective, the carrier identity matters because tracking systems, claims processes, and delivery guarantees differ by carrier — and customers experiencing delivery issues need carrier-specific guidance. An AI support agent that knows which carrier is handling a given shipment can provide accurate tracking links, explain carrier-specific delivery windows, and guide customers through the appropriate lost package or damage claim process.
Carrier-related delivery issues — delays, missed deliveries, damaged packages, lost shipments — generate significant support volume that falls on the merchant even though the carrier is responsible for the physical outcome. Customers don't distinguish between the merchant and the carrier in their support expectations. An AI agent that can identify the carrier, explain delivery status, and initiate the appropriate resolution path turns what would be a frustrating experience into a managed one.
Delivery Window
A delivery window is the estimated range of dates within which a customer's order is expected to be delivered, derived by adding the merchant's order processing time to the carrier's estimated transit time for the selected shipping service and destination.
A delivery window has two components: the merchant's processing time (how long it takes to pick, pack, and hand off to the carrier) and the carrier's transit time (how long the carrier takes to move the package to the customer's address). Both are estimates and both are variable — processing can be delayed by backlog, and carrier transit varies by destination zone, service level, and operational conditions. Customers form expectations based on the delivery window shown at checkout, and when that window passes without delivery, they generate support tickets. An AI support agent that knows the promised delivery window, the actual fulfillment date, and the carrier transit estimate can give a precise answer to 'when will my order arrive' rather than a vague reassurance, and can accurately identify whether a delivery is genuinely late versus within a still-valid estimate.
Delivery window questions are among the most emotionally loaded in ecommerce support because they intersect customer expectation with perceived merchant reliability. A customer who was promised 3–5 business days and is on day 6 is angry; a customer who understands they are on day 4 of a 5–7 day window is patient. The difference is information. AI agents that surface accurate, real-time delivery window calculations — accounting for the actual ship date, not the order date — dramatically reduce false 'it's late' escalations.
Delivery Estimate
A delivery estimate is a projected delivery date or date range communicated to a shopper at checkout or post-purchase, based on the order's processing time, carrier transit time, and the shopper's delivery location. Accurate delivery estimates set expectations that directly reduce 'where is my order' support contacts.
Delivery estimates sit at the intersection of expectation setting and promise keeping. Shoppers make decisions around delivery: they plan to be home, they buy a gift with an event in mind, they time a replenishment purchase. A specific, accurate delivery estimate ('arrives by Thursday, June 5') is far more useful than a vague shipping time range ('3–7 business days') because it gives the shopper a concrete expectation to plan around. Inaccurate delivery estimates — whether overestimated to set conservative expectations or underestimated to improve conversion — both create problems. Over-estimated dates delay purchase decisions; under-estimated dates generate disappointed shoppers who contact support when their Thursday item doesn't arrive until Monday. AI support agents interact with delivery estimates when shoppers want to confirm an estimate, when an order is running behind the stated estimate, and when a shopper placed an order for a specific date-sensitive occasion and needs to understand whether the timing is achievable.
Delivery estimates are a primary driver of both pre-purchase conversion and post-purchase satisfaction. At checkout, a clear 'arrives by [specific date]' message removes the uncertainty that causes cart abandonment — shoppers who need something by a date can confirm it will arrive in time. Post-purchase, shoppers who were given an accurate estimate have calibrated expectations and contact support less frequently. Brands that invest in accurate, order-specific delivery estimates — rather than generic shipping time ranges — see improvements in both conversion rates and WISMO contact rates simultaneously.
Split Shipment
A split shipment occurs when a single customer order is divided into two or more separate packages dispatched at the same time or at different times, each with its own tracking number, typically because items are stocked at different locations or have different availability timelines.
When a customer orders multiple items, merchants don't always ship them together. A split shipment happens when items ship from different warehouses, when some items are in stock and others are backordered, when an order is too large for a single carton, or when a logistics optimization routes items through different fulfillment nodes. Each split package has its own tracking number and its own delivery timeline. From the customer's perspective, they ordered one order and now have two or more tracking numbers arriving on different days — which is confusing without explanation. The most common customer complaint from split shipments is 'I only received part of my order' when the second package is simply a few days behind. An AI support agent that knows an order was split, can explain why, and can provide all the tracking numbers prevents this confusion from becoming a support ticket.
Without AI support, split shipments create a wave of avoidable support volume — customers contacting the merchant to report a missing item that is actually in a separate package in transit. For merchants who routinely split shipments (multi-warehouse fulfillment, dropship items, pre-order items), this is a predictable and preventable support burden. AI agents that detect split fulfillment and proactively communicate it to customers eliminate this category of ticket almost entirely.
Shipping Tracking
Shipping tracking is the process of monitoring a package's movement through the carrier network using a unique tracking number, providing location and status updates from carrier pickup to final delivery.
When a merchant hands a package to a carrier, the carrier scans it and generates a tracking number — a unique identifier that can be used to query the carrier's system for the package's current location and status. Tracking events are created at each carrier scan: origin facility acceptance, in-transit scans at intermediate hubs, arrival at the destination facility, out-for-delivery, and delivery confirmation (often with GPS or signature data). This event stream is the backbone of post-purchase communication. The challenge is that tracking data is fragmented across dozens of carriers, each with their own API, data format, and scan frequency. Merchants use tracking aggregation platforms (Aftership, EasyPost, Route) or AI support agents with built-in carrier integrations to consolidate this data into a single view that can be queried conversationally. The quality of tracking data varies by carrier and service level — USPS First Class scans less frequently than FedEx Express — and AI agents must handle gaps gracefully without alarming customers unnecessarily.
Shipping tracking data is the answer to the most-asked question in ecommerce support. Any merchant not surfacing this data in real time through their support channel is forcing customers to call, email, or hunt through shipping confirmation emails — all of which are unnecessary friction.
Shipping Notification
A shipping notification is an automated message — typically email or SMS — sent to a shopper when their order is dispatched from the warehouse, including a tracking number, carrier name, and a link to the live tracking page. It marks the transition from 'order placed' to 'order in transit.'
Shipping notifications serve a critical anxiety-reduction function in the post-purchase journey. From the moment a shopper places an order, a clock starts in their mind: they are waiting. The shipping notification is the signal that the wait has a defined endpoint — their package is physically moving toward them, and here is proof. A high-quality shipping notification includes the carrier name, tracking number, a direct deep-link to the carrier's tracking page (not just the homepage), the estimated delivery date, and a clear way to reach support if anything looks wrong. Brands that send proactive, informative shipping notifications see measurable reductions in inbound 'where is my order' (WISMO) contacts — because the shopper already has the answer. AI support agents handle the residual WISMO volume by looking up tracking data in real time and surfacing the latest status within the conversation, without requiring the shopper to navigate to a carrier website.
WISMO (Where Is My Order) is the single highest-volume support contact category for most ecommerce brands, often representing 20–40% of all inbound tickets. Every WISMO query that arrives means a shopper didn't find the information they needed from the shipping notification. Improving notification quality and enabling an AI to handle WISMO in real time are the two most direct levers for reducing this volume — and since WISMO is a pure operational ticket rather than a revenue-generating interaction, automation ROI is especially high.
Delivery Notification
A delivery notification is an automated message — email, SMS, or push — triggered when a carrier marks a shipment as delivered, confirming to the shopper that their package has arrived. It is the final step in the standard post-purchase communication sequence and the starting point for 'delivered but not received' support queries.
The delivery notification sounds simple — 'your package arrived' — but it sits at a critical juncture in the customer journey. For most shoppers it prompts immediate action: check the door, check with a neighbor, check a mailbox. When the package is there, the journey ends on a high note. When it isn't — whether due to a carrier mis-scan, porch theft, or delivery to the wrong address — the delivery notification becomes the starting gun for a stressful support interaction. Carriers sometimes mark packages as delivered before physical arrival; packages get stolen post-delivery; apartment buildings have complex delivery logistics that confuse carriers. AI support agents handle 'delivered but not received' as a structured workflow: verify the carrier scan, check whether GPS confirmation data exists, advise the shopper on common hiding spots and neighbor checks, and if those steps fail, initiate a missing package claim or issue a replacement — all within a single automated conversation.
'Delivered but not received' is among the most emotionally charged support contacts an ecommerce brand receives. Shoppers are understandably frustrated, and the outcome — whether a replacement or a refund — has direct financial implications. AI agents that handle this workflow consistently and empathetically, without requiring shoppers to repeat themselves across channels, turn a potentially brand-damaging experience into one that demonstrates commitment to making things right. Consistent, fast resolution of delivery issues measurably improves post-delivery repurchase rates.
Branded Tracking Page
A branded tracking page is a merchant-hosted order status interface that displays live carrier tracking information within the brand's own visual design and domain, keeping the post-purchase experience on-brand instead of sending shoppers to a generic carrier website.
The standard post-purchase flow sends shoppers to carrier tracking pages — FedEx, UPS, USPS — for shipment status. These pages are functional but strip the experience of all brand identity, miss upsell and engagement opportunities, and train shoppers to associate post-purchase with carrier experiences rather than the merchant. Branded tracking pages host the same live carrier data within the merchant's own domain, design system, and tone. A shopper tracking a package from a premium brand sees the brand's aesthetic, not a generic carrier interface. Brands use this high-engagement touchpoint — shoppers check tracking pages an average of 3–4 times per shipment — to cross-sell related products, promote loyalty programs, collect post-purchase survey responses, and embed a support chat widget for immediate assistance. AI support agents often link directly to the branded tracking page as the primary resolution for WISMO contacts, pairing the tracking link with contextual information about the current status.
Post-purchase touchpoints are underused real estate. The tracking page is visited multiple times by nearly every shopper who placed an order, yet most brands send that traffic to a carrier website and lose the engagement entirely. A branded tracking page reclaims that attention, reduces support contacts by surfacing status clearly, and drives incremental revenue through contextually relevant product recommendations. Brands that deploy branded tracking see measurable WISMO reduction alongside lift in repeat purchase rates from the promotional and cross-sell real estate the page creates.
Order History
Order history is the chronological record of all purchases a shopper has made through a store account, displaying order numbers, dates, items purchased, amounts charged, fulfillment status, and available actions such as reorder, return initiation, or support contact for each transaction.
Order history serves two distinct audiences simultaneously: shoppers and support agents. For shoppers, it is the self-service record of everything they've purchased — a reference point for reordering, tracking, initiating returns, and reviewing past transactions. For support interactions, order history is the context layer that transforms vague requests like 'I need help with something I bought last month' into specific, actionable support cases. An AI support agent with real-time access to order history can identify which order the shopper is referencing without asking them to find an order number, verify return eligibility against the purchase date, check whether a previous return was processed, and proactively surface relevant information based on the order's current state. This access dramatically reduces the back-and-forth in support conversations and enables the AI to resolve issues in a single interaction rather than a multi-message exchange.
Most shoppers do not remember their order numbers. When support agents — human or AI — require shoppers to provide an order number before helping them, a significant percentage fail to locate it and either abandon the interaction or call in frustration. AI agents with direct Shopify order history access skip this friction entirely: they look up recent orders by email address and identify the relevant one immediately. This is particularly important for high-repurchase-rate stores where a shopper may have dozens of past orders and genuinely cannot pinpoint which one needs attention without help.
How Bookbag helps
Conversational Tracking Lookup
Customers can ask Bookbag 'Where is my order?' in natural language and receive a precise status update — carrier, last scan location, estimated delivery — without navigating to a separate tracking page.
Multi-Carrier Support
Bookbag handles tracking across all major carriers (UPS, FedEx, USPS, DHL, and regional carriers), so the experience is consistent regardless of how an order was shipped.
Delivery Exception Alerts
When a shipment shows a failed delivery attempt, weather delay, or customs hold, Bookbag flags it and proactively contacts the customer or escalates to a support agent.
Go deeper
Guides & benchmarks
See it in the product
Frequently Asked Questions
See Bookbag in action
Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.