---
title: "Override Customer Contact Source in Dynamic Ship"
app: "Dynamic Ship"
section: "Set up"
last_updated: "2026-06-17"
url: "https://insight-works.com/kb/dynamic-ship/override-customer-contact-source-in-dynamic-ship/"
---

# Override Customer Contact Source in Dynamic Ship

Available in Dynamic Ship 2.7 and newer, you can use a new feature that allows you to override the source of a sales document’s contact information for the shipment. The contact information includes the contact’s name, email, and phone number.

You can configure this feature globally on the _Dynamic Ship Setup_ page or customer specific on the _Dynamic Ship Customer Options_ page in Business Central. There are three override configurations in the setup page, the source to pull the information from, the fields to override, and how to respect a sales order’s ship-to code.

 Note: When updating from Dynamic Ship 2.6 or older, the settings are automatically configured to mimic the previous behavior to allow for a smooth transition.

### Default Behavior

The default source for the contact information is determined by the following:

- If the source document has the _Ship-To Code_ defined: All the contact information is pulled from the related _Ship-To Address_
- If the source document has the _Ship-To Code_ set to “Default” or “Custom”: The phone number is pulled from the sell-to _Customer_, and the contact’s name and phone number are pulled from the source document’s _Ship-to Contact_and _Ship-to Phone No._field.

 Note: Business Central 24 or less does not have a _Ship-to Phone No._ field in the Sales Order, in these instances the phone number is pulled from the sell-to _Customer_.

### Customer Contact Override Fields

![](/wp-content/uploads/kb-legacy/Dynamic-Ship-Setup-Override-Fields-800x334.png)

#### Override Source

The _Override Source_ field is located on the _Dynamic Ship Setup_ and the _Dynamic Ship Customer Options_ pages in Business Central. The _Override Source_ field determines where the override contact information is pulled from. Each option represents a table.

For example: _Sell-To Contact_ pulls information from the _Sell-To Contact_ Card. This configuration works alongside the _Override Fields_ configuration.

 Note: _Override Source_ replaces the configuration “Tracking E-mail Customer Src.” for Dynamic Ship Setup and the “Customer E-mail Source” for the Customer Option.

#### Override Fields

The _Override Fields_ is located on the _Dynamic Ship Setup_ page in Business Central. The _Override Fields_ configuration determines which part of the contact information is overridden with the _Override Source_ field. This configuration affects both the _Dynamic Ship Setup_ and the _Dynamic Ship Customer Options_ pages.

The _Override Fields_ options are:

- E-Mail
- E-Mail & Phone
- E-Mail & Phone & Name

#### Override When Using Ship-To Code

The _Override When Using Ship-To Code_ field is located on the _Dynamic Ship Setup_ page in Business Central. The _Override When Using Ship-To Code_ field determines the importance level of the override configurations. If you review the Default Behavior section, the source document’s _Ship-To Code_is the primary source.

When _Override When Using Ship-To Code_ is set to “Do Not Override”, it overrides the contact information when there is no _Ship-To Code_ on the source document.

When _Override When Using Ship-To Code_ is set to “Allow Override”, it allows the related _Override Source_ and _Override Fields_ to be the primary source (e.g., if the source document has a _Ship-To Code,_its contact information is overridden). This configuration affects both the _Dynamic Ship Setup_ and the _Dynamic Ship Customer Options_ pages.

### Examples

#### Sales Order

Here is a sales order, the source document, being shipped. Each of the columns below are tables associated to the sales order, and the row is the record that relates to the order.

| **Sales Order** | **Ship-To Address** | **Customer** | **Sell-To Contact** | **Bill-To Customer** | **Bill-To** **Contact** |
| --- | --- | --- | --- | --- | --- |
| Sell-To Contact: Jim Sell-To Email: Ji\*@\*.com Sell-To Phone: JIM-1111 Ship-To Code: ‘’ |  | Contact: Bob E-Mail: Bo\*@\*.com Phone No.: Bob-3333 | Contact: Sue E-Mail: Su\*@\*.com Phone No.: Sue-4444 | Contact: Jon E-Mail: Jo\*@\*.com Phone No.: Jon-5555 | Contact: Cat E-Mail: Ca\*@\*.com Phone No.: Cat-6666 |

The following is what Dynamic Ship uses with the following configurations:

**Configuration 1**

| **Field** | **Setting** |
| --- | --- |
| Override Source | Source Document |
| Override Fields | E-Mail, Phone, and Name |
| Override When Using Ship-To Code | Do Not Override |

| **Result** |
| --- |
| Contact = Jim, Email = Ji\*@\*.com, Phone No = Jim-1111 |

The contact information is pulled from the source document (the Sales Order) because this order has no ship-to code. The _Override Source_ is set to Source Document, and all three contact fields were set via the _Override Fields_ configuration.

**Configuration 2**

| **Field** | **Setting** |
| --- | --- |
| Override Source | Default |
| Override Fields | E-Mail & Phone & Name |
| Override When Using Ship-To Code | Do Not Override |

| **Result** |
| --- |
| Contact = Jim, Email = Bo\*@\*.com, Phone No = Bob-3333 |

The information is using the base Dynamic Ship behavior as the _Override Source_ is set to Default. This is the only scenario where the configuration Override Fields and Override When Using Ship-To Code are irrelevant.

#### Sales Order with Ship-To Code

Here is a sales order, the source document, being shipped using a ship-to code. Each of the columns below are tables associated to sales order, and the row is the record that relates to the order.

| **Sales Order** | **Ship-To Address** | **Customer** | **Sell-To Contact** | **Bill-To Customer** | **Bill-To** **Contact** |
| --- | --- | --- | --- | --- | --- |
| Sell-To Contact: Jim Sell-To Email: Ji\*@\*.com Sell-To Phone: JIM-1111 Ship-To Code = LA | Name: Mary E-mail: Ma\*\*@\*.com Phone No.: Mary-2222 Code = LA | Contact: Bob E-Mail: Bo\*@\*.com Phone No.: Bob-3333 | Contact: Sue E-Mail: Su\*@\*.com Phone No.: Sue-4444 | Contact: Bill E-Mail: Bi\*\*@\*.com Phone No.: Bill-5555 | Contact: Cat E-Mail: Ca\*@\*.com Phone No.: Cat-6666 |

Here is what Dynamic Ship uses with the following configurations:

**Configuration 1**

| **Field** | **Setting** |
| --- | --- |
| Override Source | Sell-To Contact |
| Override Fields | E-Mail & Phone & Name |
| Override When Using Ship-To Code | Do Not Override |

| **Result** |
| --- |
| Contact = Mary, Email = Ma\*\*@\*.com, Phone No = Mary-2222 |

None of the contact information was pulled from the Sell-To Contact record (Sue) is because this order had a Ship-To Code with the configuration set to not override in this situation.

**Configuration 2**

| **Field** | **Setting** |
| --- | --- |
| Override Source | Bill-To Customer |
| Override Fields | E-Mail & Phone |
| Override When Using Ship-To Code | Allow Override |

| **Result** |
| --- |
| Contact = Mary, Email = Bi\*\*@\*.com, Phone No = Bill-2222 |

The contact information has been overridden with the Bill-To Customer. Mary is still the contact because only E-mail & Phone are overridden; the name continues to use the default Dynamic Ship behavior.

 Note: The above examples show extreme contrast in contact information when most of these fields are normally in sync. For example, the Sales Order’s _Sell-To Contact_ field is typically the same as the Customer Card’s _Contact_.
