Frontend packing dashboard

Hiring staff to help with packing is a good moment in your shop’s life. Worrying about who can see what, who can change what, and whether you remembered to lock down the right settings every time you add someone — that’s the part nobody loves.

The frontend packing dashboard takes that off your plate. Your packers get a single page on the front of your site with exactly what they need: today’s orders, sorted by your priority rules, with the actions they’re allowed to take and nothing else. They don’t need wp-admin access. You don’t have to audit permissions every time you hire someone.

And because WordPress roles are additive, the Packer role layers onto whatever your staff already do — Editor + Packer, Author + Packer, Administrator + Packer — without replacing what’s already there.

Setting it up

You build any page on your site (Bricks, Gutenberg, whatever page builder you use) and drop in either:

• The [tracksies_staff_dashboard] shortcode, or
• The Packsie Staff Dashboard Bricks element

Save the page. Tell your packers the URL. They sign in and they’re working.

What the page shows

Three tabs:

• Orders — today’s packing queue, sorted by your priority rules. Each card shows the customer, line items, any customer note, and the actions the packer’s role is allowed to take.
• Returns — pending returns with the customer’s stated reason and items being returned. Each one opens an inspection screen where the staff member records condition and resolution.
• Customers — quick lookup for context: tags, recent orders, lifetime value. Helps the packer answer a customer question on the spot.

The same dashboard you’d see inside the admin staff dashboard, just rendered on a public-style page with the right protections in place.

Built-in protections

The dashboard sits on a public URL, so it has guard rails to make sure casual visitors and search engines don’t see anything they shouldn’t:

• Search engines are blocked. A noindex, nofollow robots meta tag is added automatically when the dashboard is on a page. Google won’t list it.
• Logged-out visitors are redirected to the login page, with a return URL back to the dashboard so they land there once they sign in.
• Logged-in users without the right role see an Access Denied panel pointing back to the homepage. The redirect destination is configurable in Packsie settings.
• Role membership is checked on every render. Packsie reads the configured Packing Allowed Roles list and only renders the dashboard for users in those roles.
• Capability is checked too. The manage_packing capability (granted to the Packer role automatically) is the underlying gate.
• Every action requires a fresh nonce and re-checks the user’s role. Stale tabs and shared sessions can’t fire actions on someone else’s behalf.

If a staff member accidentally shares the URL or someone bookmarks it on a shared computer, casual visitors get nothing useful.

Pairing with kiosk mode

For shops running a tablet or shared terminal in the warehouse, Packsie has an optional kiosk template that strips your theme’s header, footer, and chrome away. The dashboard fills the screen — handy when you want one device dedicated to packing and not much else. Switch it on per page in Packsie settings.

Why we built it this way

You shouldn’t have to give wp-admin access to every staff member just so they can do their job. The frontend dashboard means you can hire help without worrying about what they can see or change — they get the work, and only the work, on a page that fits your site’s brand. You get to think about other things.