Your organisation's custom fields — the fields you use to tag shipment data, such as customer, lane_id, internal_ref_number, or goods_weight — can now be used as filters in both the Command Center and the Logistics KPI dashboard. This lets you slice shipment visibility and KPI data by the dimensions that matter to your operations, without involving engineering or Portcast.

You control which custom fields are available as filters directly from your settings, and any user in your organisation can manage them.

Managing which fields are available for filtering

Custom fields are managed on the Custom Fields settings page (previously named "Org Settings"). Each custom field now has a Filter toggle:

• Turn the Filter toggle on to make that field available as a filter in the Command Center and Logistics KPI. It appears in the filter bar immediately.
• Turn the Filter toggle off to remove it from the filter bar in both views. Any active filters using that field are cleared gracefully — you won't see an error.

By default, custom fields have the Filter toggle off, including newly created fields, so you choose exactly which fields appear as filters.

To enable a custom field for filtering:

1. Go to the Custom Fields settings page.
2. Find the field you want to make filterable.
3. Switch its Filter toggle on.

A field can be active for data entry or not, independently of whether it is available as a filter — so you can keep filtering enabled on a field even if it is no longer used for new data.

Fields that can't be filtered

A couple of field types are not eligible for filtering, and their Filter toggle appears greyed out:

• Custom Journey fields are not yet supported for filtering.
• Fields that have sub-fields configured cannot be used as filters.

In both cases, hovering over the disabled toggle explains why.

Filtering in the Command Center and Logistics KPI

Once a field has its Filter toggle on, it appears in the filter bar of both the Command Center and the Logistics KPI. If no custom fields are enabled for filtering, no custom field section appears in the filter bar.

The filter input matches the field's type: