Appearance
Membership Cards
Application address: /admin/loyalty-cards · Product baseline: 0.4.0
Reference status
Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.
Open this screen
Use OSERP navigation to find Membership Cards, or open /admin/loyalty-cards on your OSERP application after signing in. Confirm the active company before reading or changing records.
Menu access: settings:manage
Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.
Fields and input controls
Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.
Up to 50,000 in one run.
| Property | Reference |
|---|---|
| Reference key | up-to-50-000-in-one-run |
| Location | Screen / contextual panel |
| Input control | number |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Minimum | 1 |
| Maximum | 50000 |
| Editing | No disabled/read-only condition declared directly on this control. |
Prefix
| Property | Reference |
|---|---|
| Reference key | prefix |
| Location | Screen / contextual panel |
| Input control | input |
| Required in interface | not declared on control |
| Maximum characters | 10 |
| Placeholder | LTY |
| Editing | No disabled/read-only condition declared directly on this control. |
Separator
| Property | Reference |
|---|---|
| Reference key | separator |
| Location | Screen / contextual panel |
| Input control | select |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Declared choices: none. Choices loaded from records or configuration are not enumerated here.
Digits
| Property | Reference |
|---|---|
| Reference key | digits |
| Location | Screen / contextual panel |
| Input control | number |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Minimum | 1 |
| Maximum | 16 |
| Editing | No disabled/read-only condition declared directly on this control. |
Add a check digit (catches mistyped numbers)
| Property | Reference |
|---|---|
| Reference key | add-a-check-digit-catches-mistyped-numbers |
| Location | Screen / contextual panel |
| Input control | checkbox |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Name this run
| Property | Reference |
|---|---|
| Reference key | name-this-run |
| Location | Screen / contextual panel |
| Input control | input |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | BATCH-2026-01 |
| Editing | No disabled/read-only condition declared directly on this control. |
Note (optional)
| Property | Reference |
|---|---|
| Reference key | note-optional |
| Location | Screen / contextual panel |
| Input control | input |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Named actions
These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.
- File existing numbers
- Generate a run
- Download for printer
- Void run
- Cancel
Help text and messages
The following wording is embedded in this screen. It describes interface guidance, rather than independently verified system guarantees.
- Numbers come from your loyalty series. With a check digit, a mistyped number is refused before it reaches a customer record.
Verification still required
Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.
See the operating manual, coverage register, and troubleshooting guide.