The 7 saved views every Shopify buyer should run (and how they stay true)

Saved views get dismissed as a collections-lite feature, which gets them exactly backwards. Collections decide what customers see; saved views decide what you see, and the Products-page view system is the closest thing Shopify has to a free reporting layer for buying decisions. The mechanics, verified against Shopify's Help Center as of November 2026: you save any combination of filters, search terms, and columns as a named view, and — this is the part that makes them better than a spreadsheet export — "the products included in saved views are updated automatically." Seven views, about an hour to build once, each answering a specific question you already ask every week.

What saved views are (and what they're not)

A product view is a saved slice of your Products page: filters (vendor, tag, status, category, collection membership, metafield values, and more), a custom search term, and a column layout, saved as a menu item left of the search bar. Shopify ships four defaults — All, Active, Draft, Archived — which you can't edit but can duplicate from. Any new view you create appears in the menu on desktop and in the mobile app.

The details that matter for daily use:

• Views are live. Save a filter for Active products and every product that later goes active joins the view on its own. Nothing goes stale the way a Monday CSV export does by Wednesday.
• Columns are per-view. Hide what you don't need and reorder what you do; each view keeps its own layout.
• Saving and renaming are desktop-only. Shopify states you can only save changes to product views from the admin on desktop. The app can use views, and it's also the one place an alternative sort order survives — more on that trap below.
• Bulk actions run from views. Select across a view, switch views to keep selecting, then run bulk edit or any other action — no export round-trip.

One boundary before the recipes: this is the native Products-page system only. If you want curated, customer-facing groupings — restock pages, seasonal edits, storefront slices — that's the collections workflow, and it's a different discipline with different failure modes (the Shopify collections as an inventory tool guide owns that ground). Shopify also gives the Inventory page its own views; everything below stays on Products, where the catalog work happens.

The seven views

Each row is a build recipe using only filters and sort options that exist natively. Name views for the question they answer — six months from now, "Vendor shelf — RoastCo" beats "View 3."

Three of these deserve a note.

Stock floor is the workhorse, with a known limit. The Products page has no native low-stock filter — the filter list on Shopify's docs runs through vendors, tags, statuses, categories, channels, catalogs, collections, types, metafields, and gift cards, with nothing that says "under X units." Sorting Active products by inventory ascending is the closest native move, and it's honest precisely because it shows everything thin, not just what you remembered to tag. Pair it with a threshold habit: anything above the fold that you'd panic about at zero gets the reorder tag on sight, which is what makes view 2 function. The alert layer — what you can and can't get natively, and the workaround recipes — is covered in the low-stock alerts piece.

Vendor shelf is how small teams actually buy. Suppliers ship together, ship on their own lead times, and often have minimums, so the useful unit of buying is the supplier, not the SKU. With one view per supplier sorted thinnest-first, your next PO drafts itself from the top of the list. If you keep the reorder sheet in a spreadsheet, this view is the input stage and the sheet is the decision stage — the Shopify inventory spreadsheet piece covers the latter.

Supplier metafield is the one that feels like over-engineering until the day it isn't. A metafield holding each product's supplier code turns "which of my 900 SKUs came from that factory?" into a ten-second filter. The setup requirement is a metafield definition with "Use as filter in admin" activated, per Shopify's docs. It earns its keep the first time a supplier announces a price change or a factory goes quiet.

Keeping views true (the two traps)

The auto-updating behavior means views don't drift the way exports do — but two settings can still fool you.

Sort order doesn't save from desktop. Shopify's docs state it plainly: change the sort order in the admin on desktop and the list reverts to the default sort when it refreshes. The workaround is the mobile app, which can save an alternative sort order — so if "Inventory ascending" is the whole point of Stock floor, set and save that sort on mobile, then treat the desktop list as the same view sorted differently. Annoying, documented, survivable.

Hide archived is a per-browser setting, not part of the view. On the All view, the Hide archived toggle saves to your browser, so it applies only to you. If a teammate swears the catalog "looks different," that toggle is usually the difference — and it's one more reason status-based views (Active, Draft) beat eyeballing the All view for real work.

Neither trap breaks the system. Both just explain why the seventh view should never be named "temp."

Build order: don't build all seven today

The failure mode here isn't complexity; it's ambition. Build views 1, 2, and 3 — Stock floor, Reorder tag, Vendor shelf — in one 30-minute sitting, and run them for two Mondays before adding anything else. Those three carry the buying decision, which is the highest-stakes recurring question you have. Draft graveyard and Stale list are quarterly habits, Collection audit is for storefront hygiene, and the supplier metafield is a project for a quiet week.

A view is a decision queue, not a dashboard. The rule that keeps it useful: every view exists to produce an action — a tag applied, a PO drafted, a listing archived — and any view that stops producing actions gets deleted. Shopify lets you delete views; it won't let you un-delete them, so don't hoard.

This is also the honest seam where views end and planning begins: views surface what's thin, but they don't compute velocity or days of cover. We are building InventoryX for that layer — a weekly Monday Buying List that ranks SKUs by days of cover and turns the shortlist into draft POs — and it reads the same catalog the views do; the views just stay useful either way.

Common questions

Do Shopify saved views update automatically? Yes. Shopify's Help Center states that products included in saved views are updated automatically — a view filtered to Active products picks up newly active products on its own. That's the core advantage over a saved CSV export, which is frozen the moment you download it and quietly lies by Wednesday.

Can I create saved views in the Shopify mobile app? No — Shopify states that saving changes to product views is desktop-only. The app can open and use existing views, and it's also the only place an alternative sort order persists. Build the views at a desk; run them from anywhere.

Can my staff see the saved views I create? Shopify's documentation doesn't state whether product views are per-user or shared across staff accounts, so don't build your workflow on an assumption either way. The safe pattern: keep view names and recipes written down (this table works), so any staff member can rebuild a missing view in two minutes.

Is there a limit on how many saved views I can have? Shopify's docs name no maximum, but every view is a decision queue that costs attention, and unnamed clutter defeats the point. Seven well-aimed views beat thirty. The defaults (All, Active, Draft, Archived) can't be deleted, but everything else you can clean up quarterly.

What's the difference between a saved view and a collection? A saved view is admin-side: filters over your catalog for your decisions, invisible to customers. A collection is storefront-side: a curated group customers browse. They can overlap in content but answer different questions — and the collections-as-inventory-tool guide covers the storefront discipline separately.

Next step

Build Stock floor, Reorder tag, and one Vendor shelf view today — 30 minutes, desktop, sort order saved from the mobile app. Then bolt them onto a rhythm with the weekly inventory checklist, which gives each view a day and an owner so the seven views stay a routine instead of a one-week experiment.