Workflow

Audit Your Dropshipping Workflow with Fetch's Logs

September 2, 2026 · 7 min read

A profitable dropshipping operation isn't just about finding winning products; it's about a lean, efficient workflow. When you're managing hundreds or thousands of orders, even minor inefficiencies compound into significant losses. Fetch Order Tracking provides comprehensive logs, not just for tracking and refunds, but as a forensic tool to audit and optimize your entire dropshipping workflow.

Understanding Fetch's Log Data

Fetch captures every critical event and data point for each order. This isn't just a 'tracking number updated' notification; it's a detailed timeline of your order's journey, from placement to delivery or refund. Key fields you'll find in your Fetch logs (and thus in your Google Sheet) include:

eBay Order ID / AliExpress Order ID: Direct links to the source orders.
Tracking Number: The logistics identifier.
logistics_status: AliExpress's internal status for the shipment (e.g., 'WAIT_SELLER_SEND_GOODS', 'SELLER_SEND_GOODS', 'BUYER_ACCEPT_GOODS', 'DELIVERED').
order_status: AliExpress's overall order status (e.g., 'FINISH', 'WAIT_BUYER_ACCEPT_GOODS', 'FUND_PROCESSING', 'REFUND_COMPLETED').
gmt_create: Timestamp when the AliExpress order was created.
gmt_pay_success: Timestamp when payment was confirmed on AliExpress.
gmt_send_goods: Timestamp when the seller marked the item as shipped.
gmt_arrival: Estimated arrival time.
gmt_signed_for: Timestamp when the package was signed for.
gmt_refund: Timestamp when a refund was initiated or completed.
end_reason: Reason for order closure (e.g., 'BUYER_ACCEPT_GOODS', 'FINISH', 'REFUND_COMPLETED_SELLER_AGREE').
refund_status: Detailed status of any refund request.
dispute_status: Status of any initiated dispute.

Auditing Your Supplier Performance

Your suppliers are the backbone of your operation. Fetch logs allow you to quantify their performance and identify weak links.

Shipping Speed Analysis

Order Creation to Shipment: Calculate the average duration between gmt_pay_success and gmt_send_goods for each supplier. A supplier consistently taking 3-5 days to ship after payment, versus another shipping within 24 hours, highlights a clear performance difference.
Shipment to Delivery: Analyze the time between gmt_send_goods and gmt_signed_for. Filter by specific shipping methods (e.g., ePacket, Standard Shipping) to see actual transit times versus advertised times.

Identify suppliers with consistently high gmt_pay_success to gmt_send_goods intervals. This often points to a slow processing time before the item even leaves their warehouse, directly impacting customer satisfaction.

Refund and Dispute Rates

Filter your Fetch data for orders where refund_status is not empty or dispute_status is not 'NO_DISPUTE'. Group these by supplier. A supplier with a 5% refund rate due to 'ITEM_NOT_RECEIVED' or 'DAMAGED_ITEM' is a red flag compared to one with a 0.5% rate. This directly impacts your profit margins and eBay seller metrics.

Optimizing Your Internal Processes

Your own team's efficiency, or lack thereof, can be exposed by the logs.

Order Placement Latency

If you're using a manual or semi-automated order placement system, compare the timestamp when an eBay order is received (from your eBay API or internal system) with gmt_create in Fetch. A significant delay here indicates a bottleneck in your order processing, potentially leading to 'out of stock' issues on AliExpress or longer overall delivery times.

Proactive Refund Management

Fetch flags potential refunds with gmt_refund and refund_status. Audit how quickly your team acts on these. Are you initiating communication with the buyer as soon as refund_status changes to 'WAIT_SELLER_AGREE'? Or are you waiting until the buyer opens an eBay case? Proactive communication, informed by Fetch's data, can mitigate negative feedback and reduce case resolution times.

Identifying Tracking and Logistics Issues

Fetch's detailed logistics_status and order_status fields are invaluable for pinpointing specific logistics problems.

Stuck Shipments

Filter for orders where logistics_status remains 'SELLER_SEND_GOODS' for an unusually long period (e.g., 10+ days without further updates) or where logistics_status never progresses beyond 'WAIT_SELLER_SEND_GOODS' for orders past their gmt_send_goods. This indicates a tracking number that hasn't updated or a package that's genuinely stuck. These are prime candidates for follow-up with the supplier or proactive buyer communication.

Delivery Confirmation Discrepancies

Compare gmt_signed_for with the delivery date reported by the buyer (if any discrepancy arises). While rare, this can help identify issues with specific carriers or even fraudulent claims. Fetch provides the objective timestamp from the logistics provider.

Refining Your Automation Rules

If you're using Fetch to trigger automations (e.g., updating eBay tracking, sending customer notifications), the logs help you fine-tune these rules.

Tracking Update Timing: Audit how long it takes for a new tracking number to appear in Fetch after gmt_send_goods. This informs when you should trigger your eBay tracking update to ensure the buyer receives the most current information promptly.
Refund Notification Triggers: Analyze the lifecycle of your refunds. If refund_status changes to 'REFUND_COMPLETED_SELLER_AGREE', how quickly does your system detect and act on it? This is crucial for managing your eBay returns and ensuring timely refunds to your customers.

By regularly auditing your Fetch data in Google Sheets, you move beyond reactive problem-solving to proactive workflow optimization. You gain a quantitative understanding of where your operation excels and where it leaks profit and time. This data-driven approach is essential for scaling your dropshipping business efficiently.

Ready to put your dropshipping workflow under the microscope? Get started with Fetch Order Tracking today.

Try the fetcher → More guides