# Customer Products

## Short description

Some customers may have their own productnumbers as an alternative of the shop's articlenumbers. With this interface it is possible to define these numbers.<br>

## Delivery method

**Update Frequency**: Batch at least once a day\
**Incremental or complete set:** Incremental

**Filetype:** Zipped XML

**Filename: \[SHOPNAME]\_ErpCache\_CustomerProducts**\_**\[INDEXNUMBER]**.xml\
**Transport:** over FTPS, FTPS Vendisto server hosted by INTEGRACE, file will be placed on FTPS server by ERP party.

**Location within FTP root:** \ErpCache\\

## Structure XML

```markup
<?xml version="1.0" encoding="utf-8"?>
<Import>
    <ImportSettings>
        <Importer>ErpCache_CustomerProducts</Importer>
        <Version>1.0</Version>
        <PartialImport>Y</PartialImport>
    </ImportSettings>
    <CustomerProducts>
        <CustomerProduct>
            <AccountNumber></AccountNumber>
            <ProductNumber></ProductNumber>
            <OwnProductNumber></OwnProductNumber>
        </CustomerProduct>
    </CustomerProducts>
</Import>

```

## Fields XML

**Import element:**

<table data-header-hidden><thead><tr><th width="190.50953678474113">Name</th><th>Description</th><th width="150">Type</th><th>Required/Optional</th></tr></thead><tbody><tr><td>Name</td><td>Description</td><td>Type</td><td>Required/Optional</td></tr><tr><td>ImportSettings</td><td>Container element for importsettings</td><td>Element</td><td>Required</td></tr><tr><td>CustomerProducts</td><td>Container element for CustomerProduct data</td><td>Element</td><td>Required</td></tr></tbody></table>

**ImportSettings element:**

<table data-header-hidden><thead><tr><th width="178">Name</th><th>Description</th><th width="150">Type</th><th>Required/Optional</th></tr></thead><tbody><tr><td>Name</td><td>Description</td><td>Type</td><td>Required/Optional</td></tr><tr><td>Importer</td><td>Name of the importer.<br>Must be ErpCache_CustomerProducts.</td><td>Text</td><td>Required</td></tr><tr><td>Version</td><td>Version of the import xml. To be used for backward compatibility issues.</td><td>Text,<br>must be 1.0</td><td>Required</td></tr><tr><td>PartialImport</td><td>Defines if the file contains a complete list or represent a partial update of the customerproducts.</td><td>Boolean,<br>Default Y</td><td>Optional</td></tr></tbody></table>

**CustomerProduct element:**

<table data-header-hidden><thead><tr><th>Name</th><th width="187">Description</th><th width="150">Type</th><th>Required/Optional</th></tr></thead><tbody><tr><td>Name</td><td>Description</td><td>Type</td><td>Required/Optional</td></tr><tr><td>AccountNumber</td><td>Account number (debtor number) of the customer</td><td>Text</td><td>Required</td></tr><tr><td>ProductNumber</td><td>The identifier of a product</td><td>Text</td><td>Required</td></tr><tr><td>OwnProductNumber</td><td>The customer's  own productnumber. If left empty the current Own ProductNumber will be removed from the database.</td><td>Text</td><td>Required</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://shoxl.gitbook.io/erp-integration-guide/2023.7/erp-cache-batch/customerproducts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.