Shopify’s 2026-07 APIs now expose draft order deposit fields in the GraphQL Admin API and Customer Account API. Apps can set a deposit when creating or updating a draft order, while customer account surfaces can show the amount due now and the amount due later. Shopify says the feature is available to Shopify Plus stores.
For merchants that sell made-to-order products, wholesale orders, event bookings, custom goods, or high-value items, deposits can make draft orders more flexible. The risk is that payment, fulfilment, customer service, and accounting workflows may all assume a draft order is paid in one step. Before changing a live flow, those assumptions need checking.
What changed in the API
The new fields let an app include deposit information when it creates or updates a draft order through the Admin GraphQL API. Shopify’s Customer Account API then exposes read-only deposit information, including the split between the amount due at checkout and the amount due later.
This opens the door to cleaner partial-payment flows. A merchant could take an initial payment before production starts, then collect the balance later under agreed terms. For customers, the account view can show the payment split instead of leaving support teams to explain it manually.
Kahunam has previously covered Shopify customer account improvements and extension testing. Draft order deposits should be treated with the same discipline: test the customer-facing account experience as well as the admin workflow.
Where deposits can help
Deposits are most useful when the merchant needs commitment before the full order can be fulfilled. Common examples include custom furniture, trade orders, pre-production items, bespoke apparel, event services, and products with long lead times.
The operational benefit goes beyond cash flow. A deposit can reduce speculative orders, clarify when production should begin, and give customers a clearer payment schedule. But the workflow has to be explicit. Staff should be able to answer what has been paid, what remains due, when the balance is collected, and what happens if the order changes.
Checks before implementation
Before a Shopify Plus merchant enables deposit-based draft order flows, review these areas:
- Payment terms: confirm when the balance is due and how the customer is notified.
- Order editing: test what happens if quantities, discounts, shipping, or tax change after the deposit is paid.
- Customer account display: confirm the amount due now and due later are clear.
- Staff workflow: document how support and fulfilment teams identify partially paid orders.
- Accounting exports: check how deposits and balances appear in finance tools.
- Refunds and cancellations: define how partial payments are reversed.
The order-editing test is especially important. A deposit flow that works for a simple order can fail when a customer changes the order after paying the first amount. Test the awkward cases before relying on the flow.
Questions for app and integration teams
If an app creates draft orders, ask whether it supports the 2026-07 API version and the new deposit input. If an app reads customer account data, ask whether it can show deposit details clearly. If a finance or ERP integration receives order data, ask whether it distinguishes deposits from final settlement.
Do not assume every integration understands the new fields from day one. API availability means the platform supports the data. It does not mean every app in the stack has already adapted its workflow, labels, reports, and edge-case handling.
Practical takeaway
Draft order deposits can make Shopify Plus payment flows more flexible, especially for custom and high-value orders. Treat the change as a full workflow update, not a single API switch. Test the admin flow, customer account display, finance export, and support script before using deposits on live customer orders.
Primary source: Shopify developer changelog, Draft order deposit fields are now available in the GraphQL Admin API and Customer Account API.
Author
