> 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/web_integration_-_customer.md).

# Web Integration - Customer

Configure customer export/import and customer-related sync rules.

### Customers

The website needs a way to identify Bevica customers when sending orders. On the **Customer** record, the ‘Web ID’ is used to record this information.

![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-79de4d5b072db420256f95cb72ffce9d5450170f%2FrEGWGRPyCIWxWIKOiFUo5dozxo5e0rU-YQ.png?alt=media)

The specific use of this field will depend on your implementation. Typically, at implementation, you will need to map your Bevica Customers to your Web Customers or vice versa and populate this field.

When a new Customer is created through the order processing function, this field will be populated with the Customer ID from the website. This can be a number, email, or any appropriate value.

### Customer Balance

The ‘Balance’ fields on the Customer record automatically filter to ‘TODAY’ when being called by the website.

### Sales & Receivables Setup

We recommend that ‘Ignore Updated Addresses’ is turned on in **Sales & Receivables Setup** so that web orders do not update Customer addresses.

![](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-67ddc42115f30b4bd68160caec093f445837c5ef%2FPUrNkuw94bjInj6NWLcGv4_7uO-T5O5dQw.png?alt=media)


---

# 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/web_integration_-_customer.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.