Pantry Handover compared with White Label CMS, Ultimate Dashboard and Branda

Pantry Handover puts the information a client needs in front of them inside their own dashboard: a widget and a Site Guide page carrying your notes, a list of links and how to reach you for support. That is the whole job.

Almost nobody buys a plugin for that job on its own. Agencies reach for whatever tool is already doing something adjacent: a white-labelling plugin's custom dashboard panel, a team-notes plugin meant for internal use, or a general dashboard-customisation tool that happens to let you paste in some text. Each of those solves the handover problem as a side effect of a larger tool built for a different, broader job, and the rest of that tool's settings, modules and upsells come along whether the agency uses them or not.

This article compares Pantry Handover with the plugins agencies actually have installed for this, is specific about what each one costs a site that only wants a client guide, and says plainly where one of the larger plugins is still the better choice. The answer is not always Pantry.

The plugins most people install

WP Dashboard Notes has 20,000+ active installations and is tested up to WordPress 6.8.8, which is far enough behind current core that wordpress.org shows its own compatibility warning on the listing. It is free with no paid tier. It adds coloured sticky notes to the WordPress dashboard, either plain text or a checklist-style list note, marked public or private, edited in place with no separate save step. It has no dedicated guide page outside the dashboard, no support-contact fields, no way to choose which roles see a note beyond WordPress's own dashboard access, and no export or import.

White Label CMS, built by Video User Manuals, has 200,000+ active installations, the largest of this group, and is tested up to WordPress 7.0.4. It is free, with no paid upgrade advertised on its own listing; one reviewer notes it "does it all, out of the box and without asking for a Pro version." Beyond a client-facing job, it rebrands the login page with a client's own logo and background image, adds custom branding to the admin bar, menu and footer, hides menu items by role through a setup wizard, and replaces the default dashboard with a custom panel that can carry an RSS feed from the agency's own site.

Ultimate Dashboard has 60,000+ active installations and is tested up to WordPress 6.9.7. The free plugin removes WordPress's default dashboard widgets and adds a limited set of custom text, icon and HTML widgets in their place. Ultimate Dashboard PRO, sold separately from ultimatedashboard.io, costs $58 a year for one site, $98 for five, or $178 for unlimited sites, and adds removing other plugins' dashboard widgets, custom admin CSS, a login page customiser, an admin menu editor, multisite support, and restricting which widgets and admin pages a role can see.

Branda, published by WPMU DEV, has 20,000+ active installations and is tested up to WordPress 7.1, the most recently updated of the four. The free version carries more than 30 modules covering admin styling, login pages, system emails, maintenance mode and more, and its own FAQ describes the free tier as complete but including "contextual promotion of our other relevant plugins." Branda Pro, bundled into a wider WPMU DEV membership, adds SMTP email logs, automated white-label client reporting and white-label client portal creation.

Where the big plugins cost you

WP Dashboard Notes solves a narrower problem than a handover guide, and its own listing shows the gap: a note is either public to anyone with dashboard access or private to its author, with nothing in between, so there is no way to show a guide to a client's editor without also showing it to everyone else who logs in. There is no support-contact block and no export, so an agency that wants those still needs a second plugin or a habit of retyping the same details on every new site. The compatibility warning on its listing is the plugin's own, not an inference from the changelog.

White Label CMS's dashboard panel is one feature inside four separate customisation areas, reached through its own setup wizard: login-page branding, admin bar and footer branding, the dashboard panel, and per-role menu hiding. An agency that only wants the client guide still gets a plugin built to rebrand the entire wp-admin experience, with the settings and the surface area for a login-page redesign sitting unused unless it is switched on.

Ultimate Dashboard's free listing tells the reader directly where the paywall is: "For even more features, check out Ultimate Dashboard PRO" and "For multisite support & more check out Ultimate Dashboard PRO" both appear in its own description. Restricting which widgets or pages a role can see, hiding other plugins' dashboard widgets, and any white-labelling at all sit behind the $58-to-$248-a-year subscription; the free plugin only adds and removes simple widgets.

Branda's free version is not paywalled, by its own account, but more than 30 modules is a lot of settings surface for a plugin an agency installs to show a client one guide screen, and its own FAQ confirms the free version promotes WPMU DEV's other plugins inside its own screens. Branda also offers an opt-in newsletter signup that, per its listing, sends the site administrator's email address to Mailchimp and sets a cookie; it is opt-in and only affects the administrator, not site visitors, but it is an external request a plugin bought purely for a client guide would not need to make.

Across all three of the broader tools, the login page and the admin menu are part of what gets customised. That is more of the admin area for a client's WordPress update, a theme change or a plugin conflict to disrupt, and more for the agency to check when a client cannot log in and calls asking why.

What Pantry Handover does instead

