1,000,000 is accepted and 1,000,001 is not
Both carts were one line of one product. The first came back with its quantity as sent. The second came back as no cart, with a userErrors entry that names the line's quantity.
What was sent, and what Shopify answered
| Step | Answer | Quantity of the line |
|---|---|---|
| 1. cartCreate with one line of quantity 1,000,000 | Accepted | 1,000,000 |
| 2. cartCreate with one line of quantity 1,000,001 | Refused in the mutation's userErrorsINVALID “The quantity for merchandise with id … must be greater than zero but less than 1000000.” | no cart |
What that shows
- A line of quantity 1,000,000 was accepted, and the cart came back with that quantity.
- A line of quantity 1,000,001 was refused in userErrors, with the code INVALID, naming the line's quantity as the field. No cart was created.
- The message read “The quantity for merchandise with id … must be greater than zero but less than 1000000.” (the id is left out here). It says less than 1,000,000, and 1,000,000 itself was accepted: the limit is the number in the message, inclusive.
Cap a quantity field at what the cart took, not at what the message says
A quantity field capped from the message refuses an order of exactly 1,000,000 units that Shopify takes. The gap is one unit, and it only matters to a wholesale form that sets its own maximum from the error text.
This run says nothing about stock. The store took the quantity for this product; a product whose inventory is tracked may be stopped by its stock first.
How this was verified
Every step on this page was sent to a Shopify Plus development store we keep for this, on API version 2026-10, and Shopify’s answer was recorded as it came back.
The carts were built through the Storefront API with cartCreate, one line each, and the quantity was read from the cart that came back. No order was placed.
A suite sends these steps again. A statement that no longer matches the answer takes this page down until it is corrected, and no record stands for more than 90 days without being taken again. This is what one store answered on one API version: your store’s plan can change the result, so try it on a development store.
Seen something different on your store? Write to privacy@offersuite.io with the request and the answer and we’ll run it.