Dawn Quick Add: What the Built-In Quick Buy Really Does

Search for “Shopify quick buy” and every result sells you an app. Dawn has it built in, has had for years, and ships with it switched off. This page covers what the setting actually does, where it lives, and what each of its two working modes costs you in bytes — read from Dawn v16.0.0, published 2026-08-10.

How we got these numbers. On September 1, 2026 we read the theme’s source at release v16.0.0: the settings schema and conditional asset tags in sections/main-collection-product-grid.liquid, the rendering branches in snippets/card-product.liquid, and the byte size of every asset file the theme loads for each mode, taken from the repository itself rather than estimated. We also scanned all 46 section files to find every place the setting appears.

It exists, and it is off

The setting is quick_add, a dropdown with 3 choices — none, standard, bulk — and it defaults to none. Nothing appears on your product cards until you change it.

It is also rarer than you would expect. Out of 46 sections in Dawn, exactly 2 carry it:

That is the whole surface. Search results, related products and recently viewed do not offer it, so a shopper who reaches a product through search will not see a quick add button no matter how the setting is configured.

What the two modes actually do

standard puts an Add to cart button on the card. What happens next depends on the product: if it has one variant the item goes straight into the cart, and if it has several the theme opens a <quick-add-modal> and fetches the full product page in the background to show the variant picker inside it. That fetch is a real request for a real page, made the moment the shopper clicks.

bulk replaces the button with a quantity input. It is built for wholesale-style ordering where a buyer takes several of the same item, and for single-variant products it renders the quantity control directly on the card.

What each mode costs

This is the part that decides the choice, and it is not in any documentation. The theme loads different files per mode, and the conditional blocks at the top of the section spell out exactly which:

So turning on standard adds 21,128 bytes to a collection page. Turning on bulk adds 41,935 bytes — 2.0× as much.

The gap is not where you would guess. bulk pulls in quick-order-list.js at 18,255 bytes, which is the quick order list component — a feature that has nothing to do with adding one item from a card, but ships in the same bundle. That single file is larger than everything standard loads put together.

None of this is compressed size and none of it is execution cost; it is what the browser has to fetch and parse before the card behaves. On a collection page already carrying product images, it is a fair trade for standard and a decision worth making deliberately for bulk.

The recommendation, stated plainly

Turn on standard on your collection and featured-collection sections unless you have a reason not to. It is 21,128 bytes for a conversion feature that merchants routinely pay a monthly app fee to replicate, and the app version will not be lighter.

Reach for bulk only if buyers genuinely order multiples of the same item. Otherwise you are paying 20,807 extra bytes on every collection page for a quantity box most shoppers will never touch.

Checking this yourself

The dropdown is defined in the {% schema %} block of sections/main-collection-product-grid.liquid; the conditional stylesheet_tag and script lines are the first 24 lines of the same file. The rendering branches are in snippets/card-product.liquid, which reads quick_add and switches on 'standard' and 'bulk'. File sizes come from the assets/ directory of the repository at v16.0.0.