Custom Fields - Example Workflows

Below are some examples to help you design Custom Fields that support your team’s operational workflows. For step-by-step instructions and screenshots, refer to the related articles on setting up custom fields and using them on the container dashboard.

Example 1: ERP/TMS Sync

• Create shipment-level fields:

  • ERP shipment ID (Text)

  • Customer reference number (Text)

• Include these in CSV or API when creating tracking requests.

• Use exports, API, or webhooks from Terminal49 to maintain your ERP/TMS in sync without separate mapping spreadsheets.

Example 2: Exceptions & Issue Tracking

• Create a container-level multi-select field such as Container issues.

  • Name: Container issue

  • Type: Multi-select

  • Options: Customs hold, Hot ports, Destination change, etc.

• Add this field as a column on the Container Dashboard

• Create a view filtering on key issues (e.g., Customs hold, Hot ports).

• Save and share the view for real-time, team-wide visibility as 'Containers with issues'

Example 3: Operational Notes / Next Steps

• Create container-level fields:

  • Next action date (date)

  • Owner (Select)

  • Status (Select)

• Update via inline editing as containers move through your process.

• Share views with warehouse, customer service, or sales teams.

These examples show common ways teams use Custom Fields to store your own structured, business-specific data—like ERP IDs, workflow details, and internal notes—directly on shipments and containers so your teams and systems stay aligned and up to date.

If you need help with Custom Fields or have any other questions, the fastest way to get assistance is through our in-app chat. You can also reach us at support@terminal49.com.