Carriers

Create reusable shipping-provider definitions that Shipping Methods can reference.

Carriers identify the delivery providers that shipping methods can represent to customers and staff.

What this feature is for

Carriers are reusable shipping-provider identities. They let multiple Shipping Methods share a recognizable delivery provider without duplicating carrier details in each method.

A practical way to use it

Create the carrier/provider that will deliver orders.
Create Shipping Methods that reference the carrier where the form supports it.
Set method-specific cost/service rules there rather than creating a separate carrier for every price.
Test the customer-facing shipping labels at checkout.

How it connects to other features

Carriers become operational through Shipping Methods. Zones determine where methods are eligible; the checkout address and cart determine which eligible method is finally shown.

What to expect after changes

Editing a shared carrier can affect several shipping methods. Deleting one should be preceded by a review of methods that reference it.

Carrier vs. Shipping Method

A Carrier represents the provider/service integration identity—such as its name, code, API/account details, endpoint, service code, and sandbox state. A Shipping Method represents the option offered/calculated for an order and contains the destination/rate rules. Keeping them separate means several shipping methods can share one carrier definition.

Recommended setup

Create the Carrier first and give it a recognizable Name and Code.
Set Priority if the carrier order matters in the administration workflow.
Add a Description that helps staff distinguish similar services.
Enter only the provider configuration your carrier requires: API Key, Account Number, Endpoint, and/or Service Code.
Enable Sandbox while testing when the provider supports a test environment, and keep Is Active off until the connection is ready for live use.
Create the related Shipping Method and connect it to the carrier along with the destination/rate rules that should be offered at checkout.
Test with a customer address that should qualify for that Shipping Method before enabling it broadly.

Carrier fields

Field	Purpose
Name	Staff-facing name for the carrier.
Code	Short identifier used to distinguish the carrier in operational/configuration screens.
Priority	Controls carrier ordering where the administration uses priority.
Description	Internal explanation of the carrier/service.
API Key	Credential used by a carrier integration when required.
Account Number	Merchant/shipping account identifier when required by the provider.
Endpoint	Provider service endpoint used by the carrier configuration.
Service Code	Provider-specific service/product code when needed.
Sandbox	Uses the test/sandbox mode for providers that support it.
Is Active	Controls whether the carrier is treated as active for related configuration.

Protect carrier credentials

API keys and account details are private operational credentials. Do not include them in documentation screenshots, support screenshots, or public issue reports.

Using the carrier list

Search by Name or Code when staff need to find a specific provider. The list shows the carrier name/code and Status; use View to review the saved definition, Edit to change shared carrier details, and Delete only after checking whether Shipping Methods still depend on it.

What happens after you save

Changing a carrier changes the shared provider definition used by related shipping configuration. It does not by itself decide which customer address qualifies or what shipping fee is charged—that logic belongs to Shipping Methods, Zones, Store Settings, and the order address.

Shipping Methods · Zones · Store Settings