> 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/culina_sales_outbound_requests.md). # Culina Sales Outbound Requests Create Culina-formatted outbound requests for sales orders. To correctly send outbound files containing sales orders to **Culina** managed warehouses, you first need to have completed **Warehouse Integration Setup** for the specific warehouse. See [Third Party Warehouse Integration](/documentation/integration/bevica_warehouse_integration.md). Then there may be some Culina specific setup on Customers and Ship-to's that is necessary. * Delivery Instructions / Comments * Booking / Delivery Details ## Delivery Instructions / Comments **Sales Orders** Delivery Instructions can be sent to Culina. On a sales order, navigate to **Comments,** enter the required text and assign the correct comment type **Delivery Instr. (Sales).** The first 160 characters, across multiple lines, are sent to the warehouse. If the instruction text exceeds this limit, it will not be shown in full. See the **Sales Comments** section here [Sales Comments and Notes](/documentation/guides/sales/sales_comments_and_notes.md) ## Booking / Delivery Details The below fields on a sales order under **Warehouse Integration** fasttab are used by the warehouse to manage deliveries. * **Requested Delivery Date:** the date you are asking the warehouse to deliver the order. * **Ship-to Contact No.** provides the name and phone number. * **Booking in Date:** only populate if a specific date has been agreed. * **Slot 1 Start Time:** beginning time slot for delivery. * **Slot 1 End Time:** ending time slot for delivery. * **Slot 2 Start Time:** not used by this integration. * **Slot 2 End Time:** not used by this integration. ## File details The following table highlights where details sent to the warehouse are held on the sales order. | File Field | Sales Order field | Note | | ---------------------------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------- | | Warehouse | | Set from Warehouse Integration Setup | | Customer | | Set from Warehouse Integration Setup | | Order Date | Order Date | | | Customer Order No. | External Document No. | | | Consignee Order number | | | | Delivery Name | Ship-to Name | The file's field length is limited to 40 characters. | | Address 1 | Ship-to Address | The file's field length is limited to 40 characters. | | Address 2 | Ship-to Address 2 | The file's field length is limited to 40 characters. | | Address 3 | Ship-to City | | | Address 4 | Ship-to County | | | Delivery Date | Requested Delivery Date | | | Delivery Code | | | | Excise Number / Deferment Account number | | | | Delivery Text 1 | Comments | See Delivery Instructions / Comments above | | Delivery Text 2 | Comments | See Delivery Instructions / Comments above. | | Delivery Text 3 | Comments | See Delivery Instructions / Comments above. | | Delivery Text 4 | Comments | See Delivery Instructions / Comments above. | | Booking in Name | Ship-to Contact No, Name | | | Booking in Phone number | Ship-to Contact No, Phone No. | | | Booking in Date | Whse. Booked/Collection Date | Only to be populated if a specific date has been pre-arranged. | | Delivery Point Code | | | | Delivery Window Start Time | Slot 1 Start Time | | | Delivery Window End time | Slot 2 End Time | | | Product Code | 'No.' field | Only inventory items are included in the file. The Culina Product Code must match Bevica Item No. | | Rotation | | | | Quantity | | | | Unit of Measure | Sales Line Unit of Measure Code | Bevica converts the sales line UoM to CASE or UNIT. | | Cases Sales Value | Customer Price | Populated for Duty Free orders. | | Pick info | | | --- # 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/culina_sales_outbound_requests.md?ask=&goal= ``` `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.