> ## Content Index
> Fetch the complete content index at: https://www.doitwithfriday.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Shopify Draft Order Discount Change: Why Some Quotes Fail
- URL: https://www.doitwithfriday.com/news/shopify-draft-order-discount-permission/
- Published: 2026-11-19T09:25:00.000Z
- Updated: 2026-11-20T14:55:28.000Z
- Description: Shopify rejects a draft order discount added by an app acting for a staff member without one permission. The draft isn't saved, and the error is easy to miss.
- Author: Kevin Anderson
- Tags: News, What to Watch

Shopify published the change on November 18, 2026, as a breaking change in its developer changelog, a page Shopify writes for the developers who build apps.

Below: what changed, which apps and automations it hits and which it leaves alone, the permission that fixes it, and who should own that fix at your store.

## What Shopify changed on November 18

Shopify's developer changelog lists the change under Breaking API Change and Action required. It applies to two GraphQL Admin API mutations that apps use to create and edit draft orders.

### Two mutations, one new check

Draft orders are orders built by hand, for example a quote for a wholesale buyer or a phone order; Shopify's Help Center says the Create and edit permission covers sending and sharing an invoice for them. Apps create them with `draftOrderCreate` and change them with `draftOrderUpdate`. The [Shopify changelog post](https://shopify.dev/changelog/posts/draft-order-discount-permission?ref=doitwithfriday.com) says that "in all supported API versions" both mutations now return an `ACCESS_DENIED` error when an app acting as a staff member adds a discount and that staff member lacks the `apply_discounts_to_draft_orders` permission. In that case, Shopify says, the mutations "don't save the draft order and return null for the mutation payload."

Because the change applies in every supported API version, an app cannot avoid it by staying on an older version. The changelog tags the post as Security.

### What counts as adding a draft order discount

The changelog names two triggers. The first is adding a discount code to `discountCodes` that the draft order does not already have. The second is setting `acceptAutomaticDiscounts` to true on a draft that does not already accept automatic discounts. When an app creates a new draft, any discount code or automatic discounts count as an added draft order discount, "because the draft order doesn't exist yet."

### What still works

Shopify says that "keeping or removing a draft order's existing discounts still works." Drafts that already carry a draft order discount are not stripped. The change blocks the moment a new draft order discount is added; discounts already in place stay.

## Which draft order discount requests are blocked

The block needs three conditions at once. A request that acts as a staff member, adds a discount and comes from a staff member without the permission fails; any other request is outside this change.

### Apps that act as a staff member

Shopify's affected list says an app is hit if it calls either mutation as a staff member, expects to add discount codes or turn on automatic discounts, and does not make sure the staff member has the permission. In Friday's reading of Shopify's access token documentation, an app acts as a staff member when it uses an online access token. Shopify's [access token documentation](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens?ref=doitwithfriday.com) says online tokens are for "interactive workflows during a staff member's active session, so requests respect that user's permissions and are attributed to them." For example, that is an app a sales rep opens inside the Shopify admin to build a quote with a draft order discount, apply a wholesale price or send an invoice.

The same page says an online token expires after 24 hours or when the user logs out of the Shopify admin, and that the token response includes an `associated_user` object describing the staff member who authorized it. That object is how a developer can see whose permissions a request carries.

### Where an offline access token fits

The changelog is direct about the exemption: "Requests that don't act as a staff member, such as requests made with an offline access token, aren't affected." Shopify's documentation calls the offline access token the default, used for "webhooks, scheduled jobs, and other background tasks" with no user session behind them. A connection that runs on a schedule or on a webhook with no one logged in matches that description, though only the app's builder can confirm which token it uses.

So connections that use an offline access token keep adding each draft order discount as before. A tool that a staff member opens and works in during their session is the kind of tool to check.

### What the change leaves alone

The changelog covers only `draftOrderCreate` and `draftOrderUpdate`. It says nothing about discount codes that shoppers enter at checkout or about automatic discounts on regular storefront orders. It covers app requests, not staff who build a draft order discount by hand in the admin, where the Help Center's Apply discounts permission for draft orders already applies.

## Why a failed draft order discount can go unnoticed

In Friday's view, the risk sits less in the block than in where it is reported. The error sits outside `userErrors`, the field the changelog says some apps rely on alone to catch a failed draft order.

### An error outside userErrors

Shopify's changelog says that in these cases "the mutation returns a top-level GraphQL error with the code ACCESS\_DENIED and null for the mutation's payload. The error doesn't appear in userErrors." It adds: "Apps that rely only on userErrors for failure handling need to update their error handling." This is the example response Shopify publishes for `draftOrderUpdate`:

```
{
  "errors": [
    {
      "message": "Access denied for draftOrderUpdate field. Required access: `write_draft_orders` access scope. Also: The user must have access to manage draft orders.",
      "locations": [{ "line": 2, "column": 3 }],
      "path": ["draftOrderUpdate"],
      "extensions": {
        "code": "ACCESS_DENIED",
        "documentation": "https://shopify.dev/api/usage/access-scopes",
        "requiredAccess": "`write_draft_orders` access scope. Also: The user must have access to manage draft orders."
      }
    }
  ],
  "data": {
    "draftOrderUpdate": null
  }
}
```

