Shopify shipping rules by collection: fragile vs everything else

A vase from “Fragile” must not ship at the €6.95 letter rate. A tea towel from “Textiles” should. Native zones know countries and kilos, not collections. Shopify shipping rules by product collection is a *condition* on the visual flow in OO - Shipping Rates & Rules, not a second Shopify zone. Checked 7 November 2026: listing, Conditions, Shipping rates, Getting Started, Activity logs, Shopify Help Shipping rates and Shipping profiles. If the product/collection condition or the Advanced gate for carrier rates moves, re-read those sources before you promise “fragile + $18” on Basic.

Yesterday was cart total as a *pricing base*. Today is *which products* may see the rate.

Native tools: a zone or a profile — not a collection on the same canvas

Shipping rates: flat, weight, or price per zone. Shipping profiles: separate rates for a product group. That splits checkout into profiles. It does not combine “Fragile is in the cart” with a postcode and a threshold on one canvas.

Listing (7 Nov 2026): Free, 0 reviews, launched 28 Oct 2026. Do not invent stars. 40+ conditions, including products. Category: Product-based. Visual flow or AI draft. Combined rates. Hide/rename/reorder. Logs.

Docs/positioning: product conditions include name, SKU, vendor, tags, collections, variants, metafields, price, weight, dimensions. Tags, collections and metafields load through the Admin API at rate time — not from last week’s CSV. Put a product in “Fragile” today, test the next checkout.

Carrier-calculated custom rates: Advanced Shopify or higher, a development store, Plus, or a shop where the carrier is already active. Hide/rename of existing methods works on more plans — that relabels “Standard”, it does not price a collection.

What shops build until the collection sits on the card

A second Shopify zone named Fragile. Copy every country. No mixed cart. No postcode beside it.

A weight table “because vases are heavy”. Weight is a pricing base. A light crystal bowl is still fragile. Collection ≠ kilograms.

A customer tag `fragile-ok`. Rates by customer tag is the *buyer*. Collection is the *line*. Do not swap them.

Delivery customization: hide Standard when the cart “looks fragile”. Rename/hide changes labels, not the carrier sum. Without Advanced/dev/Plus there is no collection rate at checkout.

Collection condition versus pricing base

Sources: listing 7 Nov 2026; Conditions collection; Getting Started plan gates. Mixed cart (vase + towel): test both, read logs. Do not claim “highest wins” unless your log shows it — docs describe matching, not a silent max(). Combined rates if two components should be one line.

An AI draft “fragile collection $18” is a concept. Review before save. The collection must exist in Shopify; the app loads it at rate time.

Worked example: homeware, Fragile collection, letter rate otherwise

Store “Clay House”. Collection `fragile` (manual or automated on tag `fragile`). Everything else: letter $8.

1. Install OO - Shipping Rates & Rules. Free. Carrier rates only with Advanced (or development/Plus). Otherwise you stop at hide/rename.

2. App zone for your country. Attach carrier OO - Shipping Rate & Rules on the Shopify zone/market (attach).

3. Flow: `Start when…` destination country. Branch: product collection = `fragile` → rate card Fragile fixed $18 (handling optional). Other branch: not that collection → Letter $8.

4. No second native zone. Postcode stays an extra condition if islands cost more — by postal code.

5. Test checkout: towel only; vase only; both. Logs 7 days: which zone, which rate, why the letter branch did not fire. Product added to the collection after the test? Run again — load is rate-time.

A smart collection on tag `fragile` cuts maintenance. The condition is still “collection”, not “tag”, until you deliberately add a tag condition.

Custom rates is the canvas. How to set rates is the checklist. This post is one condition on that canvas.

Ship the branch without renaming Standard

Home checklist. Carrier on every zone/market. Collection in Shopify, then the condition. Test a mixed cart. Logs seven days. Review AI drafts. Lower plans: plan banner, do not force a collection carrier sum.

Dimensional weight is another base and needs L/W/H metafields. Do not use it “because vases look big” if your rule is the collection.

Bottom line

For Clay House I would put `fragile` on a collection condition, letter on the other branch, and read the mixed cart in logs before a sale — not hope native profiles split the vase. Shopify shipping rules by product collection is a product condition at rate time, Free, carrier on Advanced/dev/Plus. Native zones do not know collections on the same flow. Listing 7 Nov 2026: Free, 0 reviews. Docs: collections in the product group. If matching or the plan gate moves, this advice is wrong.

Add the branch from the OO - Shipping Rates & Rules listing and check one vase, one towel, and both together.