This is a really useful improvement for merchants and app developers working with inventory, logistics, warehouses, suppliers, ERP, or WMS systems.
Shopify now allows metafields to be added directly to Inventory Transfers in both Shopify admin and the Admin GraphQL API.
This means extra transfer-related data can now be stored directly on the transfer instead of using external notes, spreadsheets, or separate app databases.
Some useful examples:
- Lot numbers
- Serial numbers
- RFID references
- Bill of lading numbers
- Container references
- Freight account numbers
- Customs broker notes
- ERP/WMS reference IDs
- Supplier references
- Internal approval notes
This is especially helpful for merchants who need better receiving workflows, supplier tracking, inbound shipment details, or external system syncing.
Another nice part is that when a transfer is duplicated, the metafield values are copied as well. Also, if the metafield is enabled for analytics, it can be used as a filter or dimension in Shopify Analytics.
For anyone building inventory, warehouse, supplier, Stocky replacement, or ERP integration apps, this update makes transfers much more flexible and easier to extend.
What do you think about this update? How would you use transfer metafields in your inventory or logistics workflow?
Thanks for flagging this, this is a solid update for anyone doing multi-location fulfillment or working with 3PLs.
The lot/serial number and BOL use cases are the ones I’d actually lean on day to day. Being able to attach that at the transfer level instead of bolting it onto a tag or a separate spreadsheet closes a real gap, especially for stores that reconcile against an ERP or WMS. The auto-copy on duplicate transfers is a nice detail too, that’s exactly the kind of manual re-entry that causes mismatched serial numbers down the line.
Worth calling out: Shopify Analytics will let you filter and pivot on these new metafields natively, which covers a lot of ad hoc “how many transfers moved through location X with reference Y” type questions. For teams that need to blend that with broader inventory reporting (stock levels across locations, days of inventory remaining, dead stock, that kind of thing) on a recurring dashboard rather than a one-off query, that’s where a tool like Mipler comes in. It’s not pulling transfer metafields specifically, but it’s worth knowing about if you’re already building out inventory dashboards and want more flexibility than the native reports give you: Mipler ‑ Advanced Reports - Multi-store analytics, custom reports & scheduled exports | Shopify App Store
Are you syncing this with an external WMS already, or is this the first time you’ll have a structured place to put those reference IDs?
Hey @Subhan_Tariq .
This is genuinely useful, especially the analytics filter or dimension part. Being able to slice transfer performance by carrier, container, or supplier without pulling data into a separate BI tool closes a real gap.
Curious whether you have tested how it plays with bulk transfer duplication at scale, like recurring PO templates, since that is where a lot of ERP sync apps hit friction with custom fields today.
Appreciate you breaking this down, it’s a solid summary of what’s changing.
We build Channel Bay, an inventory and PO management app positioned as a Stocky replacement, so this is relevant to us. That said, we don’t see a ton of immediate use for it yet. Most of what you listed (lot numbers, customs notes, freight references) feels like it’ll matter more for reporting and analytics than for actual inventory reconciliation. Being able to filter by that data in Shopify Analytics is a nice add, but it doesn’t change how a transfer actually gets reconciled against what’s received.
Right now our focus with merchants is almost entirely on getting the core numbers right (on-hand counts matching reality, transfers and POs reconciling cleanly) before layering on extra metadata. Once that foundation is solid this becomes a lot more interesting, especially for merchants with complex supply chains who need that extra traceability. For now though, it feels more like a reporting problem than an inventory accuracy one.
This feels like a useful step because it gives operational teams a structured place to keep transfer context instead of scattering it across notes and spreadsheets.
What will be interesting is how developers use these fields to improve the end-to-end workflow. Metadata is valuable, but the bigger operational challenge is still making transfers, receiving, reconciliation, and inventory updates work together seamlessly. It’ll be interesting to see how the ecosystem builds on top of this.