New payments admin menu entry? What for?

Resolved T4ng
(@schwipps)

4 months ago

Hi,

I just updated WooCommerce to 9.4.2. I’m not sure it’s specific to that version, but I noticed a new Payments entry in the main WordPress admin menu, right below “Products”. Which makes it the fourth first level menu entry, just for WooCommerce.

That payment button, appears to be a shortcut, to /wp-admin/admin.php?page=wc-admin&task=payments, where we’re offered to set additional payment methods.

As a store manager, I can say we don’t need to set an additional payment method every morning, so that it’s not useful, at all, having this option available from this already-very-busy main menu.

Now, that page is different from the Settings > Payments (/wp-admin/admin.php?page=wc-settings&tab=checkout) page, where payments methods are set.

Adding a new distinction for additonal payment methods just makes the whole thing more confusing. Additional payment methode are… payment methods. We probably can stick with that, or at least set both classic and additional payments methods from that single page.

If not the default behaviour, can you please provide us with an option to remove that Payments entry from the main menu?

Thank you.

Viewing 11 replies - 1 through 11 (of 11 total)

Fabian Todt
(@gaambo)

4 months ago

I can only agree with OP here.

I also found this Github issue: https://github.com/woocommerce/woocommerce/issues/39668

It was closed, allthough the menu item is still there. But at least it contains code snippets to remove it.
Plugin Support shahzeen(woo-hc)
(@shahzeenfarooq)

4 months ago
Hi there!

I understand your concern. I can see the WooPayments button on my test site as well. You can hide it using the snippet below.
```
function remove_payments_ad_tab(): void {
  remove_menu_page("admin.php?page=wc-admin&task=woocommerce-payments");
}
add_action("admin_menu", "remove_payments_ad_tab", 999);
```
You can use a code snippet plugin to add the provided code. However, please note that we generally don’t provide support for custom code. Additionally, I’ve noticed that many users have reported this issue here: GitHub Issue #39668. I recommend adding your comment there as well, so our developers can review it and potentially address the issue in future updates.

Thank you
Thread Starter T4ng
(@schwipps)

4 months ago

OK, thanks.

Though I feel it’s more a practice concern rather than a technical issue.

Best Regards.

ckadenge (woo-hc)
(@ckadenge)

4 months ago

Hi @schwipps,

Though I feel it’s more a practice concern rather than a technical issue.

Thank you for sharing your concern with us.

However, I’d just like to understand if you already had the chance to test out the code that was shared in the previous reply above. If you did, could you please confirm if it works as expected?

Thread Starter T4ng
(@schwipps)

4 months ago

Hi,

Thanks @gaambo for pointing that gitHub topic.
Thanks @shahzeenfarooq, @ckadenge for pushing it.

I just tested this code, and indeed, it works as expected.

I just hope I won’t need it anymore in 9.4.3 and further versions.
Still needing it would mean Auttomatic pushes its business too hard from the free version.
Renaming it again would just be despicable.

You’re right, concern is the word here. WordPress certainly need money to keep going. But such methods are definitely not the best way to keep it popular over the long run.

I really don’t run for them, but Auttomatic can’t blame competitors for their methods unless the house is in order.

ckadenge (woo-hc)
(@ckadenge)

4 months ago

Hi again @schwipps,

We’re glad to hear that the code you tested is working as expected.

We appreciate your feedback. WooCommerce is committed to continually improve our products and services, and your input plays a significant role in that process.

Changes can sometimes be disruptive, but we assure you that our goal is always to enhance the user experience and meet the needs of all our merchants.

Regarding future versions, we are continuously working to improve WooCommerce, and we take all user feedback into account. We aim to strike a balance between maintaining a robust free version of our product and offering premium features that add value for our users.

Also, a healthy competitive environment pushes us to deliver better products and services. Rest assured, we are committed to keeping our house in order and maintaining the trust of our users.

Cheers!
Thread Starter T4ng
(@schwipps)

3 months, 1 week ago
Hi,

Glad to see you guys didn’t changed the page address/option again for this last update.
Still, you didn’t remove the menu entry.
- This reply was modified 3 months, 1 week ago by T4ng.
Plugin Support Jonayed (woo-hc)
(@jonayedhosen)

3 months, 1 week ago

Hi @schwipps ,

I understand you’re still experiencing the issue, and the latest updates haven’t resolved it yet. However, looking at a related issue (GitHub link), it appears the developers are actively working on a fix. The pull request for this issue has already been merged, which is a promising sign.

I’d recommend keeping an eye out for the next update and checking the changelog to see if this issue has been addressed: WooCommerce plugin changelog.

Thank you for your understanding and patience!
Thread Starter T4ng
(@schwipps)

3 months, 1 week ago
Hi @jonayedhosen,

To my understanding, this issue you’re pointing, basically says that the new expected behavior, long story short, should be:

“Do you know WooPayments? Did you already install it? Have you really really considered installing it?! Because you really really should (considering we really really want your money on every single transaction!). Anyway, as long as you won’t have it installed, I’ll keep showing that useless top-level menu entry. And this behavior will remain until you enabled WooPayment, for every single payment method WooPayment is ready to take a spoon at the cake.”

How about dropping support for non-WooPayment gateways instead?
- This reply was modified 3 months, 1 week ago by T4ng.
- This reply was modified 3 months, 1 week ago by T4ng.
Plugin Support Feten L. a11n
(@fetenlakhal)

3 months, 1 week ago
Hi there,

Thanks for sharing your feedback with us. I understand your frustration regarding the WooPayments prompts and menu visibility.

The WooPayments menu entry is designed to make merchants aware of our integrated payment solution. I want to be transparent about why WooPayments is prominently promoted:
1. Integration Revenue: WooPayments is WooCommerce’s native payment solution, and like any business, we earn revenue from transaction fees, which helps fund continued platform development, like WooCommerce (which is free)
2. User Experience Benefits:
- Built-in fraud protection
- Seamless integration with the WooCommerce admin interface
- Simplified setup process compared to some third-party solutions
- Unified support channel for both platform and payment issues
But I acknowledge that the current implementation may feel too persistent. Your feedback about the prominence and frequency of these prompts is valuable and something we can relay to our product team.

With this, I’ll go ahead and close this thread. If you have any specific bugs or issues on your website, don’t hesitate to open a thread!
Thread Starter T4ng
(@schwipps)

3 months, 1 week ago

I understand you need revenues, and I understand your solution -WooPayments- offers users benefits, for those who are interested in what it offers.

But many users also made another choice, with other gateways implemetions, plus probably don’t want to add multiple payment methods to their website. Believe it or not, some of them probably have good reasons to make that choice.

So I’m not saying WooPayment is evil, I’m just saying you can’t leave an advertising hoarding on all every admin pages, for all WooCommerce users.

I suggest you basically provide a tickbox, as a WooCommerce Advanced setting, to allow aware users to remove this useless entry menu.

Viewing 11 replies - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.

Tags