Search Contacts by more than one identity field before creating a record. Only Name is required in the current New Customer sheet; email and phone are optional. When duplicate customers are not explicitly allowed for the tenant, an exact case-insensitive email match or normalized phone match stops Save. The customer list and profile are sensitive surfaces, so this article intentionally has no Harbor & Hearth customer screenshot.
Step by step
- Go to Contacts → Contacts and search name, email, phone, company, address, contact code, and imported identifiers. Open a possible match and compare identity and history before choosing Add Contact. A missing email or different spelling does not prove the person is new.
- Choose Add Contact only when no correct profile exists. The New Customer sheet opens directly in editing mode and shows Details only; Activity, Store credit, Account, Payment methods, Notes, profile image controls, Associations, and generated profile identifiers become available only after the record exists.
- Enter Name. It is the only field that enables Save and is trimmed before storage. Email and Phone can be blank, but leaving both empty makes later duplicate detection, communication matching, receipt delivery, and contact lookup less reliable.
- Enter the primary Email only after confirming spelling and customer authorization. CC emails are additional visible recipients on supported receipts and account invoices; BCC emails receive private copies. CentriPOS parses, normalizes, deduplicates, and prevents the primary email from being repeated in CC or BCC. Keep routing recipients necessary and current.
- Choose the primary Phone label: Mobile, Office, Home, Main, Fax, or Other. Enter the number using the tenant’s country formatting. On save, CentriPOS normalizes the primary number for storage and creates a primary labeled phone-line entry when a usable number exists.
- Use Additional phones for separate labeled numbers. Choose Add, select Mobile, Office, Home, Main, Fax, or Other, and enter the number. Empty additional lines are discarded; duplicate numbers are removed from the saved phone-line array. Use X to remove only the draft additional line.
- Enter Company and Role when they describe this person’s business relationship. These text fields do not create a Company association, make the customer a company bill-to identity, or assign a billing/requester role. Use Contacts → Associations after creation for those relationship controls.
- Complete any Account fields shown. These are tenant-configured customer fields and render as text, date, or number inputs according to General setup. Blank entries are removed from the saved accounting-field object. Do not use them for payment credentials or unrelated sensitive data.
- Enter Street address manually or choose the exact Address suggestion. Selecting a suggestion replaces Street, City, State, and ZIP from the parsed result; it does not fill Street address 2. Verify apartment, suite, delivery location, city, state, and ZIP before saving.
- Choose Customer Group when groups exist. This sheet exposes one selector—No group or one group—even though other bulk or imported workflows can create multiple membership rows. Saving from this form replaces memberships in the known group scope with the selected single group, so review a multi-group customer before editing.
- For a new customer, Associations is intentionally absent. Save the customer first, reopen the profile, and use Associations to add one or more existing household/company links. Association membership remains separate from Company text and Customer Group.
- Turn on Tax exempt only with approved documentation and policy. The saved flag tells supported checkout not to charge sales tax for this customer; it does not validate a certificate, set an expiration, choose exempt products, or update prior sales.
- Choose Save once. CentriPOS compares the entered email case-insensitively and compares primary phone numbers using digits, including a leading-country-code-tolerant comparison. When duplicates are disallowed and a match exists, the warning names the likely customer and the save stops. Review that profile instead of altering punctuation merely to bypass the control.
- If the tenant’s Allow duplicate customers setting is enabled, the client duplicate check is skipped. That setting is permissioned business policy, not evidence that a second record is correct. Create separate people sharing an email or phone only with clear identity evidence, then use Associations if they are related.
- On successful creation, CentriPOS assigns a new internal customer ID, generates the customer code through the stored record, initializes account balance to zero, saves selected group membership, closes the sheet, and returns the created customer to the opening workflow when supported. Search again and open it before relying on the record.
- To edit, open the Customer Profile → Details and choose Edit contact. The form loads the current primary/CC/BCC emails, labeled phones, company, role, account fields, address, group, and tax status. Existing association links can be added or removed in the Associations manager while editing.
- Change only the intended fields. Updating Email also rewrites the selected group membership’s stored fallback email when group membership is being saved. Changing group selection or primary email can remove and recreate memberships within the groups known to this form; recheck the customer’s group state afterward.
- Choose Cancel to discard draft text, address, group, and tax changes. In New Customer mode Cancel closes the unsaved sheet; in an existing profile it exits editing. Association Add/Remove controls act immediately through their own relationship writes, so do not assume Cancel reverses an association change already confirmed.
- Choose Save to update the existing record under the current tenant and customer ID. The customer code, imported source identifiers, balances, history, associations, notes, payment methods, and activity are not replaced by ordinary field editing. Reopen Details and verify every intended value and routing recipient.
- Manage a profile image only after the customer exists. The image menu can Upload / take picture, Replace image, Edit crop, or Delete image. Images are stored under the customer’s tenant and ID in product-media storage. Confirm the photo is appropriate, authorized, and belongs to the right person.
- After creation or editing, test the actual dependent workflow: send a controlled receipt when email routing changed, confirm phone sender/matching behavior when phones changed, inspect fulfillment address, attach the customer in Sell to check tax and price-book behavior, and verify Groups and Associations from their dedicated screens.
- No real customer-record screenshot is published for this guide. The Harbor & Hearth screenshot manifest marks /contacts/list rejected-sensitive-customer, and no safe exact New Customer capture is assigned. The guide stays text-only rather than inventing a profile or exposing customer data.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Add Contact | Opens New Customer directly in Details edit mode. |
| Name | Only required field; trimmed and used as the customer display identity. |
| Optional primary routing and matching address. | |
| CC emails | Normalized additional visible recipients for supported receipts and account invoices. |
| BCC emails | Normalized private recipients; primary and CC duplicates are removed. |
| Phone label | Mobile, Office, Home, Main, Fax, or Other. |
| Phone | Optional normalized primary number and primary phone-line source. |
| Additional phones | Separate labeled numbers; blank and duplicate values are discarded on save. |
| Company | Free-text affiliation; it does not create a Company association. |
| Role | Free-text responsibility; it does not assign association billing or requester permissions. |
| Account fields | Tenant-configured text, date, or number customer fields; blank values are omitted. |
| Address suggestion | Replaces parsed street, city, state, and ZIP after selection; Street address 2 remains separate. |
| Customer Group | Single No group/one group selector whose save can replace known-scope memberships. |
| Associations | Existing-customer-only immediate relationship manager for one or more household/company links. |
| Tax exempt | Customer checkout tax flag requiring verified business authority. |
| Duplicate check | Stops save on case-insensitive primary email or normalized primary-phone match unless duplicates are tenant-enabled. |
| Allow duplicate customers | Tenant setting that skips the client warning; it does not prove the records should be separate. |
| Save new customer | Creates a UUID-backed tenant customer, zero account balance, generated code, and selected group link. |
| Edit contact | Loads editable identity, routing, phone, account, address, group, association, and tax controls. |
| Cancel | Closes an unsaved new record or exits field editing; it does not reverse an already completed association write. |
| Save existing customer | Updates editable fields without changing the customer ID or intentionally replacing history and balances. |
| Customer image | Existing-record upload/camera, crop, replace, or delete controls. |
| Post-save verification | Reopen profile and test communication, fulfillment, tax, pricing, group, and association behavior affected by the change. |
| Sensitive screenshot boundary | No customer-list or New Customer screenshot is published until an exact safe Harbor & Hearth capture exists. |
Expected result
One intended customer ID and code exist with the reviewed name, normalized email routing, labeled deduplicated phones, company/role, configured account fields, verified address, tax flag, group and association links; duplicate policy was respected; sensitive profile imagery and data remain private; and controlled communication, fulfillment, Sell pricing/tax, Group, and Association checks reflect the saved changes.
Troubleshooting
- Search by more than one identity field before creating or merging a customer.
- Confirm the selected customer, company, or household before changing balances or associations.
- Do not place payment credentials or unnecessary private information in notes.
CentriPOS API explorer · API Center administration