Removing personal details from your ERP exports
Narada needs codes, never people. Nothing it does needs a person’s name or a street address, and contact emails are optional. Remove those before the files leave your building. We also recommend replacing customer codes, since many ERPs build them from the name, such as SMITHHEAT.
| Remove | Replace, the same way in every file | Never change |
|---|---|---|
| Customer and contact names | Customer codes, for example C-0001 (recommended) | Dates |
| Email addresses and phone numbers | Supplier codes and names, for example S-001 (optional) | Quantities |
| Street addresses | Branch names, for example Branch 1 (optional) | Prices and costs |
| Salesperson names | Status words | |
| Free-text notes and memos | Which code belongs to which row | |
| Supplier contact details |
Columns to drop, file by file
Section titled “Columns to drop, file by file”| File | Drop these columns before sending |
|---|---|
| Sales lines | Ship-to name and address, contact, salesperson, customer PO or job name, notes and memos |
| Customers | Name, contacts, emails, phone numbers, addresses |
| Purchase orders | Buyer name, supplier contact, notes |
| Suppliers | Contacts, emails, phone numbers. Names are optional |
| Returns | Notes. Keep the reason code |
| Parts list | Nothing, but check descriptions: special-order parts sometimes carry a customer’s name |
Prices and costs stay real. Narada works out what stock and missed sales cost you, in your own money. They are used only inside your own account.
An example: one sales line, before and after
Section titled “An example: one sales line, before and after”| Invoice | Date | Part | Branch | Customer | Qty | Price | Notes | |
|---|---|---|---|---|---|---|---|---|
| Before | INV-204118 | 2025-03-14 | HV-FIL-1620 | BR-01 | Smith Heating LLC | 6 | 19.95 | Call Joe 555-0142 |
| After | INV-204118 | 2025-03-14 | HV-FIL-1620 | BR-01 | C-0412 | 6 | 19.95 | removed |
You keep one lookup table: Smith Heating is C-0412, Ace Mechanical is C-0413, and so on. It stays with you. Narada never needs it.
Three rules that keep the data useful
Section titled “Three rules that keep the data useful”- One lookup table, every file. Apply the same lookup to every file the code appears in. A customer who is C-0412 in sales and C-0977 in returns looks like two customers.
- The lookup table stays with you. Keep each made-up code to 50 characters or fewer.
- Leave the numbers alone. Rounding prices or shifting dates changes the answer Narada gives you.
Why scrub before sending, not after
Section titled “Why scrub before sending, not after”When a file is first loaded, the AI sees its column headings and its first 5 rows, to match your columns to ours. If a name is still in those rows, the AI sees it. Scrubbing before sending keeps names out of every step.
What if we leave a column in by mistake?
Section titled “What if we leave a column in by mistake?”Narada ignores columns it does not read. But they travel with the file until the file is deleted, 30 days after it arrives. So remove personal columns before sending, rather than relying on us to skip them.
Where your data is stored and who can see it: Your data and security.