A good customer record does not contain everything. It lets the business perform the sale, issue the right document and reach the right person without turning every buyer into an identity file. Every field needs a purpose, access rule and lifetime.
Test every field
- Why are we collecting it?
- Is it necessary or merely convenient?
- Does the customer know the use?
- Who can view or change it?
- How is accuracy maintained?
- When is it archived or deleted?
- How will the person’s rights be handled?
1. Three records beat one giant form
Adapt depth to the flow. An anonymous counter sale may need no named identity beyond the required transaction document. A consumer requesting a named invoice supplies the necessary particulars. A B2B customer needs legal name, billing address, useful identifiers, operational contact and approved terms. Delivery can add a distinct address and recipient.
| Flow | Useful core | Needs justification |
|---|---|---|
| Counter sale | Transaction and receipt | Identity only where needed |
| Named consumer invoice | Name and required particulars | Phone/email for actual follow-up |
| Business customer | Legal name, address, IDs, contact | Credit and extra data |
| Delivery | Address and recipient | Sensitive instructions |
Do not copy national ID by habit. CNDP states that processing involving CIN numbers, sensitive data or certain interconnections requires prior authorisation; other processing may require a declaration. Analyse necessity and formality first.
2. Purpose determines the field and its lifetime
Law 09-08 and CNDP conditions require, among other points, an explicit legitimate purpose, adequate non-excessive data, accuracy, limited retention, security and access, rectification and objection rights. A delivery address does not automatically become a marketing list. A contact who leaves a customer can be replaced without deleting historical invoices.
| Data | Possible purpose | Lifetime/control |
|---|---|---|
| Legal name | Invoice and evidence | Tied to legal retention |
| Purchasing contact | Order handling | Review when role changes |
| Delivery phone | Coordination | Restrict access |
| Marketing email | Separate communication | Manage choice/objection |
| Internal note | Operational risk | Factual, necessary, reviewed |
Avoid subjective or insulting comments. Record an operational fact—“deliver after 15:00, agreed 2 September”—instead of judging the person.
3. Design access and correction before importing
Separate read, create, edit and export permissions. A salesperson may search customers without exporting the whole list; a cashier should not change a credit limit; the privacy owner needs to locate every system containing one person. Log sensitive changes.
- Name the data controller.
- Map purposes.
- Select minimum fields.
- Document information and processing basis.
- Check CNDP declaration/authorisation.
- Define roles and authentication.
- Set archive and deletion rules.
- Test access, correction and objection.
For foreign transfer or a cloud supplier abroad, check CNDP conditions and the applicable transfer request. “The software is international” does not resolve the formality.
Legal retention does not authorise every use
You may need to retain an accounting document while removing marketing data or restricting the archive. Document purposes separately.
4. Keep one commercial identity, not five duplicates
BelloPOS can centralise the operational identity used for quote, order, invoice and payment with role-based rights. Define a matching rule before merging: one phone does not always mean one customer, and separate establishments of one company may need distinct addresses.
- Create: search before adding
- Edit: preserve issued documents
- Merge: validate identity and history
- Export: limit and log
- Delete: separate active data from required archive
A useful metric is not fields completed. Track error-free invoices, current contacts and rights requests handled on time.
Mistakes to avoid
- Requesting CIN by default.
- Reusing email for marketing without analysis.
- Giving everyone export rights.
- Writing subjective notes.
- Merging on one phone number.
- Promising deletion incompatible with required archive.
Frequently asked questions
What is the minimum for a business customer?
Legal name, billing address, necessary identifiers and a useful contact, adapted to the document and contract.
Can I ask for CIN?
Not by reflex. CIN processing triggers specific review and may require CNDP authorisation; check necessity and formality.
How long should the record stay?
Set periods by purpose. Legally retained documents, active relationship, delivery and marketing need not share one period.
Can data be hosted abroad?
Check the foreign-transfer regime and CNDP formalities before choosing the data flow.
Does BelloPOS make the business automatically compliant?
It can support roles and customer records; purpose, notice, formalities and governance remain the business’s responsibility.
What to take away
A healthy customer record holds the minimum for an explicit purpose, stays accurate, restricts access and separates required archive from marketing.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- CNDP, Law 09-08 compliance conditions, read 2 September 2026
- CNDP, Law 09-08 on processing personal data
Audit ten fields in the customer form
For each, write purpose, user, source, lifetime and the action if the customer requests correction.
Read next
Other practical guides on the same subject: