> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/trade-and-b2b/shipping/troubleshooting-your-order-cannot-be-shipped-to-the-selected-address-at-b2b-checkout.md).

# Troubleshooting "Your order cannot be shipped to the selected address" at B2B checkout

Fix the Shopify B2B checkout error caused by split shipping and draft order submission mode.

Last verified against Shopify: April 21, 2026

This article explains why a retailer can see `Your order cannot be shipped to the selected address` during Shopify B2B checkout, even when the address is correct.

It also shows the cleanest resolution path Roadmap recommends.

### The error message and when it appears

Retailers usually see this message after they reach shipping in checkout:

> Your order cannot be shipped to the selected address. Review your address to ensure it's correct and try again, or select a different address.

This usually appears when both of these conditions are true:

* the company location uses `Submit all orders as drafts for review`
* the cart contains products from more than one shipping profile

### Why the message is misleading

The address is usually not the problem.

The real issue is shipping rate calculation.

When the cart spans multiple shipping profiles, Shopify needs to calculate shipping separately for each shipment.

That split shipping step is where the draft order flow breaks.

### The root cause

Shopify uses split shipping when a cart contains products from more than one shipping profile.

A common example is a cart that mixes standard parcel items with oversized freight items.

In a normal checkout flow, Shopify can split those shipments and calculate rates separately.

In the B2B draft order flow, Shopify does not support that split shipping step.

Shopify states this directly:

> Split shipping in checkout can't be applied to B2B checkouts that require orders to be placed as draft orders.

<https://help.shopify.com/en/manual/checkout-settings/split-shipping>

The result is a silent rate calculation failure, followed by an address error that points your team in the wrong direction.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FWjeEVnWbXfHgH9jpQxgH%2FScreenshot%202026-04-22%20at%2012.22.48%E2%80%AFPM.png?alt=media&amp;token=2d8b79dc-d490-4411-b72c-99a0d4d807e7" alt=""><figcaption></figcaption></figure>

### Resolution

Roadmap recommends switching that company location to `Automatically submit orders`.

Then use payment terms to control trust and payment timing instead.

{% stepper %}
{% step %}

#### Change the company location setting

In Shopify, open `Customers → Companies`, open the company location, and change `Order submission` to `Automatically submit orders`.
{% endstep %}

{% step %}

#### Assign the right payment terms

Use `Due on fulfillment` for new or untrusted accounts, or a `Net` term for established retailers.
{% endstep %}

{% step %}

#### Retest with a mixed profile cart

Build a cart that includes items from each shipping profile and run checkout again with the same retailer account.
{% endstep %}
{% endstepper %}

This keeps your shipping profiles intact.

It also avoids collapsing freight and standard products into one profile just to work around the draft order limit.

{% hint style="warning" %}
Do not remove separate shipping profiles unless your pricing model genuinely allows it.

If freight needs different rating logic, keep the profiles separate and change the order submission mode instead.
{% endhint %}

### If you still need draft review behaviour

Some merchants still want a manual review path for edge cases.

Roadmap usually suggests one of these alternatives instead of making every company location use draft review:

* segment retailers into separate catalogues or company setups, then reserve draft review for the small group that truly needs it
* create draft orders in admin for one off manual review scenarios, instead of forcing every self serve checkout through that path

These options keep the main B2B flow fast, while preserving extra control where it is actually needed.

### Related articles

* [Choosing your B2B company checkout settings](/trade-and-b2b/checkout-and-payment/choosing-your-b2b-company-checkout-settings.md), for the wider decision between automatic submission and draft review.
* [Multiple shipping profiles in B2B: what to know](/trade-and-b2b/shipping/multiple-shipping-profiles-in-b2b-what-to-know.md), for the split shipping behaviour behind this error.
* [Handling custom payment terms like "20th of the month following"](/trade-and-b2b/checkout-and-payment/handling-custom-payment-terms-like-20th-of-the-month-following.md), for the trust based payment setup Roadmap recommends as the replacement.

Need a hand? Contact us in the Roadmap app via Intercom.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roadmap.so/trade-and-b2b/shipping/troubleshooting-your-order-cannot-be-shipped-to-the-selected-address-at-b2b-checkout.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
