Every COD seller knows the double loss: a parcel sits at the carrier in Failed Delivery, and meanwhile a brand-new order for the very same product is about to be packed and shipped from scratch. The Relaunch Center spots that overlap for you: it lists new orders that match a failed-delivery parcel β same products, same destination β so that instead of sending a second parcel, you redirect the failed one to the new customer. One shipment saved, one stuck parcel recovered. Open it at https://v2.egrow.com/centers/relaunch. For the full center map, see The Order Centers, Explained.
Before you begin
- Your shipping runs through a connected carrier that supports the relaunch operation (eGrow tells you if a carrier doesn't).
- You have parcels sitting in the Failed Delivery stage β those are the parcels eligible to be redirected.
- The new order is confirmed β you're about to reroute a physical parcel to this customer, so confirm they really want it first, for example with a quick VoIP call.
How the matching works
The stage badges at the top of the page show which orders the center watches: the processing stages β confirmed orders being prepared for shipment (the same stages the Processing Center works). For each of them, eGrow looks for a parcel already in Failed Delivery that carries the same products and goes to the same destination. When it finds one, the order appears in the Relaunch queue with its matched parcel.
How strict "same destination" is depends on one setting, Match Same City Only:
- On (default) β an order is matched only if the failed parcel is going to the same city.
- Off β any failed parcel in the same country carrying the same products can match.
The info banner at the top of the page rewords itself to reflect whichever mode is active.
Note: the Relaunch Center is one of two exits from Failed Delivery. The other is the Follow-up Center, where an agent calls the original customer to rescue the delivery. Try the follow-up first; relaunch when the original sale is truly dead but the parcel β and the demand β are still alive.
Reading the worklist
The center is a simple table with a search box, a refresh button at the top right, and pagination at the bottom. Each row shows:
- Order β the new order's number; click it to open the full order details in a side panel.
- Customer β the new customer's name (click to open their profile) and phone number.
- Destination β the city and country the new order ships to.
- Failed Parcel β the matched failed-delivery order, as an amber link you can open to inspect the parcel before deciding.
- Items β the total quantity of products on the new order.
- Relaunch β the amber action button that starts the relaunch flow for this row.
When nothing matches, the table shows "No orders to relaunch β there are no orders matching a failed-delivery parcel right now." That's normal: rows appear only when a real overlap exists.
Relaunching an order, step by step
Step 1 β Pick the failed parcel
Clicking Relaunch opens a picker listing the failed-delivery parcels that share at least one product with the new order. The parcel eGrow already matched is pinned at the top, so usually you just confirm it β but you can search and page through all eligible parcels and pick a different one. Each entry shows the order number, customer, city, and tracking number.
Step 2 β Confirm with the carrier
Next, eGrow opens the relaunch form for the carrier of the old parcel. The fields are the carrier's own (each integration defines its relaunch module), pre-filled from the old and new orders β typically the parcel code and the new customer's name, phone, and address. Review them, then press Relaunch. A Back button returns you to the parcel picker if you chose the wrong one.
Important: if the failed-delivery order has no carrier connection, or its carrier doesn't offer a relaunch operation, eGrow says so and the flow stops β nothing is sent anywhere.
What happens when you press Relaunch
The relaunch runs in two phases:
- Carrier phase β eGrow calls your carrier's relaunch API, which redirects the physical parcel to the new customer's details.
- eGrow phase β the relaunch is recorded on eGrow: the parcel and its tracking are attached to the new order, and both orders' histories reflect what happened.
If the second phase fails after the carrier already accepted the redirect, eGrow keeps the window open, shows exactly which side reported the error ("error from [carrier]" vs. "error from egrow"), and offers a Retry that re-runs only the recording step β the parcel is never redirected twice.
On success you get a "parcel relaunched successfully" confirmation, the row leaves the queue, and the new order continues its normal path to delivery β no new parcel was ever printed or shipped.
Configuring the matching
The only setting is Match Same City Only, in the Relaunch settings. Keep it on for dense areas where redirecting across cities isn't worth it; switch it off in markets where your carrier moves parcels between cities cheaply and you'd rather recover every possible parcel.
Tip: relaunch works best for your best-sellers β the more often a product is ordered, the more likely a new order for it appears while a failed parcel of it is still recoverable. Check this center as part of your daily processing routine, before packing: every match you catch is a shipping fee you don't pay twice.
Where it fits
Relaunch sits between two flows: it pulls parcels out of Failed Delivery (where the Follow-up Center has been chasing the original customer) and injects them into new orders coming out of Confirmation and Processing. See The Order Centers, Explained for how all the pieces connect.