> 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_website_integration/website_integration_setup.md). # Website Integration Setup Complete the initial setup for Bevica website integration. The Web Integration Setup page provides the defaults to automate sending and receiving web-related data. ### Quick Page links: * Setup * Web Order Setup * Locations * Stock ### Setup Setup is required in each Business Central Company you want to integrate with. Go to **Web Site Setup** and ‘Initialise’ to automatically create the web services.
| Fast Tab | Field | Usage | | -------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | General | Default Stock Location | The default location for transactions | | | Default Order Type | See ‘Web Orders Setup’ section below | | | Default Price Group | If you have a single price group | | | Comment Code Delivery | Comments on Web Orders map to particular comments on Bevica orders | | | Comment Code Gift | | | | Comment Code Generic | | | | Hide Confirm Messages | When doing bulk updates this stops confirmation messages. This should only be used during bulk updates as the confirmation messages are there to help prevent data issues | | | Unblock Customer After Creation | This unblocks the Customer after creation in case other extensions may create blocked customers. | | | Protect Customer Web Id | Set this to prevent Users editing 'Web Id' on the Customer card. The field can be managed via a Configuration Package | | Stock | Stock Active Locations | See ‘Locations’ section below | | | Stock Split by Variant | Whether the Variant Code (Duty Type) splits stock | | Payment | Payment Journal Template | See: Website - Payments | | | Payment Journal Batch | | | | Payment Function | | ### Web Order Types Setup Different types of orders can be managed if required. In most scenarios, there is a single ‘Web Order Type’ created during initialisation and called “WEB”. | Field | Usage | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Order Type | Used by the Website to identify particular order paths | | Default Customer No. | If the Customer doesn’t already exist, using a generic customer account for orders | | Default Location Code | | | Default Customer Template | If creating Customers the template to use to default values | | Create Customer | Whether Customers should be created if they are new, rather than using a Default Customer | | Default Currency Code | | | Default No. Series | If you want to use a different No Series for different types of Web Order | | Release Document | To automatically 'Release' sales orders when they are created. | | Force Price Including VAT | Make all prices from the website be treated as VAT inclusive. This defaults the order to be flagged as ‘Prices Include VAT’ | | Validate Function | {No Action, Standard, ByPass} Allows for customised Validation processes | | Process Function | {No Action, Standard, ByPass} Allows for customised Process processes | | Default Unit of Measure | | | Document Type | {Blank, Sales Order, Sales Return Order} | | Global Dimension 1 Code | Default a dimension onto the Sales Order | | Global Dimension 2 Code | Default a dimension onto the Sales Order | | Force Web Order Id as Document No. |

Tick this to use the Web Order ID as the Bevica Document No. If this is selected the 'Default No. Series' field must be blank.

You need to ensure that all website order Id's are 20 characters or less and that no duplicate Id's are presented to Bevica. In both cases, the web order import will fail.

| | Transaction Type | Options: Sale Into Reserve, Withdrawal from Reserve. Sets all lines on the order to this Transaction Type. | | Broking Order | Set this where the order is a Broking order. The entire order must only contain Item lines which have a Paid Reserve No. | ### Locations Locations for the website are used for Inventory and Web Orders. ### Single Location Setup You can define a ‘Default Stock Location Code’ if you only use a single **Location** in Bevica for your inventory, or for the website. ### Multi Location Setup If you need to use multiple locations for inventory then on the **Location** card tick the ‘Web Stock’ field for each location. The ‘Web id’ can be used to ensure a consistent identifier for the website in case of record renaming, or if the website will identify this location using a different value than the Location ‘Code’ field. ![Multi Location Setup](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-8bd351f30343825046ec14292669c9126f0f2907%2FTR_dU73BfGG8SPJJlUA5-WZ-PGtDEeyCNw.png?alt=media) ### Stock After you have set your Locations and appropriately then select ‘Update Stock’ on the ribbon. This will create stock records based on the Location, Variant, and Unit of Measure setup you have defined. If an item is deleted, it will be automatically removed from the Web Stock table. If orphaned entries need to be deleted in bulk, you can run the 'Clear Deleted WebStock' report. This will only need to be run once. ### Retention Policy The Web Orders table (71955) is available to add to your Retention Policies to enable regular clean-up of data. This can be set up initially from the Web Site Setup page. From the Web Site Setup page, you can find 'Setup Retention Policy' under the 'Related' dropdown. Once this has been created from the Web Site Setup page it can be managed directly through Retention Policies. It is advised that orders in 'Created' or 'Errored' status are set to never delete to ensure unprocessed orders are not removed from Bevica unintentionally. Here you can find more information on [Setting up Retention Policies](https://learn.microsoft.com/en-gb/dynamics365/business-central/admin-data-retention-policies). --- # 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_website_integration/website_integration_setup.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.