One Per Person, Four Per Cart: The GTA 6 Box Limit

Rockstar's $399.99 Grand Theft Auto VI collector's box carries three different answers to one simple question: how many can a person buy. The customer-facing FAQ says one. The same page's own machine-readable product record says four. The fulfilment system that will actually process the order says one, and records that one as the only unit available to a given user. This desk read all three surfaces first hand within a few minutes of each other, printed the raw fields below, and then checked the separate claim that the box is limited in supply. That claim has its own contradiction, and it involves the largest number a signed 32-bit integer can hold. The FAQ says one CONFIRMED. The product page at store.rockstargames.com/merchandise/gtavi-goodtime-state-vice-city-collection answered HTTP 200 at 1,024,232 bytes when this desk's editor read it at 2026-09-24T20:07:53Z. One of its collapsed FAQ answers reads, verbatim: Limited to 1 purchase per person. Purchase requires log-in to the Rockstar Store. That is unambiguous and it is the answer a shopper will see if they open the FAQ. The same page's product record says four CONFIRMED. Embedded in that same 1,024,232 byte response, in the page's own structured product data, is the field "maxQuantity":4. It sits alongside "itemSkuId":"360657-US", "xsollaProjectId":"100851", "originalPrice":399.99, "isPhysical":true, "productType":"collectible", "visible":true, "purchasable":true and "purchaseState":1. maxQuantity is the field a storefront front end normally reads to cap the quantity selector. On this record it is set to four, which means the widget is configured to let a shopper ask for four of a product the FAQ says is limited to one. There is a related string on the same page that is worth handling carefully, because it looks like corroboration and is not. The store's English string table contains "purchase-limit-exceeded":"Purchase limit exceeded. This item is limited to one per person.". That is a generic store string, available to any product that trips a limit. It is not bound to this SKU. Only maxQuantity is item specific, and this desk says so plainly rather than counting the generic string as a second vote for one. The fulfilment layer says one, and it is the layer that counts CONFIRMED. The product record names its own fulfilment vendor and project: "xsollaProjectId":"100851". Querying that project's public catalogue for this SKU is a single unauthenticated GET. At store.xsolla.com/api/v2/project/100851/items/physical_good/sku/360657-US, the editor received HTTP 200, content-type: application/json, 521 bytes, at 2026-09-24T20:07:40Z. The record, field by field: FieldValue item_id1650109 sku360657-US nameGrand Theft Auto VI: The Goodtime State - Vice City Collection can_be_boughttrue limits.per_user{"total": 1, "available": 1, "recurrent_schedule": null} stock_count_remaining0 is_pre_ordertrue release_date2026-11-19T08:00:00+03:00 weight.ounces384.0000000 pricenull So the three surfaces line up like this. The FAQ tells the shopper one. The checkout widget is configured for up to four. The fulfilment record enforces one and reports one as available. A shopper can therefore put four in a basket and expect to be told no, and the only surface that agrees with the FAQ is the one furthest from the customer. The weight, and the limits on the rest of that record CONFIRMED. The recorded shipping weight is 384 ounces. Converting it is this desk's own arithmetic: that is 24.0 pounds, or 10.886 kilograms. For a box measuring 19 by 13.5 by 12.5 inches, that is a substantial parcel, and it is consistent with a glass shot glass, a metal tin, a metal spoon and a ceramic-weight figure travelling together. Three limits attach to the rest of that JSON, and all three matter. First, "stock_count_remaining": 0 is not a sold-out signal here. It sits on the same record as "can_be_bought": true, on a pre-order item, where a stock counter is very often simply unmanaged. This desk does not headline it, and nobody should read it as the box having sold out. Second, the +03:00 offset on release_date is the API's own timezone, not Rockstar's. Converting it is this desk's own arithmetic: 08:00 at +03:00 is 05:00Z, which is exactly the same instant as the website's own releaseDate epoch field. Nobody may read an 08:00 launch hour off that string. Third, price is null on every record this desk queried, and the price on the web page is hardcoded to 399.99 USD on every locale. No GBP or EUR figure exists anywhere in the record, so no conversion may be presented as Rockstar's. Limited supply, against a number that means no limit CONFIRMED. Rockstar describes this box as limited in several places. The newswire headline is "Pre-Order The Goodtime State – Vice City Collection Now While Supplies Last". The promo card on rockstargames.com/VI calls it "a premium, limited-edition collectible set". And the store FAQ answers the supply question directly: Yes, this item is currently only available in limited quantities. The same page's product record, in the same response, sets "stockAvailable":2147483647 and "limitedAvailabilityEndDate":0. Identifying that number is this desk's own arithmetic: 2,147,483,647 is two to the power of thirty-one, minus one, the maximum value of a signed 32-bit integer. In practice it is the conventional sentinel a system writes into a stock field when no stock limit has been set. Rockstar does not say what the number means, and this desk does not put words in its mouth. Two honest caveats belong with that. A sentinel value is not proof that unlimited units will ship, and stockAvailable may well be a field the front end ignores in favour of a separate inventory service at checkout. What can be said is narrower and it is all this article asserts: the machine-readable stock field on the page that calls the product limited carries the value systems use to mean no cap. This desk has run the same discipline on a sell-out claim before, in the album vinyl piece where the press said sold out and the feed said in stock. Here the direction is reversed, and the method is the same. The merchandise list this desk could not reproduce Hours before Rockstar's announcement, a list of dozens of upcoming Grand Theft Auto VI merchandise items circulated, attributed to a modder pulling storefront API links. This desk tried to reproduce it and failed, and that failure is printed here rather than quietly dropped. A paginated sweep of the same Xsolla project returned 2,528 physical goods entries, every page at HTTP 200. Searching all 2,528 for Macca, Manatee, Narcos, Leonida, Chunkee, Flexfit, Baby Tee, Tonal, Keyline, Shards, Parody, Lobster, Money Clip, Hologram and Palms returned zero hits. Twelve guessed product slugs on the Rockstar Store data route all returned HTTP 404 at 17 bytes each. The only Zippo, Burger Shot and tote entries in the catalogue belong to older Grand Theft Auto V, Grand Theft Auto IV and Red Dead Redemption 2 products. Either those items sit in a different project, or behind an authenticated catalogue, or they were pulled after the leak. This desk cannot tell which, and asserts none of the three. What it can say is that exactly one collector's box product is live, and the catalogue holds only three SKUs for it: 360657-US, 360660-DE (item 1652435) and 360660-UK (item 1652436), whose records are otherwise byte-identical to the US one. What a shopper should actually do Treat the FAQ as the binding answer, because the fulfilment record agrees with it. One box per account, log-in required, no guest checkout, no free shipping. Do not treat the zero stock counter as a countdown, and do not treat the sentinel stock value as a promise that supply is endless. Those are two different failures of reading, and both are easy to make from the same page. With 56 days to launch by this desk's own arithmetic, the product record has been live for a matter of hours. Fields like these are edited. Everything above is what the three surfaces said on 24 September 2026, at the timestamps printed beside each one.