Source: Shopify developer changelog, November 18, 2026\. Shopify says `draftOrderCreate` returns the same error, with its own name in the message and path.

### A message that points to another setting

The message text names the `write_draft_orders` access scope and says the user "must have access to manage draft orders." It does not name the discount permission. In Friday's view, a developer who reads only the message can spend an afternoon checking app scopes and the staff member's general draft order access, both of which may already be in order, while the missing piece is the Apply discounts permission that governs each draft order discount.

### What the store sees

In Friday's view, the owner's symptom is a missing record. Picture a sales rep at a ten-person wholesale supplier who builds a quote in a quoting app, adds the buyer's tier code and clicks send. If the app only checks `userErrors`, it finds none, and the screen may look as though the quote went out. No draft order is saved, so no invoice reaches the buyer, and the first sign can be the buyer asking where it is.

## The fix sits in Shopify staff permissions

For the store, the fix is a setting. The changelog tells developers to ask the merchant for the Apply discounts permission under Draft orders, and Shopify's Help Center explains it.

### The Apply discounts permission under Draft orders

Shopify's [Store permissions page](https://help.shopify.com/en/manual/your-account/users/roles/permissions/store-permissions?ref=doitwithfriday.com) lists the Apply discounts permission in its Draft orders section: "This permission allows users to apply and remove custom line item and order discounts." The page says the Apply discounts permission also requires two other Draft orders permissions, View and Create and edit. Open the staff member's permissions, or the role assigned to them, in the Shopify admin, and check the Draft orders group.

The changelog's own fix reads: "If your app needs to add discounts, ask the merchant to give the staff member the Apply discounts permission under Draft orders." Friday's recommendation: grant it only to the people whose quotes carry discounts.

### Discount codes need a second permission

The same Help Center entry adds: "Staff will also need the Discounts permission to apply discount codes." So a rep whose quotes carry a code such as a wholesale tier code needs both the Apply discounts permission under Draft orders and the separate Discounts permission. Check both before you test.

### Two permissions with the same name

The Orders section of the same page has its own Apply discounts permission, which "allows users to apply discounts to existing or new line items in an order, or to the entire order." It is a separate entry on the page. The permission the changelog names sits under Draft orders.

### Who already has it

Shopify split its single Draft orders permission into seven on June 20, 2023, Apply discounts among them. Its changelog said staff who held the old permission "will automatically have all the new permissions selected by default." Staff and roles set up since then may have been given a narrower set; in Friday's view, a rep added this season is the one to check first.

## Who owns the fix: the store, the agency or the app vendor

A permission tick fixes today's draft order discount block. In Friday's view, whether the next silent failure gets caught depends on who wrote the error handling and who reads platform changelogs.

### Ask which token your tools use

Friday's recommendation: list every app and automation that creates or edits draft orders, then ask its owner one question in writing, "Does this act as a logged-in staff member, or does it use an offline access token?" For a public app, that is the vendor's support team. For a custom app, it is the agency or developer who built it. If nobody can answer, that is a finding in itself, and in Friday's view it tells you who holds knowledge you are paying for without owning.

### Error handling someone else wrote

The changelog asks developers to check the top-level errors array as well as `userErrors`. In Friday's view, this is the shadow cost of a custom app built by an agency: the code that decides whether a failure is shown to your staff was written once, and nobody may be on contract to update it. Ask for three things: the date the change was handled, a test that shows the error reaching the screen, and a copy of the code in a repository you control, so the next fix does not depend on one vendor's calendar.

### Test one quote before Black Friday week

Shopify's changelog does not mention the holiday season. In Friday's view, the timing still matters for stores that run wholesale or phone orders through draft orders, because a missing quote costs more in the last week of November. Sign in as a rep who uses the quoting app, build a draft order with a discount code, and check that the draft order was saved in the admin. Then repeat it as a rep without the permission and confirm the app shows an error.

### When a small workflow beats one more app

In Friday's view, if a quoting app exists only to add a tier code and send an invoice, a small [workflow you own](https://www.doitwithfriday.com/services/workflows/) that uses an offline access token, writes every result to a log and alerts a person on failure can be cheaper to keep than another monthly subscription. Our guide to [AI workflow error handling](https://www.doitwithfriday.com/blog/ai-workflow-error-handling/) covers alerts and retries for that case. The trade-off: Shopify says requests made with an offline access token aren't affected by the staff permission check, so in that workflow the store itself has to decide, and log, who can trigger a discount.

## Check one discounted quote this week

The block is narrow and the store-side fix is a permission setting, provided someone knows to look. A draft order discount that silently never saves is the thing to rule out this week.

Give the Apply discounts permission under Draft orders, and the Discounts permission for codes, to the staff who send discounted quotes, then test one draft order with a discount code. Ask each app owner whether their tool reads the top-level errors array. If you want a second look at the apps and automations that write your draft orders, [send us the list of tools that touch them](https://www.doitwithfriday.com/contact/).

Last checked: November 19, 2026, against Shopify's developer changelog, Shopify's access token documentation, the Shopify Help Center Store permissions page and Shopify's June 2023 changelog on draft order permissions.

Facts come from Shopify's own developer changelog, documentation and Help Center, checked November 19, 2026\. Friday has no relationship with Shopify or any Shopify app vendor. Statements marked as Friday's view or Friday's recommendation are opinion.