How to Get Your Shopify Bin Locations onto ShipStation Pick Lists

This is one of the most common questions I see from stores running Shopify and ShipStation together: your bin locations live in Shopify, your pickers work off ShipStation pick lists, and the two never talk. So your team ends up hunting for stock or keeping the "real" locations in a separate spreadsheet. Almost every answer online is a workaround, and some of them will quietly cost you later. Here's why it happens, and the three real ways to fix it — ranked by how well they hold up as you grow.

Why ShipStation won't just show your bin locations

ShipStation does have inventory locations. The catch is that its native inventory features only do something if ShipStation is your source of truth for inventory — meaning you run your stock counts and locations inside ShipStation itself. Almost no Shopify store does that. Your inventory lives in Shopify, and Shopify stays the system of record.

So the bin data is sitting right there in Shopify, but it has no path onto the ShipStation pick list, because ShipStation is only looking at its own location fields — which you're not filling in. That gap is the whole problem. Every fix below is really just a different way to carry the bin from Shopify across to a field ShipStation will print.

Option 1: Put the bin in the SKU (works today, bites you later)

The fastest hack: bake the bin into the SKU, like A12-3-TSHIRT-BLK-M. It shows up on the pick list immediately because the SKU always comes across. Done in an afternoon.

Here's why I steer people away from it. A SKU is supposed to be a stable identifier for a product — reporting, other integrations, your accountant, and your own sanity all assume it doesn't change. But bins change constantly: you reorganize, an item moves shelves, you add a location. Every time that happens you're now editing SKUs, and anything downstream that keyed off the old SKU breaks or double-counts. It feels free on day one and gets expensive the first time you rearrange the warehouse. Fine as a stopgap; not something to build on.

Option 2: Use the barcode or a custom field (fine for a small catalog)

A cleaner middle ground: put the bin in a field that isn't load-bearing — the barcode field is the one people reach for — then tweak your ShipStation packing-slip/pick-list template to print that field. Your SKUs stay clean, and the bin still lands on the sheet.

This works well if you've got a small, stable catalog and you're not really using the barcode field for scanning. It starts to strain when you do want real barcodes, when one product sits in more than one location, or when you've got enough SKUs that hand-maintaining the field becomes its own chore. Good for a few hundred SKUs; shaky past that.

Option 3: Shopify metafield → ShipStation (the one that scales)

The version I actually recommend: keep the bin in a dedicated Shopify metafield — a field built for exactly this kind of custom data — and use it to feed the one field ShipStation actually prints from, the product's Warehouse Location. Shopify stays your source of truth, your SKUs and barcodes stay clean, and bins can move around all day without touching anything they shouldn't.

Here's the catch worth knowing up front: ShipStation doesn't pull Shopify metafields. There's no toggle in the Shopify–ShipStation connection that maps a metafield onto the pick list — it's one of the most-requested features and it still doesn't exist. So the bin has to be written into ShipStation's Warehouse Location field, and kept in sync when it changes. Two ways to do that: export SKU + bin from Shopify and bulk-import it into ShipStation's products (simple, but you re-run it by hand every time bins move), or a small sync that reads the metafield and writes the Warehouse Location automatically — matched on SKU, ideally triggered whenever a product changes in Shopify. The import is fine for a small, stable catalog; the sync is what you want once bins move often or the catalog gets big. Wire the sync up once and the bin just follows the product, with nobody maintaining it.

Which one should you use?

If you've got a handful of SKUs and you're not scanning barcodes, Option 2 is genuinely fine — don't over-engineer it. If you're reorganizing your space regularly, selling one-of-a-kind pieces, or past a few hundred SKUs, go straight to the metafield approach; you'll outgrow the shortcuts fast, and the SKU hack in particular is a trap the moment your bins start moving. And if you take one thing from this: don't put the bin in the SKU just because it's the quickest to see working.

If you'd rather just have it working

The sync between the Shopify metafield and ShipStation's Warehouse Location field is where most people get stuck — it's not hard so much as fiddly, and it's easy to wire up in a way that breaks the next time a bin changes. This is exactly the kind of thing I build and fix for Shopify stores. If you want, send me how your setup looks right now and what your pickers are working off of, and I'll tell you the fastest path to getting bins on your pick lists cleanly — no charge for the read.