5.2.1 Create Customers

5.2.1.1 Terminology

Consult the following documents for the various customers and order types used in this document

• Customers

• Order types

5.2.1.2 Customer creation cases

5.2.1.3 Specifications

Customers requesting receipts can use a generic Pylon customer (e.g., "Retail Customer"). This applies to guest and retail customers.

For invoices, a unique customer must be created in Pylon for each customer. Identification will be based on the VAT ID, which is required for MyData integration.

1. Guest / Retail Customers:

   • Receipt: Use the generic Pylon customer with a configuration field storing the customer's ID. Verify the existence of this customer or provide an endpoint to retrieve the ID.

   • Invoice: Create a unique Pylon customer for each guest. The VAT ID is mandatory only if an invoice is required.

2. Wholesale customers:

   • Create a unique Pylon customer for each wholesale customer. Identification will rely on the VAT ID.

5.2.1.4 Endpoint to create customers

The endpoint to create customers in Pylon is described in the following document:

@todo (from ERP company);

The response should return the customer ID required for order processing.

The endpoint should prevent creating a duplicate customer with the same VAT ID.

5.2.1.5 Endpoint to fetch customers

Since we only store the customers for orders which require an invoice the best field for identification is the VAT ID.