Skip to main content

Custom Product Attributes

Overview​

Custom Product Attributes allow your organization to define additional dimensions used to separate, track, and operate on inventory.

Attributes can represent concepts such as:

  • Lot codes
  • Expiry dates
  • Batch numbers
  • Weights
  • Regulatory identifiers
  • Any other customer- or warehouse-specific classification

Once created, attributes become globally available to all products and customers within the organization.

Why custom attributes exist​

Not all inventory can be treated as interchangeable.

Custom attributes allow you to:

  • Separate inventory that shares the same SKU
  • Enforce operational controls (expiry, recall, quarantine)
  • Improve pick accuracy
  • Enable advanced filtering and search
  • Preserve traceability across inbound and outbound workflows

Attributes are commonly used in regulated, perishable, or serialized environments.

Attribute scope and lifecycle​

Organization-level definition​

Custom attributes are defined once at the organization level.

  • Available to all customers
  • Available across all warehouses
  • Reusable across all products

Attributes are not product-specific by default.

Product-level enablement​

Each attribute must be explicitly enabled on a product (SKU).

  • Disabled attributes have no operational impact
  • Enabled attributes become required or selectable during inventory operations

This allows each SKU to use only the attributes it needs.

Supported attribute types​

String​

Used for free-form identifiers such as:

  • Lot codes
  • Batch numbers
  • Serial groups
  • Text-based classifications

Date​

Used for time-based controls such as:

  • Expiry dates
  • Manufacture dates
  • Compliance deadlines

Date attributes support sorting, filtering, and operational enforcement.

Where attributes are used​

Inventory directory​

Enabled attributes appear as:

  • Filterable columns
  • Searchable fields
  • Grouping options

This allows users to quickly locate inventory by attribute value.

Receiving​

When receiving inventory for a SKU with enabled attributes:

  • Attribute values must be provided
  • Inventory is segmented by attribute combination

This ensures accurate downstream handling.

Shipping orders​

During shipping order creation (Step 1):

  • Attribute values can be selected to target specific inventory
  • Prevents shipping incorrect lots or expired product

LPNs and palletization​

Attributes are stored at the inventory level and carried through:

  • LPN assignment
  • Pallet movements
  • Transfers between warehouses

This preserves attribute integrity throughout the lifecycle.

Operational behavior​

Inventory with different attribute values is treated as distinct stock, even if the SKU is the same.

This affects:

  • Available quantity calculations
  • Pick logic
  • Reservation behavior
  • Quarantine enforcement
  • Transfer eligibility

Governance and best practices​

⚠️ Custom attributes introduce additional complexity.

Recommended practices:

  • Create attributes only when operationally required
  • Use consistent naming conventions
  • Prefer Date attributes for time-sensitive controls
  • Avoid creating overlapping or redundant attributes

Once attributes are actively used, removing or renaming them can impact historical data.

Who can manage custom attributes​

Warehouse users​

  • Create new attributes
  • Edit attribute names
  • Define data types

Administrators​

  • Control access to attribute management
  • Enforce organizational standards

Customers cannot create attributes but may use enabled attributes on their products.

Common use cases​

  • Expiry-controlled food or supplements
  • Lot-controlled manufacturing inventory
  • Recall-ready consumer goods
  • Batch-based quality inspection
  • Client-specific inventory segmentation