Location Custom Fields let you define reusable, Location-scoped fields in techSHIP and make them available to supported workflows without entering raw field syntax.

This guide covers how you create, edit, type, and remove customer-managed Custom Fields, how Host System-declared fields behave, and how each field definition relates to values stored on Orders and Lines.

Understand Location Custom Fields

A Custom Field definition belongs to a Location, while the value associated with that field belongs to the Order or Line being processed. Defining a field does not automatically create or populate a value on every Order; it registers the field so you can use it in supported techSHIP workflows.

A registered Custom Field can come from your Location configuration or from the assigned Host System. You can manage customer-created definitions when you have the required permissions, while Host System-declared definitions are system-managed and read-only. To check your permissions, see: 📄 techSHIP User Permissions Structure [Information].

Access Custom Fields

Open Settings > My Location > Custom Fields.

If you manage Locations with Organization Admin access, you can also open the applicable Location from Locations and select the Custom Fields tab for that Location.

Understand Custom Field Properties

The Custom Fields grid uses the following properties:

When you create or edit a customer-managed field, follow these validation rules:

• Code is required and accepts letters A-Z or a-z and digits 0-9 only. Do not use spaces, punctuation, accented letters, or other special characters.

• Display Name is required and accepts letters, digits, and ordinary spaces. It must contain at least one letter or digit.

• Exact duplicate Codes are rejected. Customer-managed Codes that differ only by capitalization can coexist, so Cost and cost are treated as distinct customer definitions.

• Type can be String or Number. New customer-managed fields default to String.

Use String for text-oriented values. Choose Number when you need supported numeric rule capabilities, including numeric ordering conditions and native Add to or Subtract from authoring.

Manage Customer-Managed Custom Fields

Add a Custom Field

1. Open the applicable Custom Fields tab for the Location.

2. Select Add + to open the Add Custom Field dialog.

3. Enter the following fields and click Save:

• Enter a stable identifier in Code.

• Enter the friendly label you want to see in supported selectors in Display Name.

• Select String or Number in Type.

4. Select the page-level Saveaction to persist the Location configuration.

You have now registered the Custom Field for this Location.

Reopen the relevant rule editor or supported field selector when you are ready to use it.

Edit a Custom Field

In the Custom Fields grid, locate the customer-managed definition that you want to change and:

1. Under Actions, select the Edit pencil icon.

2. Update the applicable Code, Display Name, or Type and click Save.

3. Select the page-level Save action to persist the updated Location configuration.

You have now updated the field definition. If you changed Code, review any workflows that previously referenced the old Code before continuing to use the field.

Delete a Custom Field

In the Custom Fields grid, locate the customer-managed definition that you want to remove and:

1. Under Actions, select the Delete trash icon and confirm the deletion.

2. Select the page-level Save action to persist the updated Location configuration.

You have now removed the Custom Field definition from the Location configuration. Review any rules or other workflows that referenced that field and update them as needed.

Work with Host System-Declared Custom Fields

Some Host System integrations can automatically declare Custom Fields that they support. These definitions are added to the Location's registered field set without requiring you to create them manually.

A Host System-declared field is read-only at the definition level. You can identify these fields in the grid because their Type indicates that they are declared by the applicable Host System, and they do not provide the normal customer Edit or Delete actions.

For example, a Host System could declare Materials and Handling, with both definitions using the Number type.

If you configure a customer-managed Code that matches a Host System-declared Code without regard to capitalization, the Host System definition takes precedence in the registered field list. Your customer-managed definition is not automatically deleted or overwritten.

If you change or remove the assigned Host System, the set of Host System-declared fields can change accordingly. Your customer-managed definitions remain configured, and values already stored on Orders are not automatically deleted.

Use Registered Fields in Supported Workflows

After you save a customer-managed field, reopen the applicable editor or selector to load the latest registered Custom Fields. Supported Field selectors display the friendly Display Name, while the saved rule continues to reference the underlying Code.

A Number definition can make numeric capabilities available in supported rule editors, while a String definition remains available for text-oriented behavior. For detailed Action and Condition behavior, see the Next Steps section below.

Understand Custom Field Value Scope

A Location Custom Field definition is shared at the Location level, but the value used during processing depends on the applicable Order Management Rule level.

This distinction is important when you configure Package or Line iterations. A Package iteration can repeatedly work with the same Order-level Custom Field, while a Line workflow can address the value stored for the current Line.

Work with Legacy Custom Fields

Existing Custom Field definitions created before the structured editor remain available in the Custom Fields grid. Definitions without explicit type information continue to use String until you change their Type.

Older definitions can also retain legacy Codes or labels that do not meet the validation rules for newly entered fields. If you edit one of those definitions, you may need to update it so that the edited values comply with the current Code and Display Name validation rules.

When you finish editing an existing definition, select the page-level Save action to persist the configuration. You can then reopen the relevant workflow to use the updated registered field.

Next Steps

To use registered fields in Rule Set Conditions and Actions, continue with 📄 What's New in Order Management Rules (OMR) for Rule Sets in techSHIP [Guide].

For a practical example that uses a numeric Custom Field to accumulate packaging costs, continue with 📄 Setting up Order Management Rules: Accumulating Packaging Costs with Custom Fields [Guide].