Workflow
Untangling AliExpress Combined Orders for eBay Tracking
You’ve seen it: a customer buys five items from your eBay store, all sourced from different AliExpress suppliers. AliExpress, in an attempt to “optimize” logistics, combines these into a single package with one tracking number. While this might seem efficient on their end, it creates a significant headache for dropshippers trying to manage individual eBay order statuses, track refunds, and reconcile finances in their Google Sheet.
The core problem is the mismatch: one AliExpress tracking number corresponds to multiple eBay Order IDs. If you simply apply that single tracking number to all five eBay sales in your sheet, Fetch Order Tracking will correctly update the logistics_status for all of them. However, when a refund occurs for *one* of those items, the gmt_refund and end_reason fields will only appear for the specific AliExpress order that was refunded, not necessarily for all five entries associated with the combined tracking. This can lead to missed refund opportunities or incorrect status updates for your eBay customers.
The Manual Split: When AliExpress Combines
The ideal scenario is one-to-one: one eBay Order ID maps to one AliExpress Order ID and one tracking number. When AliExpress combines orders, you need a strategy to maintain this clarity in your tracking sheet.
Fetch Order Tracking processes each row in your sheet independently. If a row contains an AliExpress Order ID, it will fetch the latest status for that specific order. If it contains an AliExpress tracking number, it will fetch the latest status for that tracking number. When combined orders happen, you need to ensure each eBay sale row is linked to its *original* AliExpress Order ID, even if the tracking number is shared.
Scenario Walkthrough: Five eBay Sales, One AliExpress Package
Let's say you have five eBay Order IDs:
- eBay Order ID: 12345678901 (AliExpress Order ID: AE1)
- eBay Order ID: 12345678902 (AliExpress Order ID: AE2)
- eBay Order ID: 12345678903 (AliExpress Order ID: AE3)
- eBay Order ID: 12345678904 (AliExpress Order ID: AE4)
- eBay Order ID: 12345678905 (AliExpress Order ID: AE5)
AliExpress combines AE1, AE2, AE3, AE4, and AE5 into a single package with tracking number TN1234567890. Your Fetch Order Tracking sheet setup should look like this initially:
| eBay Order ID | AliExpress Order ID | AliExpress Tracking Number | order_status | logistics_status | gmt_refund | end_reason |
|---|---|---|---|---|---|---|
| 12345678901 | AE1 | |||||
| 12345678902 | AE2 | |||||
| 12345678903 | AE3 | |||||
| 12345678904 | AE4 | |||||
| 12345678905 | AE5 |
Once you get the combined tracking number (TN1234567890), you have two primary options for updating your sheet:
Option 1: Apply Tracking to One Row, Use AliExpress Order IDs for Others (Recommended)
This method ensures that the logistics_status is updated correctly for all items, but individual AliExpress order statuses and refund information remain tied to their specific rows.
- Identify the primary item: Pick one of the eBay sales (e.g., the first one, 12345678901) to carry the combined tracking number.
- Update the primary row: Enter TN1234567890 into the 'AliExpress Tracking Number' column for eBay Order ID 12345678901.
- Leave others with AliExpress Order IDs: For eBay Order IDs 12345678902 through 12345678905, leave the 'AliExpress Tracking Number' column blank, but ensure their respective 'AliExpress Order ID' columns (AE2, AE3, AE4, AE5) are populated.
Your sheet would look like this:
| eBay Order ID | AliExpress Order ID | AliExpress Tracking Number | order_status | logistics_status | gmt_refund | end_reason |
|---|---|---|---|---|---|---|
| 12345678901 | AE1 | TN1234567890 | ||||
| 12345678902 | AE2 | |||||
| 12345678903 | AE3 | |||||
| 12345678904 | AE4 | |||||
| 12345678905 | AE5 |
Fetch Order Tracking will now:
- For 12345678901: Use TN1234567890 to fetch
logistics_status. It will also fetchorder_status,gmt_refund, andend_reasonfor AE1. - For 12345678902-12345678905: Use AE2-AE5 to fetch
order_status,gmt_refund, andend_reason. Crucially, Fetch Order Tracking will *also* associate TN1234567890 with these orders internally (because it knows AE2 is part of the combined order for TN1234567890) and update theirlogistics_statusaccordingly.
Always prioritize populating the AliExpress Order ID column. This ensures granular order status and refund detection, even when tracking numbers are shared across combined orders.
If, for example, AE3 is refunded because the item was out of stock, Fetch Order Tracking will update the row for eBay Order ID 12345678903 with gmt_refund and an end_reason like 'SELLER_CANCELLED_ORDER' or 'BUYER_REQUEST_CANCEL'. The other rows (AE1, AE2, AE4, AE5) will remain unaffected in their gmt_refund and end_reason fields, as they were not refunded.
Option 2: Apply Tracking to All Rows (Less Recommended)
You could enter TN1234567890 into the 'AliExpress Tracking Number' column for *all* five rows. While this will correctly update the logistics_status for all of them, it makes refund detection more complex.
| eBay Order ID | AliExpress Order ID | AliExpress Tracking Number | order_status | logistics_status | gmt_refund | end_reason |
|---|---|---|---|---|---|---|
| 12345678901 | AE1 | TN1234567890 | ||||
| 12345678902 | AE2 | TN1234567890 | ||||
| 12345678903 | AE3 | TN1234567890 | ||||
| 12345678904 | AE4 | TN1234567890 | ||||
| 12345678905 | AE5 | TN1234567890 |
If AE3 is refunded, Fetch Order Tracking will update the gmt_refund and end_reason fields *only* for the row associated with AE3. However, if you're relying heavily on tracking number status alone for refund detection, this approach can create ambiguity.
Managing Order Finalization and eBay Updates
Once an order reaches logistics_status: DELIVERED, you'll want to mark the corresponding eBay order as shipped. For combined orders, all five eBay orders associated with TN1234567890 can be marked as shipped simultaneously. However, you should only mark an eBay order as FINISH or process a refund on eBay once the AliExpress order_status for that *specific* AliExpress Order ID (e.g., AE3) confirms a refund (gmt_refund is populated) or a successful completion (order_status: BUYER_ACCEPT_GOODS or FINISH).
Key Fields for Combined Order Management
- AliExpress Order ID (Crucial): Always populate this field for every individual eBay sale. It's the primary key for specific order status and refund detection.
- AliExpress Tracking Number: For combined orders, apply this to one primary row, or all rows if you prefer. Fetch Order Tracking will correctly link logistics status across associated orders.
order_status: Reflects the lifecycle of the *individual* AliExpress order (e.g.,AWAIT_SHIPMENT,AWAIT_BUYER_PAYMENT,FINISH,REFUND_ONLY).logistics_status: Reflects the physical delivery status of the *package* (e.g.,IN_TRANSIT,DELIVERED). This will be identical for all orders in a combined package.gmt_refund: Timestamp when a refund was initiated for the *specific* AliExpress order. This is your primary indicator for eBay refunds.end_reason: Explains *why* the individual AliExpress order was refunded (e.g.,SELLER_CANCELLED_ORDER,BUYER_REQUEST_CANCEL,LOGISTICS_ISSUE).
By meticulously linking each eBay sale to its unique AliExpress Order ID, even when tracking numbers are shared, you maintain the necessary granularity for accurate tracking, timely refund detection, and efficient customer service in your eBay dropshipping operation.
For more streamlined tracking and refund detection, explore Fetch Order Tracking's features at fetchordertracking.com.