Ship Vias

Summary Information
Menu Path:	Customers — Ship Vias
Required Feature(s):	Customers

Navigation: Customers → Ship Vias

The Ship Vias module allows administrators to define and manage shipping method codes used to specify how orders are delivered to customers. These codes provide a structured way to identify and assign transportation or delivery carriers to customer transactions.

Ship vias help maintain consistency in order fulfillment workflows, improve reporting accuracy, and ensure that the correct shipping method is applied uniformly across customer records and transactions.

Purpose of Ship Vias

Ship Vias are used to:

• Provide standardized shipping method codes for customer transactions and orders
• Define the carrier or delivery method associated with each shipment
• Support reporting and filtering by shipping method type
• Maintain consistent shipping assignments across stores and operational workflows

Each ship via represents a predefined delivery method that can be assigned to a customer record or transaction.

Creating or Editing a Ship Via

To create or modify a ship via:

1. Navigate to Customers → Ship Vias.
2. Click the + button to create a new ship via, or choose an existing ship via to edit.

1. Enter the required information.
2. Click Save to apply the changes.

Available Fields

Field	Description	Field Behavior
Code	Unique identifier used to represent the ship via within the system.	Required. The value must be unique and is used internally to reference the shipping method across customer records and transactions. Once assigned to customer records or orders, changing this value is not recommended as it may affect existing references.
Description	A descriptive explanation of the ship via to help administrators and users understand its delivery method.	Optional. Displayed in the administrative interface to clarify what carrier or delivery service the code represents when assigning shipping methods.

Operational Considerations

• Ship via codes should follow a consistent naming convention to maintain clarity across the system.
• Codes should remain stable after creation to preserve data integrity in existing customer records and transaction history.
• Administrators should avoid creating duplicate codes that represent the same shipping method or carrier.
• Descriptions should clearly indicate the carrier name or delivery service associated with each ship via code.

Example

Code	Description
LOCAL	Local Delivery Service
UPS	UPS Ground Shipping
FEDEX	FedEx Express Delivery

In this example, each code represents a distinct shipping method that can be assigned to customer records or transactions to identify the appropriate carrier or delivery service.

---