Our extensions, Shopware
<!–
–>
Data filtering is a powerful enhancement to traditional import and export processes. It allows you to transfer only the essential information, eliminating the need for time-consuming manual cleanup. This significantly boosts the efficiency of your import and export workflows.
However, filtering capabilities vary across e-commerce platforms, and Shopware 6 offers only limited options in this regard. In this Shopware 6 filter guide, we explain how to filter products during import and export in Shopware 6. We reference insights from a key Stack Exchange discussion and share our own hands-on experience with Shopware’s data tools.
Want to go deeper? Don’t forget to explore our Shopware Cookbook for more expert guidance and practical tutorials.
Table of contents
- Shopware 6 Filter & Import, Export Profiles
- Advanced Import & Export Filters in Shopware 6 with Firebear
- Final Words: Advanced Data Management with Shopware 6 Filters and Beyond
- Frequently Asked Questions About Data Filtering in Shopware 6
Shopware 6 Filter & Import, Export Profiles
One recurring question from the community comes from Claudiu Stoica, who asked how to filter products by category in a Shopware 6 import/export profile. The goal was to avoid importing or exporting all products, focusing instead on a specific product category.
Claudiu initially created a corresponding profile and a Shopware 6 filter using the API with the following request body:
|
1
2
3
4
5
6
7
8
9
10
11
12
|
{
“id”: “my99id2cb2784069938089a8a77ctest”,
“label”: “Label test”,
“name”: “name test”,
“sourceEntity”: “product”,
“fileType”: “text/csv”,
“delimiter”: “;”,
“enclosure”: “””,
“createdAt”: “2022-11-10T10:15:22Z”,
“mapping”: [{“key”:“id”,“mappedKey”:“id”,“position”:0,“id”:“someid4f7c6c478b8041cfd5fe0ae0c5”},{“key”:“cover.media.url”,“mappedKey”:“cover”,“position”:1,“id”:“someid0ffa7f48e6b135f6e754d6b93c”}],
“config”: {“createEntities”: false, “updateEntities”: true}
}
|
Despite setting up a valid profile structure, Shopware 6 didn’t offer a straightforward way to filter by category at this level. This limitation sparked a deeper discussion around workarounds and best practices.
Shopware 6 Profile & Existing Endpoint Limitations
According to Dneustadt, a contributor in the same Stack Exchange thread, filtering by category directly in the import/export profile is currently impossible. This limitation stems from how Shopware 6 handles profiles and the restrictions of existing API endpoints. Essentially, the profile configuration doesn’t support conditional Shopware 6 filters like category constraints during data transfers.
This means that every export or import tied to a product entity will include all assigned products, regardless of category, unless filtered manually before or after the process. For store owners and developers dealing with large catalogs or multi-category structures, this presents a significant hurdle.
How to Filter Products by Category in Shopware 6 Export Using a Custom API Endpoint
While Shopware 6 doesn’t natively support filtering by category during import/export operations, you can overcome this limitation by implementing a custom API endpoint. This method allows you to control which products get exported, for instance, by category, bypassing the default system constraints.
Use your admin API credentials to request the following endpoints in that order with the respective payloads:
|
1
2
3
4
5
|
POST /api/_action/import–export/prepare
{
“profileId”: “…”,
“expireDate”: “2022-12-12 12:00:00”
}
|
Where:
- profileId is the id of the profile you want to use for exporting.
- expireDate is a date after which the export would be deemed expired and ready to be deleted.
- file is a parameter that contains the file you’re trying to import, but since you want to export you just omit it.
This endpoint returns logId required in the next step.
|
1
2
3
4
|
POST /api/_action/import–export/process
{
“logId”: “…”
}
|
Request this endpoint with the logId from the prior request to start export/import. Since it runs in the message queue, you’ll have to wait for the process to finish.
|
1
2
3
4
5
6
7
8
9
10
|
POST /api/search/import–export–log
{
“filter”: [
{
“type”: “equals”,
“field”: “id”,
“value”: “…”
}
]
}
|
Next, you can utilize the search endpoint for the import_export_log entities with the logId you received previously as a filter. Do so to check the state of the process. You will be able to proceed with your Shopware 6 filter once it is finished. You’ll also need the fileId from this record for the download.
|
1
|
POST /api/_action/import–export/file/prepare–download/{fileId}
|
Use the fileId to request this endpoint. You will get accessToken in return necessary for the final request.
|
1
|
GET /api/_action/import–export/file/download?accessToken=...&fileId=...
|
Streamline both fileId and accessToken from earlier to request this endpoint which should yield a download stream of the exported file.
However, if you want to implement filters for Shopware 6 export, you will need to request your new custom endpoint instead of starting the process using the existing endpoint when you first retrieve logId. The implementation could look as follows:
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
/**
* @Route(defaults={“_routeScope”={“api”}})
*/
class CustomExportApiController extends AbstractController
{
private ImportExportFactory $importExportFactory;
public function __construct(ImportExportFactory $importExportFactory)
{
$this->importExportFactory = $importExportFactory;
}
/**
* @Route(“/api/_action/custom/export/{logId}/{categoryId}”, name=”api.action.custom.export”, methods={“POST”})
*/
public function customProductExport(string $logId, string $categoryId, Context $context): JsonResponse
{
$importExport = $this->importExportFactory->create($logId, 50, 50);
$logEntity = $importExport->getLogEntity();
if ($logEntity->getState() === Progress::STATE_ABORTED) {
return new JsonResponse([‘success’ => false]);
}
$criteria = new Criteria();
$criteria->addFilter(new EqualsAnyFilter(‘categoryTree’, [$categoryId]));
$offset = 0;
do {
$progress = $importExport->export($context, $criteria, $offset);
$offset = $progress->getOffset();
} while (!$progress->isFinished());
return new JsonResponse([‘success’ => true]);
}
}
|
After calling your custom endpoint proceed with the steps described earlier.
Custom API Endpoint Limitation: Why It Won’t Work for Shopware Apps
While the custom API endpoint approach gives developers fine-grained control over a Shopware 6 filter aimed at product export, including category filtering, it comes with a major limitation: it’s not suitable for apps.
Apps in Shopware 6 operate in a sandboxed environment with restricted permissions. As a result:
- You cannot register custom Symfony controllers within an app.
- You’re limited to using only the Admin API and the App System’s lifecycle events and webhooks.
This makes it impossible to implement the kind of controller-based logic required for the filtering workaround shown above.
So, How Can App Developers Address This To Implement a Shopware Filter?
If you’re building an app and need a Shopware 6 filter for export, consider these alternative solutions:
1. Use the Admin API for Post-Processing
Instead of filtering during the export, let the export run as-is, then:
- Download the resulting export file using the regular API flow.
- Parse and apply a Shopware 6 filter to the data on your app’s server before forwarding it to its destination or storing it.
This moves filtering logic outside Shopware, into your app’s backend.
2. Use a Scheduled Task + Webhook Combo
You can:
- Create a scheduled task in Shopware to run regular exports.
- Register a webhook in your app to receive export completion events.
- When triggered, fetch the file and apply filtering externally.
3. Pre-Export Category Tagging or Custom Fields
If the Shopware catalog is manageable and relatively static:
- Encourage users to tag or mark exportable products using custom fields or special tags.
- Let your app filter the export file based on these flags — e.g., only include products where customField.exportable = true.
4. Suggest a Plugin-Based Alternative for Reliable Shopware 6 Filter
If filtering logic is critical and performance-sensitive, consider offering a Shopware plugin instead of an app. Plugins can register custom controllers and integrate tightly with Shopware’s internal services, unlike apps.
⚠️ Note: Plugins require installation access to the Shopware instance, so this approach won’t work for merchants using SaaS-hosted versions where plugins aren’t allowed.
While Shopware’s app framework imposes limits on what you can do natively, creative use of the API and external processing pipelines can still deliver solid results — especially if you’re handling filtering on your own infrastructure.
Advanced Import & Export Filters in Shopware 6 with Firebear
When it comes to managing large volumes of product and order data, filters and conditions are essential. They help you narrow down exports to only the necessary items and, potentially, prevent importing irrelevant records. At Firebear, we’ve developed solutions that extend the default data handling capabilities of Shopware 6 — making your workflows faster, cleaner, and more reliable.
Below, we’ll show how our Improved Import, Export & Mass Actions app for Shopware 6 enables advanced export filtering and what to expect regarding import filters.
How to Create a Shopware 6 Filter for Export
Using the Improved Import, Export & Mass Actions app, you can apply custom Shopware 6 filters to your export profiles with ease. Here’s how the process works:
Step 1: Create or open an export profile. Navigate to the app’s export section and choose or create the profile you want to configure.
Step 2: Open the “Filter” screen. Here, you define which data should be included in the export.
Step 3: Add a Shopware 6 filter. To avoid exporting all records:
- Click the “+” button to create a new filter.
- Select a product property to filter by — for example, orderDate to target orders by creation date.
- Choose an operator, such as Range, which allows defining a time interval.
- Enter a value — like “last week” or a custom date — to specify the data range.
You can add multiple filters to fine-tune the export even further.
👉 Interested in having filters tailored for your Shopware data export functionality? Contact us now to explore custom solutions.
What About a Shopware 6 Filter for Import?
Import filtering is a slightly different challenge. Since third-party systems often use non-standardized attribute formats, it’s not as simple as applying a direct filter to external data.
At this point:
- Our Shopware 6 import module supports powerful attribute mapping, allowing you to align external data to your internal structure.
- However, it doesn’t currently support import filtering based on external file content, mainly because demand has been limited.
That said, if more users express interest in this feature, we’re open to implementing it in future updates to the Improved Import, Export & Mass Actions app.
For now, if you want to explore this functionality or influence our roadmap, please reach out via our Firebear Help Center.
Other Advanced Import & Export Features for Shopware 6
The Improved Import, Export & Mass Actions application is designed to solve the most common data transfer challenges in Shopware 6. Whether you’re managing a growing catalog, migrating data between systems, or automating routine admin tasks, this app gives you the flexibility and control you need.
Thanks to full support for product properties and advanced automation, you can easily edit your catalog in a spreadsheet editor, re-import it in bulk, or schedule regular data operations — all without the risk of manual errors.
Here’s what you can expect from the app beyond filtering:
- ✅ Product import and export with full support for properties (attributes). Seamlessly transfer products while preserving all associated data like descriptions, prices, and custom attributes.
- 👥 Customer import and export with complete address support. Migrate and update customer records with billing and shipping address details intact.
- 🧾 Order export. Export order data for accounting, analytics, or integration with third-party systems.
- 🧬 Support for product variants and all related attributes. Export/import products with variations (e.g., size, color), preserving complex configurations.
- 🎯 Attribute mapping and mapping presets. Align external data structures to your internal schema with reusable presets.
- ⏰ Scheduled imports and exports. Automate repetitive tasks with flexible scheduling — daily, weekly, or custom intervals.
- 📄 Support for CSV, XLSX, and XLS files. Work with the most common spreadsheet formats for maximum compatibility.
- ☁️ Direct file uploads & FTP/FTPS support. Import from local sources or pull/push data from secure remote servers.
Want to dive deeper into how our app transforms Shopware 6 data workflows? Click here to learn more about the Improved Import, Export & Mass Actions app:
- Improved Import, Export & Mass Actions application for Shopware 6
- Improved Import, Export & Mass Actions Manual
Final Words: Advanced Data Management with Shopware 6 Filters and Beyond
Data filtering is one of the most critical enhancements you can introduce to your import and export workflows in Shopware 6. It allows you to transfer only the data that matters — whether that means exporting products from a specific category or importing only records that meet predefined conditions. While native Shopware 6 tools offer limited filtering capabilities, Firebear’s Improved Import, Export & Mass Actions app opens the door to powerful, flexible, and fully customizable filters.
Beyond Shopware 6 filter capabilities, our app offers a full suite of features — from product variant handling and customer address support to scheduling and FTP integration.
Whether you’re running complex data transfers or simply looking to streamline your catalog management, Firebear provides the tools and expertise you need. Reach out to us for custom implementations, feature requests, or expert support.
Let’s make Shopware data work the way you need it to.
Frequently Asked Questions About Data Filtering in Shopware 6
Can I filter products by category when exporting in Shopware 6?
By default, Shopware 6 doesn’t allow filtering by category during export. However, with custom development or third-party tools like Firebear’s app, you can implement this functionality.
How do I apply an export Shopware 6 filter in the Improved Import, Export & Mass Actions app?
In the app, go to the export profile, navigate to the Filter tab, click the “+” button, choose a product property (like orderDate), select an operator (such as Range), and define the desired value.
Can I create multiple filters in an export profile?
Yes, you can add multiple filters in the export filter interface to fine-tune which records are exported.
Does Shopware 6 support import filters natively?
No, Shopware 6 does not support conditional filtering during import. It imports all valid records in the provided data file.
Can I filter imported data in the Improved Import, Export & Mass Actions app?
Currently, the app does not support import filtering. However, you can map external attributes before import. Filtering may be added if demand increases.
Are export filters available for all entity types (products, orders, customers)?
Yes, you can apply export filters across different entity types such as products, orders, and customers within Firebear’s app.
What attributes can I use for filtering exports?
You can filter by standard system attributes like SKU, orderDate, subtotal, and custom fields if they are mapped correctly in the profile.
Can I automate filtered exports in Shopware 6?
Yes, with the Firebear app, you can schedule filtered exports to run automatically at defined intervals.
Is it possible to filter export data using a custom Shopware 6 API controller?
Yes, developers can create custom API endpoints to apply filters — such as category-based filters — during the export process. This requires plugin-level access.
How can I get support for adding custom filtering features?
You can contact Firebear’s help center for guidance on implementing advanced filters or requesting new features in the Shopware 6 app.
Please enable JavaScript to view the comments powered by Disqus.
