Skip to main content
This module contains all customer-related models used for managing customer data and personalization.

CustomerMemoryDTO

Model for customer memory entries that store personalized information.
FieldTypeRequiredDescription
entityIdstringYesEntity identifier (location or organization ID)
typestringYesEntity type: “location” or “businessOrganization”
datastringYesStored memory data as text
Customer memory allows storing personalized information like preferences, dietary restrictions, or special notes that persist across conversations.

CustomerDTO

Complete customer model with profile information and order history.
FieldTypeRequiredDescription
idstringYesUnique customer identifier
createdAtdatetimeNoCustomer account creation timestamp
updatedAtdatetimeNoLast profile update timestamp
locationIdsstring[]NoAssociated location identifiers (default: [])
emailstringNoCustomer email address
firstNamestringNoCustomer first name
lastNamestringNoCustomer last name
genderstringNoCustomer gender: “male” or “female”
birthDatedatetimeNoCustomer birth date
companyNamestringNoCompany name for business customers
phonestringNoPhone number
phoneAccessCodestringNoPhone access code/country code
addressAddressDTONoCustomer’s default address
deliveryNotesstringNoDefault delivery instructions
whatsappNumberstringNoWhatsApp number for communication
languagestringNoPreferred language: “fr”, “en”, “de”, “it”, “es”
ordersOrderDTO[]NoCustomer’s order history (default: [])
memoryCustomerMemoryDTO[]NoStored customer memory entries (default: [])

Customer Languages

The system supports the following customer languages:
CodeLanguage
frFrench
enEnglish
deGerman
itItalian
esSpanish

Customer Profile Usage

The customer model serves multiple purposes:
  1. Identity Management: Basic customer identification and contact information
  2. Personalization: Language preferences and delivery notes for customized service
  3. Order History: Access to previous orders for reordering and recommendations
  4. Memory Storage: Persistent storage of customer preferences and special requirements
  5. Multi-location Support: Tracking customer relationships across different restaurant locations
Most customer fields are optional to accommodate different levels of customer information availability. The system can function with minimal customer data and progressively enhance the profile over time.