Shopify POs & Transfers: Why Your Reference Numbers Aren't Copying Over (and What to Do)

Hey everyone, your friendly Shopify expert here, diving into a really important thread that popped up in the community recently. It's about a common frustration many of you dealing with inventory might have experienced: the elusive Purchase Order (PO) reference number not making its way to auto-created Inventory Transfers. It sounds technical, but trust me, the impact is very real for your day-to-day operations.

The Head-Scratcher: Missing PO References in Transfers

Picture this: You’re diligently creating Purchase Orders in Shopify, carefully adding a crucial reference number – maybe it’s your supplier's invoice number, a unique identifier for a specific shipment, or something vital for your internal tracking. You mark the PO as 'Ordered,' and Shopify, being the helpful platform it usually is, automatically creates an Inventory Transfer for you. Great, right?

Well, not quite. As our community member @gav_2 pointed out, that all-important Reference field from your Purchase Order is left completely blank on the linked Inventory Transfer. It’s like the system forgets a critical piece of information right at the last hurdle.

The impact? It's a significant gap in the native purchasing workflow. That reference number is critical for matching transfers to supplier documentation, ensuring accuracy, and maintaining reliable traceability. Having to manually re-enter it on every single transfer isn't just annoying; it introduces unnecessary friction and, more importantly, a risk of errors.

Why Isn't Shopify Flow Solving This? The API Roadblocks

Like many of you, @gav_2 and others immediately thought of Shopify Flow – that powerful automation tool we all love. Surely Flow could just copy the reference over, right? Unfortunately, as Hardeep and @ajaycodewiz confirmed, it's not that simple. The community discussion revealed some key limitations:

• No 'Inventory Transfer Created' Trigger: This is a big one. Shopify Flow simply doesn't have a trigger that fires specifically when an inventory transfer is auto-created from a PO.
• API Linkage Issues: By the time other transfer triggers (like 'Ready to Ship' or 'Completed') *do* fire, the Admin API doesn't expose a direct link back to the originating Purchase Order. It's like the system creates the transfer, but then severs the easy programmatic connection to its parent PO.
• Timing is Everything: Triggering on a PO status change (like 'Ordered') is too early. The Inventory Transfer doesn't exist yet at that exact moment, so there's nothing for Flow to interact with.
• PO API Limitations: @ajaycodewiz highlighted a crucial point: Purchase Orders aren't even fully exposed in the Admin GraphQL API (as of 2026-07, which is an interesting future-dated note, but clearly indicates a current limitation). This means a 'Send HTTP request' step in Flow can't reliably read the PO's reference field anyway.

To really drive the point home, @ajaycodewiz reproduced the issue on a test store and shared these visuals:

It's clear from these screenshots that the Reference, Note, and Tags fields are indeed blank on the auto-created transfer, with the only link being the PO number itself.

So, What Can You Do About It?

Based on the community discussion, here are the paths you can take right now:

1. The Manual Entry Method (The Quick Fix)

This is the simplest, most immediate solution, though definitely not ideal for efficiency or preventing errors:

1. When you mark a Purchase Order as 'Ordered' and the Inventory Transfer is automatically created, note down the PO's reference number.
2. Navigate to the newly created Inventory Transfer.
3. Manually type or paste the reference number into the Transfer's 'Reference' field.

It gets the job done, but it's a Band-Aid, not a cure.

2. Develop a Custom App (The Heavy-Duty Solution)

If manual entry is crippling your operations, especially for high-volume stores, a custom app might be your best bet. This would involve:

1. Bypassing Auto-Creation: Your custom app would handle the creation of both the Purchase Order and the Inventory Transfer.
2. Programmatic Control: This would give you the ability to explicitly copy the PO's reference field value directly into the Transfer's reference field during creation.
3. Developer Resources: This solution requires development expertise, either in-house or by hiring a Shopify development partner. It's a significant investment but offers a tailored, automated workflow.

3. Contact Shopify (The Long-Term Solution for Everyone)

This is where the collective voice of the merchant community becomes powerful. As Hardeep and @ajaycodewiz suggested, this is a clear feature gap in Shopify's native inventory management. The expected behavior, as @gav_2 outlined, is for that reference field to carry over automatically.

Here's how you can help:

1. Submit Feedback: Reach out to Shopify Support and formally submit this as a feature request. The more merchants who report this issue and request the feature, the higher its priority becomes.
2. Reference the Community Thread: Feel free to link to the original community discussion (shopify.com/t/po-reference-field-not-propagated-to-auto-created-inventory-transfer/654092) in your feedback, as it clearly outlines the problem and the attempted solutions.

Wrapping It Up

It's frustrating when a seemingly simple piece of data doesn't flow seamlessly between linked parts of your system. The community has made it clear that the current limitations in Shopify Flow and the Admin API prevent an automated solution for this particular PO reference issue. For now, it's either manual data entry, a custom development project, or, ideally, persistent feedback to Shopify to improve the core platform functionality. This kind of feedback helps shape the platform, ensuring that Shopify remains the best choice for growing businesses. Let's keep those conversations going in the community!