How to set different Shopify shipping rates by warehouse origin

Updated August 13, 2026 · SMART Shipping Rates (E-TRADE PARTNER)

You can set different Shopify shipping rates by warehouse origin by matching the fulfillment location Shopify sends on the carrier-service request. SMART Shipping Rates & Rules uses Origin country, Origin postal code, Origin address line 1, and Origin address line 2 for the shipping FROM address. Destination shipping zones still handle the customer address. Calculated origin rates need Shopify Carrier Service.

Multi-warehouse stores have two addresses on every rate request: where the order is going, and where it is packing. A New Jersey warehouse can reach New York cheaply. The same cart fulfilled from Nevada should not inherit that East Coast price. Native destination zones only see the customer.

Origin conditions are for that packing location. They do not replace destination targeting. Use both: a zone for the customer, then an origin condition so each warehouse prices its own request.

Why origin rates matter

• They recover outbound cost when two warehouses serve the same destination at different cost.
• They keep East Coast rates from applying to West Coast fulfillment, and the reverse.
• They make the packing location visible in the rule, instead of burying it in a destination-only table.
• They work with destination zones, so customer geography and warehouse geography stay separate.

What origin conditions actually read

Origin fields come from the origin object on Shopify's carrier-service request: the shipping FROM address of the location Shopify selected for that group of line items. They are not customer address fields.

Keep destination matching on the zone (country, city, postal code). Origin decides which warehouse's price table applies to that request. See Shipping rates and zones.

What Shopify can and cannot do natively

Shopify locations and delivery profiles attach products to packing sites. That helps inventory routing. Native shipping settings still price mainly by destination. They do not give you a checkout table that says "if this warehouse packed it, charge this".

The split-cart limit (read this before you build)

When a cart splits across fulfillment locations or delivery profiles, Shopify sends one Carrier Service request per group. Each request contains only that group's line items. Shopify often sums the rates it gets back. SMART cannot see the whole cart in that case, and it cannot silently un-double shipping. There is no wizard in the app that stops Shopify from summing those groups.

Practical mitigation: keep products that should share one rate in one delivery profile and one location group when that is operationally honest. Use origin conditions when different warehouses should price differently for their own request. Review grouping in Delivery profiles. If summing is correct (two real shipments), leave the split in place.

Setup steps in SMART Shipping Rates & Rules

1. In Shopify admin, confirm each packing site is a location with a complete address (country, postal code, and street as you want to match them).
2. Open SMART Shipping Rates & Rules, then Shipping rates. Confirm Carrier Service is available. Zone creation is disabled when it is not.
3. Create one calculated rate per warehouse you need to price, inside the destination zone the customer should see.
4. Add Origin country, Origin postal code, Origin address line 1, or Origin address line 2 so the rate only matches that warehouse's FROM address.
5. Leave customer targeting on the zone. Do not put the warehouse ZIP in destination postal codes.
6. Open Checkout simulator, set Ship from location to that warehouse, and run the same destination cart from each origin. Then place one real checkout Shopify would fulfill from that location.
7. If a live price looks wrong, open Activity log (entries are kept up to 48 hours) and check which origin Shopify sent.

Worked example: US East vs US West warehouses

A US brand packs from a New Jersey warehouse and a Nevada warehouse. Both sell nationwide. Standard ground to the East should be cheaper when New Jersey packs. Standard ground to the West should be cheaper when Nevada packs. Overnight can stay one national table.

1. Create the East standard calculated rate in Shipping rates with destination targeting for East postcodes.
2. Add Origin postal code (or Origin address line 1) for the New Jersey location.
3. Repeat for the West warehouse with the Nevada origin and West destination group.
4. Create the cross-country rates the same way: far destination plus the origin that is actually packing.
5. In Checkout simulator, set Ship from location to New Jersey, then to Nevada, and confirm the $8 vs $14 split for the same customer ZIP.

If two origin rates could match the same request, review Settings → Multiple rates, or tag the components and blend them in Combined rates. Blending only works inside one Carrier Service request. It does not merge Shopify's summed split-cart total. See rate blending.

Tips for multi-warehouse rates

• Copy the location address from Shopify settings. A missing unit on Origin address line 2 is a common miss.
• Name internal rates after the warehouse your ops team uses, then set a simple customer-facing method name.
• Test a cart Shopify would actually assign to that location. Inventory routing still decides origin.
• Use Delivery profiles to keep products that should share one rate in one profile and location group when that is honest.
• Pair origin rules with destination zones instead of duplicating every customer ZIP on the origin condition.
• Confirm calculated prices in the Checkout simulator before a live checkout.

How origin and destination should stay separate

A destination zone answers where the order is going. An origin condition answers which warehouse packed this request. Start with the destination zone, then add the smallest origin condition that uniquely identifies the location. If two warehouses share a postal code, use Origin address line 1 or Origin address line 2 instead of forcing a ZIP match that both would pass.

Frequently asked questions