Marked shipped but no tracking sent: what the buyer can actually see
A shipped label does not establish that tracking was recorded or sent. Locate the fulfillment entry for the relevant items, compare its tracking details with the actual shipment, then check whether that entry triggered a customer notification and what the message contained. Where WooCommerce's documented Fulfillments feature is present, drafts send no customer notifications; fulfilling a draft or updating a fulfilled entry can notify according to its toggle. Even a sent message may not be delivered. Classify the first confirmed gap before answering the buyer, and do not claim carrier acceptance from the store label alone.
For: A research-only merchant's support or fulfillment lead investigating an order described as shipped when the buyer has no tracking information.
Start with the specific order and the items the buyer expected. Identify which system produced the word shipped: the store status, a fulfillment feature, an extension or a warehouse message. Record the active platform, feature and extension version. Do not assume that every WooCommerce installation exposes the Fulfillments system described in the current documentation, or that a third-party extension uses its status vocabulary.
In that documented system, an individual fulfillment contains products and quantities, a draft or fulfilled status, and shipping information such as carrier and tracking details. Open the relevant entry instead of stopping at the order-level label. An order can have more than one fulfillment, so confirm that the tracking you found belongs to the items in question. Order-level fulfillment is calculated from the constituent records; it is not independent evidence that a carrier accepted a parcel.
Read the physical shipment evidence separately. A tracking reference and the carrier's latest event can tell different stories from a store entry. If you can find only the store's fulfilled mark, describe carrier acceptance as unconfirmed. The buyer's report that a parcel arrived is another record to preserve; it does not prove which notification your store sent earlier.
Distinguish missing tracking from a missing handoff
If the correct fulfillment exists but contains no tracking, check the actual shipping or warehouse record. Tracking present there but absent from the store is a handoff gap you can name. Tracking absent from both systems is not yet an email problem: establish whether this shipment had a tracking service and who holds its dispatch record. If the shipment genuinely has no tracking, tell the buyer that accurately rather than creating a number or borrowing another parcel's reference.
If the order has no matching fulfillment record, give the fulfillment owner the exact missing link: the accepted order and items with no corresponding shipment entry. Preserve any warehouse confirmation that already exists. Do not create a fulfilled entry solely to silence the buyer's question before physical dispatch is established.
If tracking is present, compare the carrier and reference against the shipment for this order. A populated field can still point to the wrong parcel. Keep the original mismatch in the internal record, and have the authorized owner correct the association using the active system's procedure. The useful diagnosis is which record failed to carry the right information, not a general claim that email is broken.
Trace the notification from the fulfillment event
WooCommerce's documented draft fulfillments do not notify customers when created, edited or removed. Adding tracking to a draft therefore does not mean the buyer was sent that tracking. Fulfilling a draft can send a notification according to its notification toggle. Updates or removal of a fulfilled fulfillment can also notify when enabled. Check the state and toggle at the relevant action; a setting visible now is not proof of its earlier value.
For the actual notification, look for the event time, send outcome and retained outgoing content in the systems your store uses. If tracking was entered only after the earlier message, that earlier message could not contain it. If the fulfillment stayed in draft or notification was disabled, you have an intended-notification explanation before investigating delivery. If the historical setting or message is unavailable, record that gap instead of declaring a cause.
WooCommerce's email troubleshooting distinguishes handing a message to the mail system from the buyer receiving it. A sent record supports the former. Compare the actual outgoing message, where retained, with the buyer's report of what arrived. Tracking omitted from the outgoing content is a content or data-path question; correct content recorded as sent but not received is a delivery question. Do not repeatedly change fulfillment states just to force emails while the shipment record is already accurate.
Give the buyer the verified information and close the right gap
When the tracking record is correct, provide the buyer with the relevant carrier information through your established customer channel and state the latest verified stage. If the shipment stage or tracking remains unknown, say which record is being checked and who will provide the next update. Avoid calling a parcel in transit merely because an internal record says fulfilled. A follow-up commitment should concern your next communication, not an invented delivery date.
Assign the repair to the gap you established: the fulfillment owner for missing dispatch or tracking records, the store or integration owner for a failed transfer into the order, and the notification or mail owner for the relevant sending stage. More than one gap can exist. A later resend may answer the buyer while leaving the original handoff defect unresolved; record both outcomes.
Stripe's dispute-prevention guidance recommends tracking and delivery confirmation. Preserve the original shipment evidence in authorized records; if tracking is later submitted in a Stripe dispute, its guidance says issuers do not follow links and a screenshot is needed. That evidence does not guarantee an outcome. For a recurring store-to-message mismatch, describe the observed gap in a Prism checkout-review consultation and confirm the investigation scope, responsibilities, fees and terms before work.
Tracking-and-notification trace
Use one real order and the affected parcel or item group. Record non-sensitive match results, timestamps, states and the next owner. Keep tracking references, private links and original messages in the merchant's authorized systems. Read the rows in order: a missing upstream record cannot be repaired solely by resending a downstream message.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Tracking-and-notification trace. The last column is for temporary notes.
Trace point
Where to inspect
How to interpret it
Your finding and owner
Active fulfillment system
Where to inspectThe store's actual fulfillment feature or extension, version and the origin of the shipped label.
How to interpret itUse its documented behavior. WooCommerce's Fulfillments model applies only where present; an extension may differ.
Fulfillment record on the order
Where to inspectThe entry covering the affected products and quantities, including its status and timestamp.
How to interpret itNo matching entry indicates a record or handoff gap. Fulfilled in the application alone does not establish carrier acceptance.
Tracking and carrier match
Where to inspectCompare the fulfillment details with the actual warehouse or shipping record inside authorized systems.
How to interpret itTracking outside the store but absent on the order is a transfer gap. No tracking anywhere requires clarification of the dispatch record or service used.
Actual shipment stage
Where to inspectThe dispatch evidence and latest carrier event, with time, or an explicit record that neither is available.
How to interpret itReport only the supported stage. A number or store label alone cannot establish transit or delivery.
Notification trigger state
Where to inspectThe fulfillment event and its notification toggle at that time, where retained.
How to interpret itDraft creation, edits and removal do not notify in the documented WooCommerce feature. A later setting cannot prove the earlier setting.
Outgoing message contents
Where to inspectThe retained message or authorized sending record corresponding to the fulfillment event.
How to interpret itCheck whether tracking was present when this message was generated. Missing content differs from correct content that was not received.
Buyer's received message
Where to inspectCompare the reported message type and time with the outgoing record without copying customer details here.
How to interpret itSent does not establish received. If receipt or message content cannot be checked, keep the result unknown.
Next owner and buyer update
Where to inspectThe first confirmed gap, the person assigned and the verified information available to the buyer now.
How to interpret itCorrect that gap and communicate the current facts. Record whether a resend answered the buyer and whether the underlying handoff was repaired.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
WooCommerce Fulfillments behavior is feature-dependent; third-party plugins can extend the statuses. No introduction version or installed feature is assumed.
Application fulfillment, physical dispatch, carrier acceptance, a notification trigger and message receipt are separate facts. No delivery date or dispute outcome follows from one label.
Do not place customer messages, private tracking links, payment data or credentials in the public consultation form.
WooCommerce order fulfillment — checked 2026-09-29. Where present, Fulfillments records items, quantities, status and tracking. Draft changes do not notify; fulfilling or changing fulfilled records can notify according to the toggle. Order-level fulfillment derives from its records, and plugins can extend the model.
Stripe dispute and fraud prevention — checked 2026-09-21. Stripe recommends tracking and delivery confirmation. Issuers do not follow tracking links, so screenshots are required when using tracking as dispute evidence; this does not determine an individual claim.
WooCommerce email troubleshooting — checked 2026-09-21. A sent message has been handed to the mail system and may still not reach the buyer. Sending and delivery failures are different investigation stages.
Get help with store operations
Need help with the order, email or fulfillment step itself?