{"id":1215,"date":"2026-06-30T21:02:24","date_gmt":"2026-06-30T18:02:24","guid":{"rendered":"https:\/\/spelldot.com\/?p=893"},"modified":"2026-09-05T09:05:02","modified_gmt":"2026-09-05T06:05:02","slug":"woocommerce-order-views","status":"publish","type":"post","link":"https:\/\/presta.site\/blog\/en\/woocommerce-order-views\/","title":{"rendered":"How to set up WooCommerce order views for warehouse, support, and accounting"},"content":{"rendered":"\n

How do you set up WooCommerce order views<\/strong> so warehouse, support, and accounting stop sharing one screen? You save a view per job on the orders list you already have.<\/p>\n\n\n\n\n\n

WooCommerce lets each login hide columns under Screen Options. That is a personal preference, not a queue. And where the whole team shares one admin login – plenty of shops still do – one person\u2019s hidden column is hidden for everyone. If the picker, the person on the phone, and the bookkeeper all click WooCommerce \u2192 Orders and get the same wall of rows, nobody has a job screen. They have a shared spreadsheet that happens to live in admin.<\/p>\n\n\n\n

Why one orders list cannot serve three jobs<\/h2>\n\n\n\n

Warehouse needs orders that are ready to pack: SKUs and quantities on the row, ship-to grouped so they can batch a region. Refunds and failed payments are noise. A picker who opens 40 orders before lunch just to read what is in each box is not slow – the list is.<\/p>\n\n\n\n

Support needs a name, a phone, what they bought, and the last note – while the customer is still on the line. \u201cLet me pull that up\u201d followed by scrolling silence is what happens when those fields live only inside the order. The caller can hear you hunting.<\/p>\n\n\n\n

Accounting needs totals, coupons, and an invoice number for a date range. Product thumbnails do not help at month-end. If the list cannot show the invoice column, they export 900 rows and match them in a sheet to find the 12 refunds.<\/p>\n\n\n\n

Same table. Three different questions. One set of columns cannot answer all three, and asking people to \u201cjust filter it\u201d every time they sit down is how the filters never stick.<\/p>\n\n\n\n

What WooCommerce order views actually are<\/h2>\n\n\n\n

A view is the orders table with the decisions already made: which columns show, which filters are on, which values are filled, how it sorts. You name that shape once and come back to it in one click. Nothing about the orders changes – only what the list puts in front of you. Loading a view is per user, so warehouse can sit on Fulfillment while support loads this week\u2019s contacts. Nobody is fighting over one layout.<\/p>\n\n\n\n

Core WooCommerce already documents the orders table: Screen Options for columns, status links, date and customer filters, column sorting. That is the orders overview<\/a>. Useful – and still one person\u2019s screen. It does not store \u201cwarehouse vs support vs accounting\u201d as three places you can return to. For the click path to save and share a workspace, use the saved views for WooCommerce orders<\/a> guide – that post is the mechanism. This one is which jobs get a screen.<\/p>\n\n\n\n

Warehouse: a fulfillment view<\/h2>\n\n\n\n

Who:<\/strong> pickers, the packing bench, whoever prints labels.<\/p>\n\n\n\n

Filter:<\/strong> status Processing. If you use a custom \u201cready to ship\u201d status, use that instead – the point is \u201callowed to leave the building,\u201d not every paid order including holds.<\/p>\n\n\n\n

Columns:<\/strong> order number, products (a preview you can hover – thumbnails, SKUs, quantities), tracking number, ship-to country, ship-to state or region.<\/p>\n\n\n\n

Sort by ship-to region when you batch carriers or packing slips. Hide phone, email, coupons, customer role – those belong to other people. If a picker still has to open the order to see the SKU, the view is not done.<\/p>\n\n\n\n

\"WooCommerce<\/figure>\n\n\n\n

Support: contact details on the row<\/h2>\n\n\n\n

Who:<\/strong> whoever answers \u201cwhere is it\u201d and \u201cI was charged twice.\u201d<\/p>\n\n\n\n

Filter:<\/strong> the last 7 days covers most shops. Add status Pending payment and Processing if those are the tickets you actually get. Do not dump Completed-from-2019 into this list.<\/p>\n\n\n\n

Columns:<\/strong> order number, date, recipient, phone, email, products as text, status, order notes.<\/p>\n\n\n\n

The notes column matters more than another status badge: a count and a hover beat opening the order while someone waits. Hide tracking and ship-to state unless support also runs the warehouse – two jobs on one view is how you end up back at the shared wall.<\/p>\n\n\n\n

\"WooCommerce<\/figure>\n\n\n\n

Accounting: totals, coupons, invoice numbers<\/h2>\n\n\n\n

Who:<\/strong> the bookkeeper, whoever reconciles the month.<\/p>\n\n\n\n

Filter:<\/strong> this month, or a date range that matches the books. Status is optional; refunds belong in the range if the books include them.<\/p>\n\n\n\n

Columns:<\/strong> order number, date, total, coupon, invoice number, customer type (guest vs account), status. No product gallery. No phone.<\/p>\n\n\n\n

WooCommerce does not invent invoice numbers by itself. If you run a PDF invoices plugin, put that number on the row so a search in the books lands on the order. The coupon column is how you answer \u201cwhy is this month down\u201d without exporting the world: when revenue drops 8% and three codes ate the margin, you want that visible on the list, not in a pivot someone builds once a quarter.<\/p>\n\n\n\n

\"WooCommerce<\/figure>\n\n\n\n

How to set up WooCommerce order views<\/h2>\n\n\n\n

Four moves, once per job:<\/p>\n\n\n\n

    \n
  1. On WooCommerce \u2192 Orders, turn on the columns that job needs in Screen Options. Turn the rest off.<\/li>\n
  2. Set the filters for that job and wait until the table looks like work, not like a dump.<\/li>\n
  3. Save it as a named view – a color helps when three badges sit in a row.<\/li>\n
  4. Pin the two you open every morning. Pinned views can show a live count, and a morning that starts with (47) fulfillment and (3) problems is already a plan.<\/li>\n<\/ol>\n\n\n\n

    Screen Options forgets the moment you click into an order and come back; saved WooCommerce order views do not. That is the job OrderFusion<\/a> is for: columns, filters, and a view you return to without rebuilding the row. The click-by-click lives in the saved-views post – no second tutorial here.<\/p>\n\n\n\n

    Start with two of those three<\/h2>\n\n\n\n

    Do not build a dashboard of seven on day one. Warehouse plus support covers most shops; add accounting when month-end still means a CSV. Two WooCommerce order views used every morning beat seven built for a screenshot. Extra queues you may already have written down: orders missing tracking numbers<\/a>, and a high-value \/ VIP queue<\/a>. Those are their own posts – point people there instead of pasting the recipes again.<\/p>\n\n\n\n

    Two more you can add later without a new article: holds, failed, and refunded as a \u201cproblem\u201d list (status history on the row helps), and first-time buyers this week if someone actually writes them. If nobody writes them, skip the view. A badge nobody opens is clutter.<\/p>\n\n\n\n

    Build two. Use them for a week. If someone still opens the unfiltered list \u201cjust to look,\u201d the view is missing a column they need – add that column, not a fourth view.<\/p>\n\n\n\t

    \r\n\t\t

    WooCommerce Plugin<\/p>\r\n\t\t

    Want to filter orders, add custom columns, and export CSV from your WooCommerce admin? Try OrderFusion<\/a> \u2014 free Lite on WordPress.org, Pro on WooCommerce.com.<\/p>\r\n\t\t

    \r\n\t\t\tInstall OrderFusion Lite (free)<\/a>\r\n\t\t\t \u00b7 \r\n\t\t\tView OrderFusion Pro on WooCommerce.com<\/a>\r\n\t\t<\/p>\r\n\t<\/div>\r\n\t\n\n","protected":false},"excerpt":{"rendered":"

    How to set up WooCommerce order views so warehouse, support, and accounting each get a job screen – not one shared orders list.<\/p>\n","protected":false},"author":1,"featured_media":1402,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[376],"tags":[187,191,197,193,195],"class_list":["post-1215","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-376","tag-filters","tag-order-management","tag-orders","tag-views","tag-workflow"],"_links":{"self":[{"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/posts\/1215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/comments?post=1215"}],"version-history":[{"count":9,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/posts\/1215\/revisions"}],"predecessor-version":[{"id":2435,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/posts\/1215\/revisions\/2435"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/media\/1402"}],"wp:attachment":[{"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/media?parent=1215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/categories?post=1215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/presta.site\/blog\/wp-json\/wp\/v2\/tags?post=1215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}