When you build your online store using WordPress and WooCommerce, you get a flexible and powerful platform — but also a different kind of support model than you might be used to from more closed, proprietary systems.
In this article, we’ll explain how support and troubleshooting actually work in practice, and who is responsible for what when something goes wrong.
WordPress and WooCommerce are what we call open source projects. This means the code is open and freely available for anyone to use, modify, and build upon. But it also means that no single company owns or controls the entire system.
Instead, your store is typically a combination of components like:
Each of these parts has different developers, different responsibilities, and different support channels. That’s why it’s important to understand where a problem belongs when something isn’t working as expected.
Here’s an overview of the most common components in a WooCommerce store — and who is typically responsible for each part:
| Component | Responsible party |
|---|---|
| WordPress core | WordPress.org / the open source community |
| WooCommerce plugin | Automattic (the company behind WooCommerce) |
| Other plugins | The specific plugin developer |
| Theme | The theme developer or your agency/developer |
| Web hosting / server | Your hosting provider |
| Payment & shipping plugins | For example, Krokedil or another plugin vendor |
| Custom code / modifications | You or a developer you’ve hired |
When something isn’t working in your store, it’s easy to get frustrated. But with a structured troubleshooting mindset, you can quickly narrow down the issue — and figure out who to contact. Here are some practical tips:
Before diving into the step-by-step process below, we strongly recommend setting up a staging or test environment (read more here) if you don’t already have one. A staging site is a safe copy of your store where you can test things without affecting real customers or orders.
If you don’t have access to a staging environment, make sure to take a full backup before making any changes. That way, you’ll be able to restore your store if something goes wrong.
Keep in mind that any orders placed after your backup was taken will be lost if you restore it — another good reason to troubleshoot in a separate test environment whenever possible.
A common first step is to switch to a default theme like Storefront, and temporarily disable all plugins except WooCommerce.
If the problem goes away, it’s likely related to your theme or one of the other plugins.
You can then re-enable one plugin or theme at a time to pinpoint exactly when the issue appears — making it easier to identify the root cause.
Under WooCommerce → Status, you’ll find lots of technical details — including your server environment, versions, and any detected errors.
This information is often extremely valuable to support teams, as it gives them insight into how your store is configured and helps identify potential conflicts or issues.
Many plugins — especially payment gateways — write logs that can be accessed under WooCommerce → Status → Logs.
These logs may show errors from API calls, failed communications with external services, or other critical events.
Support teams often ask for logs like these, as they can provide essential clues for understanding what went wrong.
To better understand what’s happening (and when), try to reproduce the issue step by step.
Take note of exactly what you do, which page you’re on, what options you select — and what the result is.
The more clearly you can describe the steps that lead to the issue, the easier it will be for support to assist you effectively.
It’s also helpful to know whether the issue occurs consistently or only under certain conditions.
Once you’ve collected relevant information — such as logs, system status, and a clear description of the issue — it’s time to contact the right support channel.
Refer to the section Who is responsible for what? above to determine who to reach out to.
If the issue is related to, for example, a payment integration from Krokedil, we recommend contacting our support team and including as much relevant information as possible. This may include:
A well-prepared support request can save both you and the support team a lot of time.
We’ve created a separate guide on how to prepare a support ticket — feel free to check it out before submitting your ticket.
It’s important to remember that the open source world is built on collaboration. No one controls the entire stack — but everyone involved, whether it’s developers, plugin vendors, agencies, or you as the store owner, can work together to solve issues.
A clear and constructive troubleshooting report is often the fastest way to get the help you need.
Working with WordPress and WooCommerce gives you a great deal of freedom — but it also means that, as a store owner, you sometimes need to take a more active role in troubleshooting.
By understanding how the ecosystem fits together, and knowing who is responsible for what, it becomes much easier to move forward when something isn’t working as expected.
And remember — you’re not alone. There’s an entire community, forums, plugin developers, and support teams out there who want to help.
As long as you can clearly describe the problem, there’s a good chance you’ll get a quick and relevant response.
Swedbank Pay Payment Menu gives you the tools to create secure and seamless payments – for both you and your customers. With Swedbank Pay you get access to a wide range of payment methods, clear reporting, and consolidated payouts.
With Kustom Checkout, you get the next-generation payment experience for WooCommerce – built on the foundation of Klarna Checkout and over a decade of experience from Krokedil. New name, same trusted core.
Increase the order value and get higher revenue. With Post Purchase Upsell, the customer can add additional products to their order after a completed purchase. They easily choose which of the selectable products they want to add and update their order with one click.
