October 11, 2026 · Muhammad Rehan · More by Muhammad Rehan
Shopify Plus Draft Order Deposits Are Now a GraphQL Field
API 2026-07 turns B2B draft order deposits from an admin-only setting into a GraphQL field apps can set and read. What ERP and OMS integrations must track now.
From admin checkbox to GraphQL field
As of API version 2026-07, Shopify exposes draft order deposits as a first-class field: DraftOrderInput.deposit, backed by DepositInput.percentage, which must be between 1 and 99 inclusive. Before this release, a deposit on a B2B order was something a merchant configured by hand in the admin UI — per company location, a capability that's existed since at least 2024 — not something an app could set or read programmatically. The feature remains scoped to Shopify Plus stores; it isn't a general B2B or all-plans capability.
Two different places a deposit can be set
It's worth keeping two fields straight. BuyerExperienceConfiguration.deposit on a CompanyLocation is the checkout-time default — the deposit requirement that applies automatically to orders placed by that B2B buyer. DraftOrderInput.deposit operates at the level of one individual draft order, set or overridden when an app creates or updates it. Both use the same DepositInput.percentage shape, but one is a standing default and the other is a per-order instruction.
What to read instead of what to infer
The practical change is on the read side. The Customer Account API now exposes read-only deposit information directly on draft orders — specifically the amount due now and the amount due later. That's the field a buyer-facing portal, invoicing tool, or ERP sync job should read to reconcile a partial payment, rather than inferring a split from the order total and whatever a webhook happened to capture.
Why this matters for ERP and OMS sync
Any integration that currently treats "draft order accepted" as "order paid in full" needs to stop doing that once deposits are in play. A draft order with a deposit produces two amounts and two due points, not one: the amount collected at checkout, and a remaining balance whose due date is governed by the payment terms template already assigned to that company location. A sync job that only checks total order value against a single captured payment will either flag a false shortfall or silently under-invoice the remaining balance — branch on deposit presence explicitly instead of assuming a one-to-one relationship between a draft order and its payment.