This page contains technical detail about the physical database structure. It is not required for normal day to day operation of the Point Of Sale.
Goto: Documentation Home
This table records details of probable individual customers. The system can sometimes determine that different cash sales are the same individual with a reasonable level of confidence. This table holds this derived information and can be used for statistical reporting.
Columns
| FieldName | Datatype | Meta Info | Gnap | Description |
| dcid | long | Primary Key. Not zero | 100/E | A unique temporary internal id assigned to this derived customer. Each time customers are derived the same individual may be allocated a different dcid and name |
| name | string, 30+ char | 101/s | Generated name for this customer. Derived customers are always given generated names even if the probable actual name can be determined. See remarks. The names are generated by an algorithm and are provided as it can be easier to discuss "white horse 16" rather than dcid# 1348723. | |
| link0 | long | 110/E | Holds details of how this customer was derived. This is a bitmask and exact values are not yet stable. The more bits that are set, generally the more different methods were used. Do not overly rely on this value |
Indexing
A unique primary key should exist on the dcid field.
This table is frequently completely emptied and repopulated. Adding excessive indexing can slow this repopulate process on some databases
Remarks
Derived Customers by mining your retail data may not be legal in all countries due to privacy laws. The derived customer logic is provided for anonymous statistical purposes only, which is generally permitted where customers are not individually identified.
Even where the derived system can isolate individual identifying information (name, email, phone) we do not populate this information directly by default. We can provide it if requested in writing by the owner or senior business executive.