LitBuy Tracking Guide: How to Read SourceTrack and Order Status

A carrier scan can tell you that a package moved. It cannot tell you whether LitBuy connected that package to the intended order, completed warehouse intake, placed the item on a shelf or generated QC images. Those are separate operational events. LitBuy’s current SourceTrack page makes that separation visible by querying a third-party tracking number and returning five timestamps instead of one reassuring status.

The five fields are Order Time, Purchase Completion Time, Warehouse Receipt Time, Inbound Shelving Time and QC Image Generation Time. Read together, they form a trace of internal handoffs. Read carelessly, they invite false conclusions. The useful question is never simply “Where is my item?” It is “Which documented handoff is complete, which one is still blank, and what evidence belongs to the gap?”

Prepare the query packet before searching

SourceTrack asks for a third-party tracking number. Copy that identifier from the current order record or seller shipment evidence rather than retyping it from memory. Preserve the carrier name, LitBuy order number, seller name, product shorthand and the time you copied the number. This small packet keeps the query result tied to the correct purchase.

Normalize only harmless formatting. Remove accidental spaces introduced by copying, but do not delete letters, leading zeros or carrier prefixes because they look unusual. If two records show different numbers, do not guess which is newer. Save both sources and ask which number is active before building an investigation around one.

Search one number at a time. A consolidated haul can contain several seller shipments, and one seller can split a purchase into multiple packages. A result for one number does not clear the other packages. Give each tracking number its own row, then connect those rows to the same order only when the account evidence supports that relationship.

Treat a blank field as unknown, not failure

The public SourceTrack interface displays a dash when no result has populated a timestamp. A dash is not a diagnosis. It may mean that the queried number is wrong, the event has not happened, the event is not yet reflected, or the number is not associated with a record the tool can return. SourceTrack itself does not explain which possibility applies.

Before contacting support, run a three-part check: confirm every character in the number, confirm the seller or order actually supplied it, and confirm you have not confused an international parcel number with the third-party number requested by the page. Record the search time. If the result remains blank, your question can state exactly what you queried and which account evidence connects it to the order.

Do not manufacture a deadline from the absence. The SourceTrack screen lists milestones but does not publish a guaranteed interval between them. A useful escalation is based on a verifiable mismatch or a material gap in your own records, not a universal timer borrowed from another buyer.

Read Order Time as the start of the trace

Order Time anchors the record without validating every later purchasing action. Use it to confirm that the result belongs to the expected buying window. If the timestamp predates your request or falls far outside the source evidence, first suspect an identifier mismatch rather than assuming an extraordinary processing error.

Compare Order Time with your payment or submission record only as a consistency check. Different systems can record different events and time zones. Do not demand exact equality unless LitBuy explicitly labels both timestamps as the same action. Preserve the displayed label, value and time zone instead of renaming the field in your notes.

If several products share one order, keep the tracking-level row separate from the order-level row. Order Time may identify the commercial record, while later physical events belong to a specific package. This distinction becomes essential when a seller ships items separately.

Use Purchase Completion Time as a commercial boundary

Purchase Completion Time indicates that the purchasing stage reached the event named by LitBuy. It should not be silently translated into seller dispatch, carrier acceptance or warehouse receipt. Those are different facts and SourceTrack provides later fields for the physical handoff.

At this point, check that your saved product identity, variation, quantity and accepted price still match the order record. SourceTrack is not a product-detail viewer, so the timestamp cannot validate those attributes. It tells you when a stage was recorded, not whether the seller supplied the right version.

When Order Time exists but Purchase Completion Time does not, keep the question with the purchasing record. Cite the LitBuy order identifier and the exact SourceTrack number, but ask about the incomplete purchasing milestone rather than asking the warehouse to locate a package that may not yet exist.

Separate Warehouse Receipt from carrier delivery

Warehouse Receipt Time is the first SourceTrack field explicitly tied to warehouse receipt. That makes it a better internal handoff marker than a seller-carrier page that merely says delivered. The two can be compared, but they are not interchangeable.

A carrier event proves what that carrier recorded. Warehouse Receipt Time proves what LitBuy’s SourceTrack record displays. If the carrier shows delivery while Warehouse Receipt remains blank, preserve the carrier tracking number, delivery event, destination shown, delivery time and any proof-of-delivery detail. Then ask whether that exact package has been matched to the LitBuy order.

Do not combine several delivered packages into one complaint. A receiving team needs the number attached to the missing receipt event. One precise row is more useful than a screenshot collage containing unrelated orders.

Understand the shelving handoff

Inbound Shelving Time is a distinct milestone after warehouse receipt. Its presence tells you the system recorded the shelving event named by the interface. By itself, that event cannot validate every product attribute or show buyer acceptance.

Compare the receipt and shelving timestamps to see which side of the handoff is complete. If receipt exists but shelving remains blank, the package has crossed one boundary but not the next displayed one. Keep the question focused on intake processing and order matching. Do not jump ahead to parcel submission or international routing.

Once shelving appears, reconnect the tracking row with the corresponding warehouse item record. Match order identity and quantity before reviewing pictures. If the warehouse entry cannot be reconciled with the source row, resolve identity first; a later timestamp does not cure an earlier mismatch.

Read QC Image Generation Time literally

QC Image Generation Time records when the image-generation milestone appeared. It does not say that the item passed inspection, that every hidden feature was checked, or that the buyer approved shipment. Those are decisions, not timestamps.

Open the available warehouse evidence and compare it with the original order specification. Check only observable attributes: count, visible color, labels, exterior condition, obvious accessories and any measurable detail the current interface provides. When a required view is missing, ask one narrowly framed question in the current account workflow.

Keep the timestamp as provenance for the image set. If new or replacement images appear later, label them separately instead of overwriting the earlier record. This creates a clean sequence of what evidence existed when you made each warehouse decision.

Measure gaps without inventing service promises

Create four intervals: order to purchase completion, purchase completion to warehouse receipt, receipt to shelving, and shelving to QC image generation. These intervals help you locate delay, but they are descriptive. The public SourceTrack page does not state that each gap must stay below a particular number of hours.

Use your own rows to detect exceptions within the same haul. If four packages progress and one remains at an earlier milestone, verify that the stalled row has the correct number and comparable circumstances. Seller timing, carrier behavior, package labeling and item handling can differ, so comparison is a prompt for investigation, not proof of fault.

Record changes instead of refreshing without a log. A simple “checked at / latest populated field / next action” column prevents duplicate messages and shows whether the system is moving. It also makes a support request concise when the record truly stops advancing.

Write an escalation that follows the trace

A useful message contains six facts: LitBuy order identifier, third-party tracking number, seller or carrier, latest SourceTrack milestone, its displayed time and the next missing milestone. Add one supporting screenshot only when it proves the mismatch. Ask for one action, such as confirming whether the received package has been matched to the order.

Keep product disputes and tracking disputes separate. A wrong size with complete timestamps is a warehouse-evidence issue. A correct order with a blank receipt field is a handoff issue. Mixing both into one request can send the case to the wrong stage.

The SourceTrack audit checklist

1. Copy the exact third-party tracking number from a saved record.
2. Attach carrier, seller, LitBuy order and product shorthand.
3. Keep one row for every tracking number.
4. Record all five displayed timestamps without renaming them.
5. Treat dashes as unknown states, not automatic failures.
6. Compare carrier delivery with Warehouse Receipt separately.
7. Reconnect shelving to the correct warehouse item.
8. Review QC images as evidence, not approval.
9. Log each check and the next missing milestone.
10. Escalate one precise handoff with one requested action.