PrestaShop

Mastering PrestaShop Back Office Product Pagination: Your Guide to Defaulting Products Per Page

Efficient back office management is the backbone of any successful PrestaShop store, especially when you're juggling an extensive product catalog. Navigating through hundreds or thousands of products can quickly become a bottleneck if your interface isn't optimized for speed and clarity. A common user request, and a frequent topic in the PrestaShop community, revolves around customizing the display of product listings for an enhanced workflow.

At Migrate My Shop, we understand that these seemingly small configuration details can have a significant impact on daily operations and overall productivity. This guide delves into a specific query from the PrestaShop forum, addressing how to set a default number of products per page in the Back Office, and provides comprehensive insights for both new and seasoned PrestaShop merchants.

PrestaShop Back Office pagination dropdown menu for products per page
PrestaShop Back Office pagination dropdown menu for products per page

The Quest for Default Back Office Product Pagination

The discussion began with a user, dxshop186, inquiring about a built-in setting to default the Back Office product list (specifically under Catalog > Products) to 50 items per page. The user correctly identified that while manual adjustment via a dropdown was possible, the "Products per page" option found in Shop Parameters > Product Settings only affected front office category pages. Crucially, their primary goal was to find a solution that avoided modifying core PrestaShop files – a best practice we wholeheartedly endorse for system stability, ease of upgrades, and long-term maintainability.

PrestaShop's Pagination Logic: A Personalized, Per-Employee Approach

The expert response from Knowband Plugins provided a definitive answer: PrestaShop does not feature a shop-wide, built-in setting to globally dictate the default number of products per page for all Back Office users.

Instead, this setting is designed to be employee-specific. When an administrator or employee selects a page size from the dropdown – typically found at the bottom of the product list, adjacent to the page navigation controls – their choice is remembered and stored for their individual employee account. This intelligent design allows each user to personalize their product display density, ensuring their preference persists across sessions without impacting other employees' settings. It's a nod to individual workflow optimization, allowing each team member to tailor their environment to their specific tasks and screen size.

This approach offers flexibility but also means there's no central administrative panel to enforce a universal default for all staff members. For large teams, this might necessitate a different strategy, which we'll explore shortly.

Key Insights and Practical Considerations for PrestaShop Users

Understanding the nuances of PrestaShop's pagination behavior is key to optimizing your back office experience:

  • Individual User Preference: The "products per page" selection in the Back Office is saved per employee. This means if you set it to 50, it will remain 50 for your account until you change it again. Other employees will have their own settings.
  • Dropdown Visibility: The page-size dropdown control only appears when the list contains more rows than the smallest available option. If your product list is very short (e.g., fewer than 20 items), you might not see the dropdown at all, as there's no need to paginate.
  • The "Quirk" of Saving: An interesting detail is that the selected value is only explicitly saved when it differs from PrestaShop's built-in default. For many legacy lists, this default is already 50. So, if your list is currently showing 20 items (perhaps due to a previous override or specific module behavior) and you select 50, it might appear not to stick if 50 was already the underlying default. However, for most users, selecting 50 will indeed save that preference.
  • Version Differences: PrestaShop 8 & 9 (Symfony Grid): This is a critical point for modern PrestaShop users. PrestaShop versions 8 and 9 have largely transitioned to a Symfony-based grid system for many back office lists, including the Products page. This modern architecture changes the underlying implementation details slightly compared to older, legacy lists. While the user experience of selecting the page size remains similar, the way these preferences are stored and managed internally might differ. Always ensure your solutions are compatible with your specific PrestaShop version.

For those managing a large inventory, having 50 or even 100 products visible at once can drastically reduce the amount of clicking and page loading, making tasks like quick edits, inventory checks, or bulk actions much more efficient.

Screenshot of PrestaShop Back Office product list with pagination dropdown highlighted
Locating the pagination dropdown in the PrestaShop Back Office product list.

When a Shop-Wide Default is Essential: Advanced Solutions

While PrestaShop's per-employee setting offers flexibility, some businesses, particularly those with large teams or strict operational guidelines, might genuinely require a shop-wide default. Since directly modifying core files is a no-go, what are the alternatives?

1. Employee Training and Documentation

The simplest and most immediate solution for a team is to implement a standard operating procedure. Train all new employees to set their product list pagination to the desired default (e.g., 50 or 100) upon their first login. Include this instruction in your internal PrestaShop user guide.

2. Custom Module Development (The Recommended Programmatic Approach)

For a truly shop-wide, persistent solution that adheres to best practices, a custom PrestaShop module is the way to go. A developer could create a module that:

  • Hooks into the appropriate controller (e.g., AdminProductsController for legacy lists or the Symfony grid component for PS 8/9).
  • Overrides or injects a default value for the number of products per page, ensuring it applies to all employees unless they explicitly change it.
  • Potentially adds a new configuration option in the Back Office where an administrator can set this global default.

This approach keeps your core PrestaShop files untouched, making your store robust and ready for future upgrades. It requires development expertise but provides a clean, maintainable solution.

// Example (conceptual, not production-ready) of how a module might override a default
// This would involve hooking into specific PrestaShop/Symfony events or controller overrides.
// For PrestaShop 1.7.x and earlier (legacy controllers):
// public function hookActionAdminProductsListingFieldsModifier($params)
// {
//     if (isset($params['list_id']) && $params['list_id'] == 'products') {
//         // Check if employee has a saved preference, if not, apply global default
//         if (!isset($this->context->employee->products_per_page) || $this->context->employee->products_per_page == 0) {
//             $params['limit'] = 50; // Set your desired global default
//         }
//     }
// }

// For PrestaShop 8+ (Symfony grid):
// This would involve more complex Symfony event listeners or service decoration
// to modify the grid's default pagination options.
// Example: A service decorator for the ProductGridDefinitionFactory
// to alter the default limit for the product grid.

3. Direct Database Modification (Use with Extreme Caution!)

While technically possible, directly modifying database entries for all employees is highly discouraged. Employee preferences are typically stored in the ps_employee table (or related configuration tables) for each user. Manually updating these values for multiple employees can be error-prone, is not upgrade-safe, and bypasses PrestaShop's internal logic. Only consider this as a last resort for a very specific, one-time fix, and always with a full database backup.

Impact on E-commerce Operations and Migrations

Understanding these granular settings is vital for smooth e-commerce operations. For stores with thousands of SKUs, the ability to quickly scan 50 or 100 products per page can save hours over a week. During a PrestaShop migration, these small configuration details are often overlooked but can significantly impact user satisfaction post-migration. Ensuring your team's workflow is optimized from day one, whether through individual settings or a custom module, contributes to a more efficient and productive environment.

Conclusion

While PrestaShop doesn't offer a global setting for Back Office product list pagination out-of-the-box, its per-employee preference system provides excellent flexibility for individual users. For those needing a shop-wide default, a custom module represents the most robust and future-proof solution, aligning perfectly with PrestaShop's extensibility. By understanding these mechanisms, you can empower your team to manage your product catalog with greater efficiency and precision.

Need expert assistance with PrestaShop optimization, custom module development, or planning a seamless PrestaShop migration? The team at Migrate My Shop is here to help you unlock your store's full potential.

Share:

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools