Customer ID FAQ
Answers to common questions about customer ID formats, best practices, and the PatronPixel generator.
Everything people ask about customer IDs — formats, sequential vs random, collisions, entropy, and whether the generator is really private. (It is.)
What is a customer ID? +
A customer ID is a unique identifier a business assigns to each customer record, such as CUS-01001. It stays stable even when names, emails or phone numbers change, making it the permanent reference for that customer across systems. More: why businesses use customer IDs.
Can I use these generated IDs in a real database? +
Not directly. These are sample strings for testing, mockups and demos. Real customer IDs must come from your own system of record with a uniqueness guarantee — usually a database unique constraint. Always validate generated values against your system first.
Should customer IDs be sequential or random? +
Sequential IDs are readable and sortable but predictable — good for internal records, bad anywhere guessability matters. Random IDs are unguessable but harder to read aloud. Many systems use both: a sequential internal key and a random public reference.
What do the #, A, a and * mean in the pattern tab? +
# generates a digit, A an uppercase letter, a a lowercase letter, and * any alphanumeric character. Everything else in the pattern is kept literally — so CUS-####-AAAA produces IDs like CUS-4821-QKXD.
What does the entropy gauge show? +
Estimated bits of entropy per ID at your current settings — roughly how hard the ID is to guess. It is computed from character-set sizes and lengths, the same math in the formats guide. Sequential mode reports itself as predictable instead of showing a number.
How do I avoid ID collisions? +
Two layers: generate with enough entropy (the gauge helps), and enforce a unique constraint in your database — the constraint is the real guarantee, since application-level check-then-insert has a race condition. On collision, regenerate and retry.
Can a customer ID contain personal information? +
It should not. Avoid embedding names, birthdates or other personal data in IDs — IDs get logged, quoted in emails and printed on invoices. A neutral CUS-01042 leaks nothing; CUS-SMITH-1985 leaks plenty.
Is PatronPixel really free and private? +
Yes. No sign-up, no tiers. The generator is plain JavaScript in your browser using crypto.getRandomValues(); nothing is sent over the network, no cookies are set, nothing is stored. See the privacy page.
Can I download the IDs I generate? +
Yes. Click any ID to copy it, use 'Copy all' for the batch, or 'Download .txt' to save the set with a timestamp and a testing-only disclaimer. The file is created locally in your browser — nothing is uploaded.
What's the difference between an ID and a token? +
An ID identifies — it names a record and is often visible. A token authorizes — like a password-reset link — and must be secret, single-use and expiring. Never use a customer ID where a token belongs.