How is ledgerDocumentUri field actually used?

When using inventoryAdjustQuantities mutation to adjust inventory quantities other than available, the ledgerDocumentUri field is required. But how is this field actually used?

Unlike referenceDocumentUri, it doesn’t appear in the inventory adjustment history UI. Also, there is no corresponding analytics dimension in inventory_adjustment_history dataset (whereas reference_document_uri exists).

Am I missing another part of the admin UI where this field is displayed? What is the actual effect of this field?

Hey @xhdtlsid2, ledgerDocumentUri is an API-level audit trail. It lives on each individual InventoryChange and lets your app trace a specific state change back to a transaction in your external system. It’s required for non-available quantities (reserved, committed, damaged, etc.) because those changes typically map to specific operations in external systems that need to be traceable.

You can see it in the Inventory Adjustment changes report in Shopify Analytics.

At the moment its just for audit trail, but i’m hoping Shopify change it to allow it to deep link into apps, like it can for orders and transfers :folded_hands: