Dashboard & UI – Release Notes

09 Jun 2025

Advanced Filtering on the Order Listing Page

Managing orders just got easier. We’ve introduced a powerful new filtering system to the Order Listing page in HDL Commerce, giving you faster access to the data you need.

What’s New

You can now filter orders using multiple dynamic criteria — making it easier to locate specific orders, analyze sales activity, and streamline your daily operations.

Available Filters:

  • Customer Type – Segment orders by customer category

  • Date Range – Filter by order dates (From → To)

  • Order Status – Quickly identify open, completed, or canceled orders

  • Sales Channel – View orders by storefront, marketplace, or B2B portal

  • Currency – Separate local and international transactions

  • Payment Method – Segment orders by payment type (e.g., Stripe, Klarna)

Technical Details (For Admins & Developers)

  • The frontend dynamically retrieves available filter options using:
    GET {BASE_URL}/bo/sales/filters/orders/attributes

  • The backend integrates seamlessly with existing filter logic — just pass the selected filters in the expected format

Why This Matters

  • Faster order searches and reduced admin time

  • Improved operational workflows for support and logistics teams

  • Easier reporting and analytics based on specific order traits

Start using the new filtering tools today by visiting your Order Listing page under the Sales section in your admin dashboard.

Need help? Reach out to support.

29 Apr 2025

Database-Driven Menu Locations

We’ve made key improvements to how navigation menus are managed in HDL Commerce, moving from file-based configuration to a more dynamic, database-driven system. This update improves flexibility, scalability, and long-term maintainability for managing navigation across channels and storefronts.

What’s New

Menu Locations Now in the Database

Navigation menu locations (e.g., Primary Menu, Footer Menu) are now stored in the database rather than configuration files. This allows dynamic updates without code deployment and supports multi-channel setups.

Migration Command for Developers

We’ve introduced a command-line tool to help developers migrate existing configuration-based menus to the new system:

php artisan navigation:location:migrator

This extracts existing paths and titles and stores them in the database — ready for use without code rewrites.

Deprecation Notice

The old method of defining menu locations in configuration.php is now deprecated. It will be removed in a future release. We recommend migrating as soon as possible to ensure future compatibility.

Technical Enhancements (For Developers)

  • Validation Updates: Reserved identifiers such as primary_menu and footer_menu can now be used safely when creating new entries. The system prevents unintended changes to existing reserved identifiers.

  • Centralised Validation: New validation rules are injected directly via the NavigationMenuLocationRequest, ensuring consistent behaviour and improving testability.

  • Scoped Logic Fixes: Channel-specific behaviours are now handled more reliably, reducing unnecessary entries in scoped navigation contexts.

Developer Notes

  • Use the navigation:location:migrator command to migrate existing configurations into the database

  • Test any overridden navigation-related logic in custom projects

  • The core system now queries menu locations directly from the database

If you need help transitioning or want a walkthrough of this update, please reach out to our team or contact support.