> 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/bevica-select/bevica-select-outcomes/bevica_select_training_outcomes_-_warehouse_integration.md).

# Outcomes - Warehouse Integration

Checklist to validate Warehouse Integration in Bevica Select. Confirm outbound documents, message formats, and expected posting and status updates.

Use this checklist after the [Warehouse Integration](/bevica-select/bevica_select_training/bevica_select_training_-_warehouse_integration.md) training.

It helps you prove you can generate, send, and manage outbound requests to your 3PL.

### Before you start

You need:

* Access to Bevica Select (ideally a test company)
* [Introduction to Business Central](/bevica-select/bevica_select_training/bevica_select_training_-_introduction_to_business_central.md)
* Operations and inventory basics: [Inventory](/bevica-select/bevica_select_training/inventory.md)
* [Warehouse Integration](/bevica-select/bevica_select_training/bevica_select_training_-_warehouse_integration.md)

Recommended:

* Run these tests against a warehouse test mailbox or test endpoint.

### Completion criteria (what “done” looks like)

You’re done when:

* You can configure a warehouse integration record and link locations.
* You can create outbound requests from released sales (and transfers, if used).
* You can cancel, re-send, and recover from common mistakes.

### Warehouse integration setup

#### Create and validate setup

**Do**

1. Create a **Warehouse Integration** record for a warehouse site.
2. Link it to the relevant location code(s).
3. Review and confirm the setup fields you will rely on.

**Check**

* You understand what each key field controls (sending, formats, and behaviour).

### Sales orders (outbound demand)

#### Create orders that generate outbound requests

**Do**

1. Create the sales order types you use.
2. Populate the fields required by your warehouse.
3. Release the sales orders.

**Check**

* Released orders appear in the outbound request list as expected.

Useful reference: [Sales Order Processing](/bevica-select/bevica_select_training/bevica_select_training_-_sales_order_processing.md).

### Outbound requests

#### Generate, send, cancel, and recover

**Do**

1. Generate an outbound request.
2. View the request content.
3. Send the request.
   * Ensure the setup is sending to an internal email and not the live warehouse.
4. Cancel a request.
5. Manually add a sales order to the outbound request list.

**Check**

* You can explain what state the request is in and why.
* You can repeat the send safely in a test cycle.

### Request formats (choose the right one)

Only complete self-learning for the warehouse you use:

* [Vision Sales & Transfer Outbound Requests](/documentation/integration/bevica_warehouse_integration/vision_sales_and_transfer_outbound_requests.md)
* [Masterlink Outbound Requests](/documentation/integration/bevica_warehouse_integration/masterlink_sales_outbound_requests.md)
* [Culina Outbound Requests](/documentation/integration/bevica_warehouse_integration/culina_sales_outbound_requests.md)

### Testing guidance (Vision)

* [Testing Vision Sales Outbound Requests](/documentation/integration/bevica_warehouse_integration/testing_vision_sales_outbound_requests.md)


---

# 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/bevica-select/bevica-select-outcomes/bevica_select_training_outcomes_-_warehouse_integration.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.