Pantry Handover's scope is a dashboard widget and a Site Guide admin page, both with a title the agency sets, notes written in the standard WordPress editor with normal formatting allowed, a list of links with labels, and a support block for company name, email, phone, hours and website, where any field left blank is left off the guide rather than shown empty. Administrators always see the guide; other roles can be added to the list of who may view it, but only administrators can edit it. A separate set of switches hides the five default WordPress dashboard boxes, welcome panel, Quick Draft, Activity, WordPress Events and News, and Site Health, each one off by default. The guide can be exported as a JSON file and imported on another site, for an agency setting up the same guide structure repeatedly.

Measured on the release zip: 21 KB, 1,373 lines of PHP, one option (pantry_handover_settings), no custom database tables, no post meta, no cron events, no transients, an admin CSS file and one admin JS file loaded only on Plugin Pantry > Handover, no front-end assets anywhere on the site, and no external requests of any kind. There is no dashboard nag, no feature that stops working after a trial period, and no setting that exists only to be unlocked by a paid add-on.

Two scope decisions are worth explaining. Pantry Handover only ever hides the five WordPress boxes it names; it does not try to hide other plugins' dashboard widgets, because that would mean reaching into other plugins' registrations rather than WordPress's own, a much less reliable thing to promise across every plugin combination and every core update. And the export and import work through a plain JSON file rather than a hosted sync service, which is also why they cost nothing in external requests; syncing a guide across many sites automatically is real extra scope, and it is reserved for the Pro add-on rather than smuggled into the free plugin as a background connection.

What it does not do, and who should stay with the big plugin

Pantry Handover does not white-label WordPress: no renamed admin area, no custom login screen, no admin colour scheme. It does not hide plugins or menu items from anyone who can already see them. It has no ticketing or chat feature.

An agency that wants a client to never see the word WordPress, with a rebranded login page and admin bar, is better served by White Label CMS, which does exactly this for free, or by Branda or Ultimate Dashboard PRO if the bundled modules or the subscription's other features are already worth paying for. An agency that wants a client's editor account to be unable to see the Plugins menu at all, not just told to leave it alone, needs the per-role menu control that White Label CMS, Branda and Ultimate Dashboard PRO each provide and that Pantry Handover deliberately does not. And an agency that wants actual support tickets or live chat with a client, rather than a phone number and an email address on a guide page, needs a dedicated help-desk plugin; none of the four plugins compared here cover that either, because it is a different job from a client guide.

None of this is a quality judgement on the larger plugins. An agency managing white-labelled admin areas across dozens of client sites, with per-role menu restrictions and a rebranded login screen on all of them, is using real, work-justified scope, and paying for it is reasonable. Pantry Handover is for the agency, or the in-house team, whose actual need is narrower: leave the client a guide, and stop there.

Moving over

White Label CMS is the largest of the four and the closest functional overlap, through its custom dashboard panel, so it is the most likely plugin an agency is moving away from for this specific job. If that panel holds free text or HTML written for a client, copy it into Pantry Handover's Notes field; the standard WordPress editor accepts the same headings, bold, italic, lists and links. Contact details that were typed into that same free text move into the dedicated Support fields, company name, email, phone, hours and website, so a phone number is not lost inside a paragraph. Any links listed there move into the Links list, one row per link.

White Label CMS's login-page branding, admin bar and footer branding, and per-role menu hiding sit outside what Pantry Handover does. Keep White Label CMS active for those settings if they are in use, or replace them with a dedicated white-labelling plugin; Pantry Handover will not take them over, and nothing about installing it requires switching them off.

Anyone moving from WP Dashboard Notes, Ultimate Dashboard's default widget or Branda's dashboard module should expect the same pattern: copy the note text and any links across by hand, since there is no shared file format between unrelated plugins to import from. Where a competitor's dashboard clean-up setting hides more than WordPress's own five default boxes, for instance third-party plugin widgets, switching to Pantry Handover brings those other widgets back, since it only ever hides the five it names; anything else needs to be hidden through that plugin's own settings, or left visible.

Pantry Handover's own export and import only read a JSON file produced by Pantry Handover itself. It is built for copying a finished guide to the next site once it is set up, not for reading a competitor's settings.

The short version

Pantry Handover is worth installing when the whole job is a guide and a way to reach the agency, inside the client's own dashboard, and nothing more. It leaves branding, menu hiding and support ticketing to other plugins on purpose, because taking any of them on would mean the free plugin stops being one settings screen and one option. Agencies that need a client to never see the word WordPress, or need menu items hidden rather than merely left alone, are better served by one of the four plugins above; agencies that only need somewhere to leave notes, links and a phone number are not.

Measure	Pantry Handover
Zip size	21 KB
PHP lines	1,373
Options	1 (pantry_handover_settings)
Tables	0
Front-end assets	0
External requests	0
Tracking	None
Locked features	None