> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/testing_vision_sales_outbound_requests.md).

# Testing Vision Sales Outbound Requests

Test outbound Vision requests end-to-end before going live.

Before going live with Vision sales order integration, you will need to complete a testing phase with Ontech.

For further details see the following articles:

* Third Party Warehouse Integration
* Vision outbound requests
* [Vision Testing Inbound API documentation](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/843907075/Testing+Inbound+EDI)
* Technical notes on the data required by Vision can be found here: [Vision SO XML Structure](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/933626253/SO+XML+Structure).

The testing phase consists of the following 4 stages.

{% stepper %}
{% step %}

### Pre-information form and initial test file

{% endstep %}

{% step %}

### Real data checks (bulk testing)

{% endstep %}

{% step %}

### API testing

{% endstep %}

{% step %}

### Agreement to go live

{% endstep %}
{% endstepper %}

{% hint style="info" %}
Note that for stages 1 and 2 files will be sent via email so setting up the communication engine isn't required until stage 3.
{% endhint %}

### Stage 1 - Pre-information form and initial test files

The Sales Orders pre-information form can be found here in the [Step by Step Guide to Testing](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4603019296/Main+Testing+Process#Step-by-Step-Guide-to-Testing) information page.

In the Delivery Options section on the final page, if you are not going to use Service Codes, please say that the Service Codes section of the file will still appear in the example files sent, otherwise Ontech will question this with you.

You will need to send some test files with your pre-information form. These will include one of each order type you have selected on the pre-information questionnaire. For more information and details of what Ontech require at this stage see [Stage 1](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4603019296/Main+Testing+Process#Stage-1---Initial-Check).

{% hint style="info" %}
Note

Before testing any orders you will need to add AWRS numbers to your customer records. See [AWRS Numbers](/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#awrs) for more information.
{% endhint %}

<table><thead><tr><th width="216.66668701171875">Type</th><th width="82.3333740234375">Code</th><th>Ontech/Bevica Information</th></tr></thead><tbody><tr><td>GB Duty Paid</td><td>P</td><td><strong>Bevica Instructions:</strong> Create a Duty Paid sales order.</td></tr><tr><td>GB Underbond</td><td>U</td><td><p><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Duty Free Movement Type and Customer Deferment No. fields are blank.</p><p><strong>Pay Customs Duty:</strong><br>All duty free orders are defaulted as Pay Customs Duty = No. If you would like to set this to Yes on the Vision outbound request file, as well as setting the Duty Status to DUTY FREE and leaving the Customer Deferment No. field blank, tick the Pay Customs Duty flag on the ship-to address. See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#pay-customs-duty">Pay Customs Duty</a>.</p></td></tr><tr><td>Export (within the EU/EC)</td><td>E</td><td><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Duty Free Movement Type is set to Export. Populate the Ship-to Country/Region Code with a country code where the EU Country/Region Code is populated. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#export-orders">Export Orders</a>.</td></tr><tr><td>Exports (outside of the EU/EC)</td><td>X</td><td><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Duty Free Movement Type is set to Export. Populate the Ship-to Country/Region Code with a country code where the EU Country/Region Code is blank. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#export-orders">Export Orders</a>.</td></tr><tr><td>Northern Ireland Duty Paid</td><td>N</td><td><strong>Bevica Instructions:</strong> Create a sales order where the Ship-to Postcode starts with BT. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#export-orders-to-northern-ireland-ni">Export Orders to Northern Ireland</a>.</td></tr><tr><td>Northern Ireland Underbond</td><td>K</td><td><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Ship-to Postcode starts with BT. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#export-orders-to-northern-ireland-ni">Export Orders to Northern Ireland</a>.</td></tr><tr><td>Diplomatic</td><td>D</td><td><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Duty Free Movement Type is set to Diplomatic Privilege. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#duty-free-deliveries">Duty Free deliveries</a>, Vision EDI Code = D. Ensure you populate the C426 No. field on the sales order header before the sales order is released.</td></tr><tr><td>NATO or visiting forces</td><td>V</td><td><strong>Bevica Instructions:</strong> Create a sales order with a Duty Free ship-to address where the Duty Free Movement Type is Visiting Forces/NATO. See also <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#duty-free-deliveries">Duty Free deliveries</a>, Vision EDI Code = V. Ensure you populate the C185 No. field on the sales order header before the sales order is released.</td></tr><tr><td>Parcel Carrier Exports</td><td>P</td><td><strong>Ontech Information:</strong> If you send goods out of the UK using a parcel carrier such as TNT, DPD, Fedex duty has to be paid and you would claim this back manually. <strong>Bevica Instructions:</strong> Create a Duty Paid order. Populate the shipping agent code that has the relevant Vision Collection Delivery Area Code and Vision Integrated Parcel Carrier Code.</td></tr><tr><td>Transfers within Warehouse</td><td>T</td><td><p><strong>Ontech Information:</strong> Sending goods from your account to another account at the same warehouse keeper. Special use of the delivery fields is required for this order type. </p><p></p><p><strong>Bevica instructions</strong><br>Sales Orders: Create a ship-to address with the correct duty status and the following fields populated:</p><p>• Name = the receiving stock holding customer's name<br>• Address 1 = the receiving customer's stock holding code<br>• Address 2 = the receiving customer's site code<br>• City = the POST TOWN of the receiving warehouse. Must not be COUNTY.<br>• Postcode = the postcode of the receiving warehouse<br>• Country = the ISO 2 digit country code<br>• Duty Free Movement Type = Vision Transfer<br>• Vision Sub Account Code = populate this with the customer's reserves account code or name if applicable. This will appear on the outbound request as Delivery Address 3 if the Reserve Sub-Account Support field on the warehouse integration record is set.</p><p></p><p>See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#duty-free-deliveries">Duty Free deliveries</a> where Vision EDI Code = T, and <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#vision-inter-whse-and-account-transfers">Vision Inter-Whse Transfers</a> for further details of orders being sent to another Vision warehouse within the same warehouse group.</p><p></p><p>Transfer Orders: On the Transfer-to location, populate the Duty Free Movement Type field with Vision Transfer. When the outbound request is generated, 'Address 1' and 'Address 2' fields will be populated with the 'to' location's Vision Customer and Site codes.<br></p><p><strong>Sales into paid reserves</strong><br>You need to ensure the <strong>Reserve Sub-Account Support</strong> field on the warehouse integration setup record is set if you want to send sales into reserves sales orders to the warehouse.<br>For sales into paid reserves, you will need to populate the following fields on the ship-to address:<br>• Name = the receiving stock holding customer's name<br>• Address 1 = the receiving customer's stock holding code. This is the same as the Customer Code for the relevant warehouse in Warehouse Integration Setup<br>• Address 2 = the receiving customer's site code. This is the same as the Site Code for the relevant warehouse in Warehouse Integration Setup<br>• Vision Sub Account Code on the ship-to address = the customer's reserves account code or name. This will appear on the outbound request as Delivery Address 3. If this is blank, Delivery Address 3 will be populated with the sell-to customer number.<br>• City = the POST TOWN of the receiving warehouse. Must not be COUNTY.<br>• Postcode = the postcode of the receiving warehouse<br>• Country = the ISO 2 digit country code<br>• Duty Free Movement Type = Vision Transfer</p><p></p><p><strong>Information on Delivery Address 3 from the Vision Spec</strong>: If the customer uses Reserves customer codes this field should contain the reserves account code or name if not known then leave blank.</p><p></p><p>See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#sales-into-paid-reserve-or-a-reserve-sub-account-with-another-company">Sales into Paid Reserves</a> for details of orders with 'sale into reserves' item lines.</p></td></tr><tr><td>Duty Transfer Orders</td><td>Q</td><td><p><strong>Ontech Instructions</strong><br>This is another form of Type T order where you can transfer stock from your holdings to another account and in doing so you can pay the duties on the stock.<br><em><strong>Note that you must check with your warehouse before sending 'Q' orders as not all warehouses offer this service. Bevica will turn off this functionality by default, to enable 'Q' type orders this will need to be turned on in you Warehouse Integration Setup in the Outbound tab.</strong></em> </p><p></p><p><strong>Bevica Instructions</strong><br>These are Duty Paid sales orders which have 'Duty Transfer' sales lines where the Duty Free Movement Type is set to Vision Transfer. You must create a sales order with the relevant details:</p><p>• You must use a Ship-to Code with the Duty Free Movement Type set to Vision Transfer and the Duty Code set to DUTY PAID<br>• You must run the 'Get Paid Reserves to Transfer Duty' function to create the sales lines<br>• The Warehouse Integration Setup record must be set to 'Allow 'Q' Type Orders'</p></td></tr><tr><td>GB Duty Deferred</td><td>P</td><td><p><strong>Ontech Information:</strong> Duty paid orders where your receiving customer or another third party (not the warehouse) is paying the duty. <br><strong>Bevica Instructions:</strong> Create a Duty Free ship-to address and leave the Duty Free Movement Type field blank. Populate the Customer Deferment Account on the ship-to address for whoever is paying the duty. </p><p>See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#duty-free-deliveries">Duty Free deliveries</a> Vision EDI Code = P.</p></td></tr></tbody></table>

### Delivery Methods

If you answered Yes to any of the Delivery Methods questions in the pre-information questionnaire, you will be asked to create orders with different **Collection Delivery Areas**. This is controlled by creating different Shipping Agent records and populating the Vision Collection Delivery. If you select Integrated Parcel Carrier, also populate the **Vision Integrated Parcel Carrier Code** field with the relevant code. For more information on the codes to select/populate, see the [Vision Documentation](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/934085044/SO+Code+Lists#E---CollectionDeliveryArea---HO13).

| Vision Collection Delivery Area field in Bevica | Vision Code in the Outbound Request file                                                            |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| 3rd Party Collection                            | COLL                                                                                                |
| 3rd Party Collection - No Signature             | COLLNS                                                                                              |
| OWN Collection                                  | OWN                                                                                                 |
| OWN Collection - No Signature                   | OWNNS                                                                                               |
| Parcel Carrier Collection                       | XCAR                                                                                                |
| Parcel Carrier Collection - No Signature        | XCARNS                                                                                              |
| Integrated Parcel Carrier                       | The relevant PCxx code. Populate this in the Vision Integrated Parcel Carrier Code field in Bevica. |

### Optional Fields 1

You may be asked to create example files with the following information unless you specified on your form that you will not be sending this information.

<table><thead><tr><th width="248">Type</th><th>Bevica Information</th></tr></thead><tbody><tr><td>Contact Name, Phone Number and Email</td><td><p>Populate the Contact Name and Phone Number on the ship-to address record. </p><p></p><p><strong>Contact Name</strong> </p><ul><li>If the Ship-to Code is populated on the sales order, the Contact Name is taken from the Ship-to record. </li><li>If the Ship-to Code is blank the Contact Name is taken from the Sell-to Contact No record. </li><li>If both the Ship-to Code and Sell-to Contact No. record are blank, the Contact Name will be taken from the Primary Contact record on the sell-to customer card. </li></ul><p></p><p><strong>Contact Phone Number</strong> </p><ul><li>If the Ship-to Code is populated on the sales order, the Contact Number is taken from the Ship-to record (Phone Number). </li><li>If the Ship-to Code is blank, the Contact Number is taken from the Sell-to Contact No. record (Phone Number). </li><li>If both the Ship-to Code and Sell-to Contact No. record are blank, the Contact Number will be taken from the Primary Contact record on the sell-to customer card. </li></ul><p><em>Note that Vision require the telephone number to be formatted with the Country Code and without any spaces.</em> </p><p></p><p><strong>Contact Email</strong> - this is only included in the file if the Add Customer Email Address on SOs field on the Warehouse Supplier card is ticked. </p><ul><li>If the Ship-to Code is populated on the sales order, the Contact Email is taken from the Ship-to record. </li><li>If the Ship-to Code is blank, the Contact Email is taken from the Sell-to Contact No. record. </li><li>If both the Ship-to Code and Sell-to Contact No. record are blank, the Contact Email will be taken from the Primary Contact record on the sell-to customer card. </li></ul><p><em>Note that there must only be one email address in the Email field on the relevant record in Bevica otherwise the file will error when sending to Vision.</em> </p><p></p><p><strong>Note</strong>: if you populate the Phone Number you must also populate the Contact Name. Generating an outbound request will error if there is a phone number but no name.</p></td></tr><tr><td>Delivery Instructions</td><td><p>Add a Delivery Instruction comment to the sales order or transfer order. See <a href="/documentation/guides/sales/sales_comments_and_notes.md">Sales Comments and Notes</a> or <a href="/documentation/guides/warehousing-and-logistics/transfer_order_comments_and_notes-1.md">Transfer Order Comments and Notes</a> for more information. The first 120 characters are sent to Vision. If comment text exceeds this limit it will not be shown in full. </p><p></p><p>You can use delivery instructions to reference a customer delivery account number at a warehouse. If it is a sales into reserves use the Vision Sub Account number field on the ship-to address. See Sales into Paid Reserves information above.</p></td></tr><tr><td>Picking Instructions</td><td>Add a Picking Instruction comment to the sales order or transfer order. See <a href="/documentation/guides/sales/sales_comments_and_notes.md">Sales Comments and Notes</a> or <a href="/documentation/guides/warehousing-and-logistics/transfer_order_comments_and_notes-1.md">Transfer Order Comments and Notes</a> for more information. The first 120 characters are sent to Vision. If comment text exceeds this limit it will not be shown in full.</td></tr><tr><td>Booked Date</td><td>Bevica uses the <strong>Whse. Booked/Collection Date</strong> on the sales order header. If this is blank it uses the <strong>Shipment Date</strong> on the sales order header. If both are blank it uses today's date. See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#booking-details">Booking Details</a> for more information.</td></tr><tr><td>Delivery Times</td><td><p>Populate the time slot fields on the customer or the ship-to address record.</p><p>• Slot 1 Start Time<br>• Slot 1 End Time<br>• Slot 2 Start Time<br>• Slot 2 End Time </p><p>See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#booking-details">Booking Details</a> for more information.</p></td></tr><tr><td>Booking Required</td><td>Tick the <strong>Whse Booked Required</strong> field on the sales order header. See <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#booking-details">Booking Details</a> for more information.</td></tr></tbody></table>

### Optional Fields 2

You may be asked to create example files with the following information if you specified on your form that you will be sending this information.

<table><thead><tr><th width="277.33331298828125">Type</th><th>Bevica Information</th></tr></thead><tbody><tr><td>Special Messaging</td><td>You can add a Gift Note comment to the sales order. See <a href="/documentation/guides/sales/sales_comments_and_notes.md">Sales Comments and Notes</a> for more information. You will need to check with your warehouse if this is supported.</td></tr><tr><td>Advanced Special Messaging</td><td>This is not supported in Bevica.</td></tr><tr><td>Delivery Options</td><td>For <code>&#x3C;DO>5</code> Service Codes, see <a href="/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#service-codes">Service Codes</a>. All other <code>&#x3C;DO></code> tags are not supported in Bevica.</td></tr><tr><td>Invoicing Segment</td><td>This is not supported in Bevica.</td></tr><tr><td>Line Options</td><td>This is not supported in Bevica.</td></tr></tbody></table>

### Export Orders

If you are asked to create an [Export order](/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md#export-orders) example when testing with Vision and do not do export orders please speak to them and request not to provide this example. If you need to provide an example export order and you do not use manifests please speak to one of the Bevica team.

### Stage 2 - Real data checks (bulk testing)

Once the files sent in stage 1 have passed the initial checks, you will be asked to send a number of real world examples for the different order types and options selected in your pre-information form. For more information and details of what Ontech will check at this stage see [Stage 2](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4603019296/Main+Testing+Process#Stage-2---Real-Data-Checks).

### Stage 3 - API testing

Ontech will provide access to the main system to allow you to send files through the API. For more information see [Stage 3](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4603019296/Main+Testing+Process#Stage-3---API-Testing).

### Stage 4 - Agreement to go live

Once you have passed the testing phase, Ontech will agree a go live date with you and the warehouse. For more information see [Stage 4](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4603019296/Main+Testing+Process#Stage-4---Approval-to-use-in-Production-system).

### Post go live file errors

Once you have gone live, if you have any issues with the files and the Request Status on the Outbound Request is Sent in Bevica, and the communication engine has sent the file, the file has made it through to the warehouse and you will need to contact the warehouse to resolve any issues.

The API process is shown [here](https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/4536008705/API+Response). If an issue occurs at stage 1, Bevica will receive a response back from the API, the communication engine message will error and you will see the error in the Error Message field.

If the file makes it through stage 1, the warehouse will inform you of any issues further into the process.


---

# 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://kb.bevica.com/documentation/integration/bevica_warehouse_integration/testing_vision_sales_outbound_requests.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.