Your fields. Your modules. One platform.
Every brand keeps information Flash doesn't ship with, and needs capabilities the next brand doesn't. Customization lets you add your own member fields and switch optional modules on per workspace — without a bespoke build and without forking the product. Everyone stays on one code base, so every upgrade and fix still reaches you.
Add the fields your business runs on
Create a field in Settings in seconds — pick a name and a type. There's no engineering ticket and no release to wait for. Six field types cover the vast majority of needs:
Text
e.g. Membership card number, vehicle plate
Number
e.g. Household size, external points
Date
e.g. Child's birthday, membership anniversary
Yes / No
e.g. Staff purchase, VIP flag
Single-select
e.g. Preferred store, occupation
Multi-select
e.g. Interests, followed categories
A field you add is a field you can act on
The hard part isn't storing an extra value — it's making the rest of the platform understand it. The moment you create a field, it's available across four places:
Member profile
Staff see and edit the value on each member's page.
Segments
Target by it — e.g. preferred store is Flagship and birthday is this month.
Email personalization
Drop the value straight into your copy for each recipient.
Import
Map an incoming column to the field when bringing members in.
Reporting dimensions are on the roadmap. Fields that hold sensitive personal data ship in a later release; for now, keep custom fields to non-sensitive business attributes.
Freedom, without the mess
Delete protection
A field in use by a segment, campaign or automation can't be deleted by accident — Flash tells you what depends on it first.
Retire safely
Deprecate a field to remove it from new work while existing data and uses keep running — no broken campaigns.
Owner-controlled
Only owners and admins define fields; everyone else fills them in. Each workspace only ever sees its own.
Turn on only what you need
Optional capabilities are delivered as modules you switch on per workspace — no separate install, no separate system. When a brand needs a capability that isn't in the standard product, we build it once as a module; the second brand that wants it just flips a switch. Your differences live as settings, never as a private copy of the code — which is exactly why one upgrade reaches every customer at once.
The decision rule we follow: use configuration first, add a custom field when you need to store a value, build a module when a capability is genuinely reusable — and never fork the product for a single customer.
Want to go further — build a whole new no-code data module, get Flash to notify your own systems in real time, or connect the apps you already use? See Developer Extensibility.
Turn on only the capabilities each brand needs.