Shopify Automation: Fixing Vendor Returns Going to the Wrong Address

One of the stores we work with runs on Shopify and sells products from several different vendors through the Collective app. Customers browse and check out on the store's own website, and from their side it all feels like one shop. That part was working well.

Returns were another story.

What was going wrong

Whenever a customer sent back a vendor's product, the return label was generated with the store owner's default return address. In this case, that address was the owner's home. So items that belonged to vendors kept showing up at their front door.

The strange part was that the vendor addresses were already saved in ParcelWILL. The information was there. It just wasn't being used when the label was created.

The only fix at the time was to catch each return as it came in and change the label by hand. That works when someone is watching and returns are slow. It falls apart on a Saturday night, or on a day when nobody is checking. One missed return meant a parcel going to the wrong place, and then another shipment to get it to the vendor where it belonged.

On top of that, the owner was spending time on something that should never have needed their attention in the first place.

What we tried first

Our first step was to reach out to ParcelWILL support. We explained the setup and asked whether the return address could change automatically depending on the vendor or the product.

We didn't get a solution that fit what the store needed. Changing labels manually was still technically an option, but it wasn't something the owner could keep doing as the number of vendor products grew.

Building a workaround

Since the app wasn't going to make that decision on its own, we built a workflow that makes it for them.

The logic is straightforward. When a customer submits a return, the workflow checks which product is being returned and which vendor it belongs to. Based on that, it applies the matching vendor rule, so the customer receives return instructions and a label pointing to the right vendor address. Nobody has to step in.

Most of the effort went into testing. We ran returns for different vendor products and checked that each one came out with the correct address before letting it run on its own.

Where things ended up

Before, a vendor product return went to the owner's default address, and someone had to fix the label manually.

Now, a vendor product return is matched to its vendor automatically and sent straight to the right address.

The owner no longer receives parcels meant for someone else, there's no need to keep an eye on returns over the weekend, and there's one less repetitive job in their week. It also means the process won't break as more vendors and products get added.

A few things we took away from this

It wasn't a complicated problem, but it was the kind that quietly costs time and money every week. A few things stood out:

When an app already has the right data but isn't using it, the gap is usually in the decision step, not the data itself. That's often where a small automation can do the job.

Manual fixes can hide how big a problem really is. Each label change only takes a minute, so it's easy to overlook until one gets missed.

It's worth checking what the existing tools can and can't do before building anything. In this case, knowing exactly where ParcelWILL stopped made it much clearer what the workflow needed to handle.

If this sounds familiar

We've set up similar rule-based return flows in ParcelWILL for other stores, using product tags, order tags, and return reasons to decide where things go. If your returns are ending up in the wrong place, or you're still fixing labels by hand, feel free to get in touch. We're happy to look at how your setup works and share what we'd try.