Page History
Table of Contents
47 Member Management
47.1 Product Stack
47.2 Member Module – Highlights
47.3 Setup Entities
47.3.1 MEMBER COMMUNITY
47.3.2 MEMBERSHIP SETUP
47.3.3 Membership Sales Setup
47.3.4 MEMBERSHIP ADMISSION SETUP
47.3.5 MEMBERSHIP ALTERATION SETUP
47.3.6 MEMBER REMINDER SETUP
47.3.7 MEMBER LIMITATION SETUP
47.4 Master Data and Relation Entities
47.4.1 Membership
47.4.2 Membership Role
47.4.3 Member
47.4.4 Member Card
47.4.5 Membership Notification
47.5 Entry Entities
47.5.1 Membership Entry
47.5.2 Member Info Capture
47.5.3 Membership Points Entry
47.5.4 Member Notification entry
47.6 High Level Entity Relationship Model
47.7 Details
47.7.1 Member Community
47.7.2 Membership Setup
47.7.3 Membership Sales Setup
47.7.4 Membership Admission Setup
47.7.5 MM Membership Alteration Setup
47.7.6 MEMBER NOTIFICATION SETUP
47.7.7 MEMBERSHIP LIMITATION SETUP
47.7.8 Membership
47.7.9 MEMBERSHIP ROLE
47.7.10 MEMBER
47.7.11 MEMBER CARD
47.7.12 Membership Entry
47.7.13 MEMBERSHIP NOTIFICATION
47.7.14 MEMBER NOTIFICATION ENTRY
47.8 Managing Memberships
47.8.1 POS commands
47.8.2 Web Services
47.8.3 RENEW
47.8.4 Price calculations
47.8.5 Stacking
47.8.6 Grace Period
47.8.7 Extend
47.8.8 Price calculations
47.8.9 Stacking
47.8.10 Grace Period
47.8.11 Upgrade
47.8.12 Price calculations
47.8.13 Stacking
47.8.14 Grace Period
47.8.15 CANCEL
47.8.16 Price calculations
47.8.17 Stacking
47.8.18 Grace Period
47.8.19 REGRET
47.8.20 Price calculations
47.8.21 Stacking
47.8.22 Grace Period
47.9 Member Notification
Setup example:
47.9.1 Activating
47.9.2 Member Opt-out
47.9.3 Email templates
47.9.4 Automation
47.10 Setup
47.10.1 ROLE CENTER
Setting up the role center Profile ID.
47.10.2 Assigning a Profile ID to User ID
47.11 POS Setup
47.11.1 Touch Screen Setup
47.12 Internal Member Registration Process
Overview
47.12.1 Before Audit is posted
47.12.2 During Audit Role posting
47.13 Web Services
47.13.1 Setup in Navision:
47.13.2 Setting up memberships
47.13.3 Querying Memberships and members
47.13.4 Mananging the membership product and duration
47.13.5 Tickets and registering member Integration
47.14 Loyalty Reward Program
47.14.1 Member Community
47.14.2 Loyalty setup
Example of Date Formula in Navision
47.14.3 Item Points Setup
47.15 Members' Link to Loyalty Reward Programs
47.15.1 Membership Setup
47.15.2 Membership Sales Setup
47.15.3 Create Membership
47.16 Application of the Loyalty Reward Programs
47.16.1 Sale on POS to a Member
47.17 Loyalty Reports:
47.17.1 Loyalty Points Summary
47.17.2 Report: Loyalty Points Value
47.17.3 Report: Loyalty Points Detail
47.18 Earning and Redeeming points
47.19 Auto Renew Process
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The Membership Module adopts the following approach:
...
Web Service integration for Magento integration
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The membership community is the top level in the setup of member and membership. A community is the club or association that is marketing the memberships. A Navision company can host any number of communities. The setup defines common rules that apply to membership within the community
Anchor | ||||
---|---|---|---|---|
|
The membership setup defines the rules that govern a specific membership in this community. The membership defines the benefits (pricing and discounts) the member will be able to capitalize on.
Anchor | ||||
---|---|---|---|---|
|
Memberships can be sold using different items in the POS or on the WEB. One aspect of membership is to sell a potential benefit to the customer that is valid for a specific amount of time.
Anchor | ||||
---|---|---|---|---|
|
In combination with the Ticket Module, members can gain access to extra tickets and have guests accompanying them for the visit. With his setup, memberships are linked to different types of tickets that can be selected when using the self-scan solution.
Anchor | ||||
---|---|---|---|---|
|
This table is used to define how an already created membership may be altered, both in terms of validity in time and the type of membership that is currently active.
Anchor | ||||
---|---|---|---|---|
|
Member can have reminders sent to them because of different events. Setup of notifications are done in this table. Reminders can be chained, if this notification is not canceled, it will create a new future notification to be executed.
Anchor | ||||
---|---|---|---|---|
|
This table is used to limit access for memberships in order to prevent misuse of cards.
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Membership connects one or more member roles.
Anchor | ||||
---|---|---|---|---|
|
Member role is the link between a member and its membership(s). A member can be part of multiple memberships and act in different roles.
Currently 2 roles are defined:
...
- Administrator – has the right to manage and benefit from membership
- User – has the right to benefit from membership
Anchor | ||||
---|---|---|---|---|
|
The member entity store the information about a member. A member is a person.
Anchor | ||||
---|---|---|---|---|
|
Members can identify their right to a membership using the member card. A member may have multiple cards for the same membership.
Anchor | ||||
---|---|---|---|---|
|
The system generates pre-emptive events to be processed in the future. The notification due date it is derived from the setup.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
This table stores the time frame(s) for which the membership is valid. The initial price, discounts and initial duration is also captured.
Anchor | ||||
---|---|---|---|---|
|
This is a temporary entity used to capture the information used for the current transaction.
Anchor | ||||
---|---|---|---|---|
|
Reserved for future use.
Anchor | ||||
---|---|---|---|---|
|
This is the data available to the notification being generated. This entry will be created when the notification is processed.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Menu: Departments > Retail Add Ons > Members > Member Community
...
FIELD NAME | DESCRIPTION |
Code | A code used to link this community with other tables |
Description | A use description of the community |
External No. Search Order | An option to define what search term should be used when there is ambiguity.
|
External Membership No. Series | Number series to generate the external membership identity |
External Member No. Series | Number series to generate the external member identity |
Member Unique Identity | The member value that must be used to uniquely identify a member;
|
Create Member UI Violation | When a member is created and the unique identity is violated the system can react with in the following ways;
|
Member Logon Credentials | Defined what term to use for logon credentials when a 3rd party member management soft is used;
|
Membership to Cust. Rel. | This is field is used when memberships are linked with customers. This is required in the following scenarios;
|
Create Renewal Notification | Create a notification when membership requires renewal |
Anchor | ||||
---|---|---|---|---|
|
Note, this is a setup table to define how a membership should behave when it is created.
Menu: Departments > Retail Add Ons > Members > Membership Setup
...
FIELD NAME | DESCRIPTION |
Code | A code used to link this community with other tables |
Description | A use description of the membership |
Membership Type | Controls how members and memberships are related.
|
Loyalty Card | For future use. |
Customer Template Code | This code identifies a template for how the customer associated with the membership will be created. This field is required when the "Membership to Cust. Rel." field on community is checked. |
Member Information | How the member entity should be treated.
|
Blocked | The setup is blocked from usage |
Blocked At | Time of block |
Perpetual | The membership validity can be perpetual (everlasting) |
Member Role Assignment | How members are assigned their role in the membership
|
Membership Member Cardinality | Maximum members in a GROUP membership |
Community Code | A link to the community this membership belongs to |
Create Renewal Notification | Create a notification when membership requires renewal |
Create Welcome Notification | Create a notification when member is created |
Receipt Print Object Type | The type of object used for generating printing for the receipt |
Receipt Print Object ID | The object ID used for generating the printout. The system supplied codeunit for printing is |
Account Print Object Type | The type of object used for generating printing for the account information |
Account Print Object ID | |
Allow Membership Delete | This options allow memberships to be deleted. |
Confirm Member On Card Scan | When a POS function requires the member card to be scanned, the member card will pop up for visual confirm. |
| |
Card Number Scheme | Who responsible of creating the member card number
|
Card Number Prefix | Specific prefixes can be defined (or generated by the number series) |
Card Number Length | The length is used to pad a number that is too short |
Card Number Validation | If there should be a check digit appended to end of the generated number |
Card Number No. Series | The number series used generated the base of member card number |
Card Number Valid Until | For how long a member card should be valid |
Card Number Pattern | A patter can be entered to control how the card number should be generated. A pattern consists of keywords that will create a number that is a bit more difficult to guess. Available keywords are listed below and must be included between [ and ].
|
Card Print Object Type | The type of object used for generating printing for the member card |
Card Print Object ID |
Anchor | ||||
---|---|---|---|---|
|
This table is used to defined the first-time sales of memberships. The menu is in the shortcut from Membership Setup, under Home Ribbon.
...
FIELD NAME | DESCRIPTION |
Type | An option to define what type of "item" we are selling.
|
No. | The Item or Account used for membership sales |
Membership Code | Links the Membership Setup table. The item sold will create a membership of this type. |
Blocked | |
Blocked At | |
Valid From Base | An option to define how the membership time frame start date should be calculated.
|
Sales Cut-Off Date Calculation | Reserved for future use. |
Valid From Date Calculation | Date formula for activation date |
Valid Until Calculation | An option to define the duration of the membership. Options are;
|
Duration Formula | Date formula for duration |
Anchor | ||||
---|---|---|---|---|
|
This table is used in combination with the ticket module. When a member uses the self-scan solution a combination of extra tickets can be associated with the membership code. The menu is in the shortcut from Membership Setup, under Home Ribbon.
A total cardinality can be registered on the record with Ticket No. Type "NA". The total cardinality limits the maximum combination of tickets for this member. Example – the membership itself targets senior citizens and following guest admissions have been setup.
...
The self-scan will always create new tickets for the member and admission. If the ticket items created include multiple admission codes (valid for more than admission location or event), it's advisable from a statistical view to print the tickets for the member and have member and guest reuse those for future arrival and departure validation.
FIELD NAME
DESCRIPTION
Membership Code
Links the membership setup table
Admission Code
Links the ticket admission definition table
Ticket No. Type
Defines which type and source of item number is used to define the sales number of ticket. Options are;
- NA
- ITEM
- ITEM_CROSS_REF
ALTERNATIVE_NUMBER
|Ticket No.
The (Item) number to use when creating tickets. Must be setup in the ticket module.
Cardinality Type
The options are:
- UNLIMITED
LIMITED
|Max Cardinality
Maximum number of tickets of this type per interaction. (Requires Cardinality Type LIMITED)
Description
A useful description for the member to understand when to select this alternative
MM Membership Alteration SetupAnchor _Toc505335466 _Toc505335466
This table defines the setup and business rules for altering a membership. Se the section "Managing Memberships" for an in depths analysis of business impact. The menu is in the shortcut from Membership Setup, under Navigate Ribbon.
...
FIELD NAME | DESCRIPTION |
Alteration Type | The type of alteration describe, options are:
|
From Membership Code | Links to Membership Setup. The type of membership we intend to change. |
Sales Item No. | The sales item used in the POS and accounting to capture the event. |
Description | The description used in POS |
To Membership Code | The target membership code |
Alteration Activate From | Options to define the start date calculation of this change, options are:
|
Alteration Date Formula | Date formula calculate the start date, e.g. CM+1 to calculate the first of next month. |
Activate Grace Period | Activate the grace period filters. Allows for filtering out unwanted change paths in relation to the current state of the membership validity. (E.g. it should not be possible to RENEW membership until 1 month prior to it expires) |
Grace Period Relates To | Which date the grace period should operate on. Options are:
|
Grace Period Before | A date formula (such as "14D") to define the time frame BEFORE the grace date which this alteration is valid. |
Grace Period After | A date formula (such as "14D") to define the time frame AFTER the grace date which this alteration is valid. |
Membership Duration | The duration of the new membership time frame |
Price Calculation | How the price should be calculated. Options are:
|
Stacking Allowed | Defines if multiple RENEWs are possible. |
Anchor | ||||
---|---|---|---|---|
|
This table hold set up that created member notifications. The menu is in the shortcut from Member Community, under Navigate Ribbon.
...
FIELD NAME | DESCRIPTION |
Code | Primary Key |
Description | A useful description |
Type | Option to determine type of notification
|
Days Before | Used with type renewals, this will create a notification X days before the membership needs to be renewed |
Days Past | Used with WELCOME and NONVISIT. Number of days since member was created or members' previous visit. |
Template Filter Value | This value is passed on the email processing and the intention is to simply notification template selection. |
Community Code | This notification belongs to stated Community Code. May be blank to be independent of membership code. |
Membership Code | This notification belongs to stated Membership Code. May be blank to be independent of membership code. |
Next Notification Code | Unless the notification is canceled when processed, it will create a new notification with this code. |
Cancel Overdue Notif. (Days) | Is a safeguard to not send notifications that are overdue, stated by number of days. A zero indicates no safeguard. |
Target Member Role | Who among the membership members is the target of the notification;
|
Anchor | ||||
---|---|---|---|---|
|
This table is used to define membership access rules. The menu is in the shortcut from Membership Setup, under Navigate ribbon.
You define rules for the membership access and when a condition is met, the system will react and prompt with a message.
...
FIELD NAME | DESCRIPTION |
Membership Code | This rule is for the stated membership code |
Admission Code | This rule is for the stated admission code. Works with webservie not POS (yet) |
Constraint Type | Options are
|
Constraint Source | Options are
|
Constraint Seconds | No. of seconds when constraint type is Relative Time |
Constraint From Time | Constraint start time when constraint type is Fixed Time |
Constraint Until Time | Constraint end time when constraint type is Fixed Time |
Constraint Dateformula | Date formula when constraint type is Dateformula |
Event Limit | The access limit per event |
POS Response Action | Options are
|
POS Response Message | Response message to display depending on the POS response action |
WS Response Action | Options are
|
WS Deny Message | Message when WS response action is Error |
Response Code | Unique code for each response |
Blocked | Block rule when not in use |
Anchor | ||||
---|---|---|---|---|
|
The membership entity holds the actual membership.
Menu: Departments > Retail Add Ons > Members > Memberships
...
FIELD NAME | DESCRIPTION |
Entry No. | Primary Key |
External Membership No. | The external membership identification |
Description | Membership description |
Company Name | A corporate membership belongs to a named company |
Blocked | Enables blocking a membership without interrupting the membership time frame |
Blocked At | When it was blocked |
Blocked By | Initials of user that blocked membership. |
Community Code | A link to the membership community table |
Customer No. | A link to the customer table |
Membership Code | A link to membership setup table |
Issued Date | Date of creation |
Document ID | (Web Service) A reference to the message that created this membership |
Anchor | ||||
---|---|---|---|---|
|
This table links the membership with its members.
...
FIELD NAME | DESCRIPTION |
Membership Entry No. | (Primary Key field) Foreign key to membership table |
Member Role | (Primary Key field)
|
Member Entry No | (Primary Key field) Foreign key to member table |
Blocked | Enables blocking a membership without interrupting the membership time frame |
Blocked At | When it was blocked |
Blocked By | Initials of user that blocked membership. |
Community Code | A link to the membership community table |
User Logon ID | Credentials for 3rd party member management software |
Password SHA1 | Credentials for 3rd party member management software |
External Member No. | (Flow field) |
Member Display Name | (Flow field) |
External Membership No. | (Flow field) |
Membership Code | (Flow field) |
Company Name | (Flow field) |
Anchor | ||||
---|---|---|---|---|
|
Represents the person in the membership.
Menu: Departments > Retail Add Ons > Members > Members
...
| DESCRIPTION | ||||||
Entry No. | Primary Key | ||||||
External Member No. | The external member identification number | ||||||
First Name | |||||||
Middle Name | |||||||
Last Name | |||||||
Blocked | Enables blocking a membership without interrupting the membership time frame | ||||||
Blocked At | When it was blocked | ||||||
Blocked By | Initials of user that blocked member. | ||||||
Phone No. | |||||||
Social Security No. | |||||||
Address | |||||||
Post Code Code | |||||||
City | |||||||
Country Code | |||||||
Country | |||||||
Gender | Options are:
| ||||||
Birthday | |||||||
Picture | |||||||
E-Mail Address | |||||||
E-Mail News Letter | Options are:
| ||||||
Created Datetime | |||||||
Display Name | |||||||
Contact No. | |||||||
Document ID | (Web Service) A reference to the message that created this member |
Anchor | ||||
---|---|---|---|---|
|
FIELD NAME | DESCRIPTION |
Entry No. | Primary Key |
External Card No. | The external member card identification number |
External Card No. Last 4 | |
Pin Code | |
Valid Until | When this member card is used, the valid until date is checked. Expired cards are not valid |
Blocked | Enables blocking a membership without interrupting the membership time frame |
Blocked At | When it was blocked |
Blocked By | Initials of user that blocked member card. |
Block Reason | This option to specify why card was blocked. Options are;
|
Membership Entry No. | Foreign key to membership table |
Member Entry No. | Foreign key to member table |
External Member No. | (Flow field) |
Member Blocked | (Flow field) |
Display Name | (Flow field) |
E-Mail Address | (Flow field) |
External Membership No. | (Flow field) |
Membership Blocked | (Flow field) |
Company Name | (Flow field) |
Document ID | (Web Service) A reference to the message that created this member card |
Anchor | ||||
---|---|---|---|---|
|
This table holds the time frame entries that establishes membership validity. The entries are found in the membership card under menu Memberships.
...
FIELD NAME | DESCRIPTION |
Entry No. | Primary Key |
Membership Entry No. | Foreign key to membership table |
Valid From Date | Time frame start date (inclusive) |
Valid Until Date | Time frame end date (inclusive) |
Created At | |
Context | The context in which this entry was created. Option are;
|
Blocked | Enables blocking a membership without interrupting the membership time frame |
Blocked At | When it was blocked |
Blocked By | Initials of user that blocked membership entry. |
Item No. | Item used in sales |
Description | Description used in sales |
Membership Code | The membership code membership should have code in this time frame. The membership code on membership correctly reflects the current membership code. |
Closed By Entry No. | The time frame may be altered by another entry as the consequence of RENEW, UPGRADE, EXTEND. The causing entry is linked on the CANCEL entry |
Duration Dateformula | The original duration, as per entry creation |
Unit Price | Unit Price (from Item Card) |
Amount | Amount (discounts applied) |
Amount Incl VAT | Amount Incl VAT |
Receipt No. | NPR Reference. POS Receipt number of sales |
Line No. | NPR Reference. POS Receipt line number of sales |
Source Type | NAV reference of origin. Reserved for future use. Options are:
|
Document Type | NAV reference of origin. Reserved for future use. Option mirror the type of creating document |
Document No. | NAV reference of origin. Reserved for future use. |
Document Line No. | NAV reference of origin. Reserved for future use. |
Import Entry Document ID | (Web Service) A reference to the message that created this member card |
Anchor | ||||
---|---|---|---|---|
|
Hence, a notification may be created. The Member Notification is created preemptively and may be canceled when it is processed on the intended notification date. The entries are found in the membership card or membership list under menu Memberships.
...
FIELD NAME | DESCRIPTION |
Entry No. | Primary Key |
Membership Entry No. | Foreign Key to membership |
Member Entry No. | Foreign Key to member.
|
Notification Code | Foreign Key to Member Notification Setup |
Date To Notify | The date when notification is to be executed. |
Notification Status | Process state;
|
Notification Processed At | Date time of last processing time |
Notification Processed By User | Who executed notification |
Blocked | Prevents notification from being processed |
Blocked At | Date time of the block |
Blocked By User | Blocked by user |
Notification Trigger | From Member Notification Setup |
Template Filter Value | From Member Notification Setup |
Target Member Role | From Member Notification Setup |
Anchor | ||||
---|---|---|---|---|
|
When the Membership Notification is processed, the actual member(s) to notify are resolved. That member information is stored in this entry table along with process status information. The entries are found in the membership card or membership list under menu Memberships.
...
FIELD NAME | DESCRIPTION |
Notification Entry No. | Primary Key, Foreign key to Members Notification |
Member Entry No. | Primary Key, Foreign key to Member |
Membership Entry No. | Foreign key to Membership |
Notification Code | From Member Notification |
Date To Notify | From Member Notification |
Notification Send Status | Process state;
|
Notification Sent At | Date time |
Notification Sent By User | Sent by user |
Blocked | Blocked |
Blocked At | Blocked at |
Blocked By User | Blocked by |
Notification Trigger | From Member Notification |
Template Filter Value | From Member Notification |
Target Member Role | From Member Notification |
Notification Method | Option of Notification Method (Should be inherited From Member) |
External Member No. | From Member |
External Membership No. | From Membership |
E-Mail Address | From Member |
Phone No. | From Member |
First Name | From Member |
Middle Name | From Member |
Last Name | From Member |
Display Name | From Member |
Address | From Member |
Post Code Code | From Member |
City | From Member |
Country Code | From Member |
Country | From Member |
Birthday | From Member |
Community Code | From Member |
Membership Code | From Membership |
Membership Valid From | From Membership Entry |
Membership Valid Until | From Membership Entry |
External Member Card No. | From Member Card |
Card Valid Until | From Member Card |
Pin Code | From Member Card |
Failed With Message | If the send should fail, and if the send implementation returned a reason, it will be here. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
For a membership to be active, there should be a time frame registered for that membership. The time frame entry defines the start and end date and include some information regarding the price and in which context it was created or edited.
When a membership is created, the first-time frame is created automatically – this time frame makes the membership valid.
The member management functions operate on those time frames and create new time frames and canceling part of them accordingly.
The general rule is that two time frames may not overlap. The operations Extend and Upgrade require an active time frame and will mexodify the active time frames until date does not to violate this rule.
When an Extend or Upgrade time frame is canceled, the original time frame is restored.
Anchor | ||||
---|---|---|---|---|
|
There are 5 commands to manipulate the current time frame. There general behavior is as follows;
...
- RENEW – will add a new time frame AFTER the last time frame (back to back) when the renew action is performed while there are future time frames. Should all the time frames be valid in the past, the new time frame is added starting today.
- EXTEND – requires that there is a time frame for the extension start date and that the duration of the new time frame, extends (is valid for a longer time) the current time frame.
- UPGRADE – also requires that there is a time frame for the upgrade start date. Upgrade changes the membership code for the remaining time in the time frame. Upgrade must have a start date of TODAY. (This is because the POS price and discount structure does not allow changing something for the future)
- CANCEL- ends the current time frame on the specified date (Setup).
- REGRET – will undo the last time frame and restore the conditions of the membership to those that applied before the change that is regretted. The first time frame created for a membership may be regretted, in which case the membership cannot be reactivated again. A REGRET operation cannot be undone.
Anchor | ||||
---|---|---|---|---|
|
Two web service are available to perform the same activities as can be done from the POS;
...
The RENEW and EXTEND operates primarily on time, while UPGRADE changes the conditions of the membership. Renew and extend can be combined with upgrade functionality under the condition that new time frames start date must be from TODAY.
CANCEL will terminate the membership on the specified date.
Anchor | ||||
---|---|---|---|---|
|
Renew is used to add a new subscription period after the current period. The start date of this new period is determined when the renewal is done and the activation date formula on the setup.
Start Date of the new subscription time frame may not interfere with previously registered time frames that are not canceled.
Anchor | ||||
---|---|---|---|---|
|
The setup allows for 3 pricing strategies, but only the Unit Price applies to renew, since overlapping time frames are not allowed.
Anchor | ||||
---|---|---|---|---|
|
With the "Stacking Allowed" option, it is possible control if multiple future renewals are allowed. When true, an unlimited number of time frames may be created.
Anchor | ||||
---|---|---|---|---|
|
A grace period can be defined in order to define when the start date of the new period must occur in relation to the current period. This is useful when you want to limit which options should be selectable.
Grace period can be defined to be relative to either start date or end date of the subscription. There are date formulas to calculate the period before the date and after the date.
Anchor | ||||
---|---|---|---|---|
|
Extend is used to add a new subscription period from the current point of time. The current point of time may be skewed using the activation date formula on the setup. The overlapping part of the currently active time frame is removed.
The membership extend functionality should be seen as a recommitment from the customer to stay a customer for full new period of time.
Anchor | ||||
---|---|---|---|---|
|
The setup allows for 3 pricing strategies:
...
- Unit Price – this will suggest the unit price as set on the item card.
- Price Difference– this method will calculated the suggested unit price as value of the new time frame minus value of canceled time frame for the overlapping period plus the extended period at full price.
- Time Difference – this method will calculate the suggested unit price as the value of the new time frame, without considering the overlapping period.
Anchor | ||||
---|---|---|---|---|
|
Not applicable.
Anchor | ||||
---|---|---|---|---|
|
A grace period can be defined in order to define when the start date of the new period must occur in relation to the current period. This is useful when you want to limit which options should be selectable.
Grace period can be defined to be relative to either start date or end date of the subscription. There are date formulas to calculate the period before the date and after the date.
In the example, above, the membership may be expanded in the last 4 months of the subscriptions.
Anchor | ||||
---|---|---|---|---|
|
Upgrade as opposed to renew and extend, changes the type of membership. The upgrade applies to the remaining of the time frame. Upgrade must become valid from TODAY or the change will not be possible.
Anchor | ||||
---|---|---|---|---|
|
The setup allows for 3 pricing strategies:
...
- Unit Price – this will suggest the unit price as set on the item card.
- Price Difference– this method will calculated the suggested unit price as the value of the new time frame minus value of canceled time frame for the overlapping period.
- Time Difference – not available as there is no time extension to consider
Anchor | ||||
---|---|---|---|---|
|
Not applicable.
Anchor | ||||
---|---|---|---|---|
|
A grace period can be defined in order to define when the start date of the new period must occur in relation to the current period. This is useful when you want to limit which options should be selectable.
Grace period can be defined to be relative to either start date or end date of the subscription. There are date formulas to calculate the period before the date and after the date.
From a business case view, grace periods might not apply to upgrades when going to a more expensive product. It can however be useful when handling membership downgrades and not allowing such selections in the beginning of the membership time frame.
Anchor | ||||
---|---|---|---|---|
|
The cancel membership function is to end the current membership. Cancel cannot be performed unless there is an alteration rule setup.
Anchor | ||||
---|---|---|---|---|
|
The setup allows for 3 pricing strategies:
...
- Unit Price – this will suggest the unit price as per the original unit price.
- Price Difference– this method will calculated the suggested unit price as the value of the remaining time.
- Time Difference – will return 0
Anchor | ||||
---|---|---|---|---|
|
Not applicable.
Anchor | ||||
---|---|---|---|---|
|
A grace period can be defined in order to separate different types cancel rules. The cancel that applies in the beginning of the membership time frame might refund the sales price. As time progress, cancel might return refund value that is proportional to the remaining time.
Grace period can be defined to be relative to either start date or end date of the subscription. There are date formulas to calculate the period before the date and after the date.
Anchor | ||||
---|---|---|---|---|
|
The regret operation works as an undo. The current time frame will be undone and the preceding time frame will be restored.
Anchor | ||||
---|---|---|---|---|
|
The setup allows for 3 pricing strategies:
...
- Unit Price – this will suggest the unit price as per the original unit price.
- Price Difference – NA
- Time Difference – NA
Anchor | ||||
---|---|---|---|---|
|
Not applicable.
Anchor | ||||
---|---|---|---|---|
|
Grace period applies to the regret if setup. Consumer law might require unconditional refund during the first 14 days.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The member module can communicate with its members in regards to the following events.
...
When the notification system is activated, it is preemptive, meaning that it will create a notification with a future date. When time comes, the notification is validated, and if it is deemed to be valid, then the member is notified.
Anchor | ||||
---|---|---|---|---|
|
A sample setup for membership renewal notifications setup
...
- First notification (R30) 30 days before expiry
- If membership is renewed before notification is sent, it will be canceled and a new notification will be created for that membership (if applicable).
- If notification was sent, next notification R20 is created
- Notification is sent to the member that is First Admin
- Second notification (R20) 20 days before expiry, unless membership was renewed
- If notification was sent, next notification R10 is created
- Notifications are sent all Admin members
- Third notification (R10) 10 days before expiry, unless membership was renewed
- If notification was sent, next notification R00 is created
- Notifications are sent to all members
- Fourth notification (R00) 1 day after expiry, unless membership was renewed
- Notifications are sent to all members
Anchor | ||||
---|---|---|---|---|
|
Notifications can be activated from the systems perspective on two levels.
...
When a rule was found, a notification is created.'
Anchor | ||||
---|---|---|---|---|
|
Members can opt out from notifications by setting the "Notification Method" to blank on their member card.
Anchor | ||||
---|---|---|---|---|
|
To send E-Mails with NaviPartner Retail, one or more template needs to be setup.
...
- To create a template, navigate to the "E-Mail Templates" page from the "Member Notification Setup" page
- Click New
- Create a template like this:
- The values in curly brackets will be replaced with actual values when the e-mail is created.
- For advanced setup, see the E-Mail Setup & Template documentation
Anchor | ||||
---|---|---|---|---|
|
To automate sending of notifications, codeunit 6060136 should be added task queue.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Suggested order for setting up member
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
- Navigate Profiles (Departments/Administration/Application Setup/RoleTailored Client)
- Add a new Profile ID for Ticket & Members
- Role Center ID is 6060149
Anchor | ||||
---|---|---|---|---|
|
- Navigate to User Personalization (Departments/Administration/Application Setup/RoleTailored Client)
- Find the User ID and set/ change the Profile ID
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
To add membership sales as buttons on the POS sales form, simply add them as regular sales items on the "Sales Form". Any item defined in the Membership Sales Setup will behave as a new sale of a membership.
Hence, if we want to have a button on the POS to create new members, then we will need to add it just like an item for sale.
Behind it we need to have two major set-ups:
Item Creation:
Membership Sales Setup where the parameters for the sales of the membership are set:
Note: The it is only the Business Flow Type Membership that works in Standard solution, the rest has been developed for Transcendence.
To manage member functions from the POS, several additional command buttons must be added in the POS to control what the button should do in regards to a member.
With the Line Type set to Internal and the Filter No. set to MM_SCAN_CARD, different sub-functions can be accessible in the POS by defining the field "Parameter" according to the following table.
...
Parameter | description |
MEMBER_ARRIVAL | The will ask for the member card and register arrival on the default admission code associated with the item specified on the Membership Sales Setup |
MEMBER_ARRIVAL:: <ADMISSIONCODE> | As above, but selection the admission code after the double colon. This requires that the ticket is valid for multiple locations and the admission code is valid for the ticket. |
SET_MEMBERNUMBER | This function will ask for the member card and extract the customer number from the membership and set it in the POS. Subsequent item registrations will enjoy the benefits derived from price / discount structures defined for the customer. |
EDIT_MEMBERINFO | Operates on the POS sales line. If it is a membership POS new sales item, the information may be edited. |
LOOKUP_MS_ENTRIES | This function will ask for the member card and show all the time frames the membership has |
REGRET_MS_ENTRY | This function will ask for the member card and regret the most recent time frame. |
RENEW_MEMBERSHIP | This function will ask for the member card and show a list of the renew products that the membership is entitled to. The list contains prices and calculated dates illustrating the time frame that will result from the change. |
EXTEND_MEMBERSHIP | This function will ask for the member card and show a list of the extend products that the membership is entitled to. The list contains prices and calculated dates illustrating the time frame that will result from the change. |
UPGRADE_MEMBERSHIP | This function will ask for the member card and show a list of the upgrade products that the membership is entitled to. The list contains prices and calculated dates illustrating the time frame that will result from the change. |
CANCEL_MEMBERSHIP | The cancel function will terminate the membership on date specified by the date formula. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Membership registration and alterations are split into two distinct parts - before and after payment.
Anchor | ||||
---|---|---|---|---|
|
New sales
- During POS item registration, the POS identifies the item as being a member item
- After the POS item has been created, the member info capture dialog is displayed to capture the required member information
- On dialog exit
- On confirmation, the membership structure is created, except the membership ledger entry making it valid.
- On cancel, the POS sales line is deleted along with the records used to capture the member information
- On dialog exit
- POS is ready for new action
...
- Teller selects some functions such as CANCEL/REGRET, EXTEND, UPGRADE, UPGRADE and scans the member card
- The POS may show a member confirmation dialog (setup)
- The POS shows a list of products the membership is eligible for.
- The selected products is registered.
- The price and receipt information is captured and the member info capture objects is updated.
Anchor | ||||
---|---|---|---|---|
|
- The member info capture table is searched for entries matching the sale receipt
- The action is finalized,
- NEW
- Adds an entry to the Membership Entry table
- RENEW,EXTEND,UPGRADE
- Adds a new entry to the Membership Entry table
- Updates the current entry
- CANCEL
- Updates the current entry
- NEW
- The action is finalized,
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
To setup ticket web-services, navigate to the "Web Services" page at Departments/Administration/IT Administration/Services and register codeunit 6060126 with the service name "member_services".
In a multi-tenant environment, this must be done from the default tenant.
The following member web services are available:
Anchor | ||||
---|---|---|---|---|
|
The following services can be used to create memberships and members, update the member information and possibly block the membership from usage until it has been unblock.
...
Services | DESCRIPTION |
CreateMembership | This web service creates an empty membership using a sales item from the membership sales setup table |
AddMembershipMember | Adds members to an existing membership |
UpdateMember | Updates an existing member |
UpdateMemberImages | Updates an existing members picture |
BlockMembership | Blocks an existing membership |
Anchor | ||||
---|---|---|---|---|
|
The following services can be used to retrieve member information
...
Services | DESCRIPTION |
GetMembership | Searches and returns Membership information |
GetMembershipMembers | Searches and returns the Member connected to a membership |
GetMemberImage | Get the image for a member |
MembershipValidation | Checks if membership is active |
MemberValidation | Checks if member is blocked and membership is active |
MemberCardNumberValidation | Checks if member card is valid and membership is active |
MemberEmailExists | Check if the email address has been used on an already created and active member. |
Anchor | ||||
---|---|---|---|---|
|
Altering the memberships validity can also be performed by webservies.
...
Services | DESCRIPTION |
GetMembershipChangeItemsList | This service returns a list of items that can be used to alter the membership. The membership time frame and price is calculated in context of the active membership. |
ChangeMembership | This service executes the change to the membership as described by one of the items from the list in GetMembershipChangeItemsList service |
Anchor | ||||
---|---|---|---|---|
|
Member and tickets are integrated. It is possible to define guest tickets for members.
...
Services | DESCRIPTION |
GetMembershipTicketList | This service returns a list of valid ticket items that the member can select from, to accommodate a self-service check-in for himself including guests. |
MemberCardRegisterArrival | This services is intended for handling self-service scanning of member card number, and allowing member entry. |
MemberRegisterArrival | This services is intended for handling self-service scanning of member number, and allowing member entry. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
"Loyalty programs are proven to increase customer lifetime value by up to 30% or more by increasing visit frequency, increasing spend per visit, and winning back lost customers," - Chris Luo, VP of Marketing of loyalty technology company FiveStars.
A Customer Loyalty Program is a marketing tool used by businesses to motivate repeat customers to come back to the shop to make frequent purchases, and beat competitions, by offering some kind of reward system.
Hence, a customer loyalty program is a structured and long-term marketing effort which offers incentives to frequent customers who demonstrate a "loyal buying behavior".
In Retail Industry, these programs generally reward loyal customers with discounts, special offers, rebates, points, or giveaways.
NP Retail has developed the tool to setup various schemes. The principle is that the customer is awarded points based on certain purchase actions and these points are then consumed by converting them into discounts, special offers, rebates, points, giveaways and so on.
All the functions for managing the Loyalty Reward Programs are found in the menu:
Departments > Retail Add Ons > Members
Anchor | ||||
---|---|---|---|---|
|
The first level of configuration will be to set up a group with a common perspective or goal. In our case, it is a "Loyalty Club". The Member Community function is used to that effect.
(Refer to section Membership Community for more details on how to set it up).
For example, we can set the following group:
...
FIELD NAME | DESCRIPTION |
Code | BK - A code used to link this community with other tables |
Description | Bamse Klubben - A use description of the community |
External No. Search Order | CARDNO - An option to define what search term should be used when there is ambiguity |
External Membership No. Series | NPR_MSHIP - Number series to generate the external membership identity |
External Member No. Series | NPR_MEMBER - Number series to generate the external member identity |
Member Unique Identity | EMAIL - The member value that must be used to uniquely identify a member |
Create Member UI Violation | When a member is created and the unique identity is violated the system can react with in the following ways;
|
Member Logon Credentials | NA - Defined what term to use for logon credentials when a 3rd party member management soft is used |
Membership to Cust. Rel. | Check On - This is field is used when memberships are linked with customers. This is required in the following scenarios;
|
Create Renewal Notification | Check On - Create a notification when membership requires renewal; |
Anchor | ||||
---|---|---|---|---|
|
The Loyalty Reward Program to collect the points will vary with different businesses. We have developed the Loyalty Reward Programs that are commonly used in the Retail System. Nevertheless, it is not an end in itself. We will develop more schemes based on the client's requirements in the future.
...
FIELD NAME | DESCRIPTION |
---|---|
Code | A code used to identify the scheme; |
Description | Description of the scheme |
Collection Period | The period which determines when the customer is eligible to accumulate points. Hence the computation of the points will be based on the period for which the point will be collected;
|
Fixed Period Start | The Date formula in NAV is used to defined the period starting point based on the purchase date. |
Collection Period Length | The Date formula in NAV is used to defined the period length in which the points will be collected. |
Expired Uncollected Points | This field determine if any uncollected points will have expired and not taken into the calculation of the points for collection. |
Voucher Point Source | It is the basis to collect the points to use in the calculation of the reward.
|
Voucher Point Threshold | The minimum number of points to start the calculation for the loyalty program. |
Voucher Creation | The method to be used to create the Discount Voucher or Coupon;
|
Base Point | It is the base to calculate the value for the Discount Voucher or Coupon;
|
Amount Base | The base amount is to include or exclude VAT amount in it calculation when converting to Loyalty Currency.
|
Point on Discounted Sales | If the check box is ticked, then we will use discounted amount to calculate the points or else, it will not be taken into the calculation. |
Anchor | ||||
---|---|---|---|---|
|
DATE FORMULA | RESULTING DATE | DESCRIPTION | NOTES |
---|---|---|---|
CW | 9/29/13 (Sunday) | Returns the last date of the current week | |
CM | 9/30/13 (Monday) | Returns the last date of the current month | |
CQ | 9/30/13 (Monday) | Returns the last date of the current quarter | |
D15 | 10/15/13 (Tuesday) | Returns the next 15th of the month | |
D15 + 1M | 11/15/13 (Friday) | Returns 1 month after the next 15th of the month | Same result as 1M + D15 |
1M + D15 | 11/15/13 (Friday) | Returns 15th day after the date is advanced 1 month | Same result as D15 + 1M |
1M – 15D | 10/10/13 | Returns the date 15 days less than a full month after reference date | |
1M + 15D | 11/9/2013 | Returns the date 15 days more than a full month after reference date | |
CM +1D | 10/1/13 (Tuesday) | Returns the 1st of the following month | |
CM+1M | 10/30/13 (Wednesday) | Returns the last date of the current month advanced by one month | If the reference date had been 02/23/2013 the returned date would be 03/28/13 |
CM + D10 + 90D | 1/8/2014 (Wednesday) | Returns a date 90 days after the next 10th of the month | |
1M+CM | 10/31/13 (Thursday) | Returns the last date of the following month | If the reference date had been 02/23/2013 the returned date would be 03/31/13 |
CW+1D | 9/30/13 (Monday) | Returns the Monday of Next Week | |
CW+5D | 10/4/2013 (Friday) | Returns the Friday of Next Week | |
CW+1D+3W | 10/21/2013 (Monday) | Returns 3 Weeks from Next Monday | |
CW-1D | 9/28/2013 (Saturday) | Returns Saturday of This Week | If the reference date had been 09/29/2013 (Sunday) the returned date would still be 09/28/2013. The week starts on Monday in NAV. |
D15+WD1 | 10/21/13 (Monday) | Returns the Monday after the next 15th of the month | |
WD4 + 6W | 11/7/13 (Thursday) | Returns the Thursday 6 weeks after the next Thursday. | Imagine a vendor that ships only once a week with a long time in transit. |
Anchor | ||||
---|---|---|---|---|
|
After defining the Loyalty Reward Programs in the Loyalty Setup menu, we now need to define the method of calculation for accumulating the points. This is done in the Item Point Setup menu.
...
Note: The above rules are associated to the Loyalty Code: ADVANCE. And ADVANCE is under the Member Community: BK. Hence any member under this Member Community: BK. will benefit from ADVANCE.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
In the above paragraphs, we have seen how to set up different Loyalty Reward Programs and now we will look into how to link the member to benefit from these programs. We need to go to the Membership Setup to set up a group of members who will be associated with the Loyalty Reward Program - Code: ADVANCE under Community Code BK.
Anchor | ||||
---|---|---|---|---|
|
Menu: Departments > Retail Add Ons > Members > Setup > Membership Setup
Setting up the group of members, using Membership Setup menu:
...
FIELD NAME | DESCRIPTION |
---|---|
| |
Code | CLUB-VIP - A code used to identify this community |
Description | Bamse klubben - A use description of the membership |
Membership Type | Controls how members and memberships are related.
|
Community Code | BK - A link to the community this membership belongs to |
Loyalty Code | ADVANCED – This code determines which Loyalty Reward Program is attached to the Community Code. |
Loyalty Card | Define whether a Loyalty Card is to be issued to the member or not. It is in this screen that we make the relationship between the Community (Member Community) & the Loyalty Reward Program (Loyalty Setup) |
Customer Template Code | WEB - This code identifies a template for how the customer associated with the membership will be created. This field is required when the "Membership to Cust. Rel." field on community is checked. |
Member Information | How the member entity should be treated.
|
Blocked | The setup is blocked from usage |
Blocked At | Time of block |
Perpetual | The membership validity can be perpetual (everlasting) |
Member Role Assignment | How members are assigned their role in the membership
|
Create Renewal Notification | Create a notification when membership requires renewal |
Create Welcome Notification | Create a notification when member is created |
Membership Member Cardinality | Maximum members in a GROUP membership |
Allow Membership Delete | This options allow memberships to be deleted. |
Confirm Member On Card Scan | When a POS function requires the member card to be scanned, the member card will pop up for visual confirm. |
Account Print Object Type | The type of object used for generating printing for the account information |
Account Print Object ID | The Object ID to be developed |
Receipt Print Object Type | The type of object used for generating printing for the receipt |
Receipt Print Object ID | The object ID used for generating the printout. |
| |
The following fields defined how the member card number should be handled. The member card number is public and should not be a sequential number only. | |
Card Number Scheme | Who responsible of creating the member card number
|
Card Number Prefix | Specific prefixes can be defined (or generated by the number series) |
Card Number Length | The length is used to pad a number that is too short |
Card Number Validation | If there should be a check digit appended to end of the generated number |
Card Number No. Series | The number series used generated the base of member card number |
Card Number Valid Until | For how long a member card should be valid |
Card Number Pattern | A patter can be entered to control how the card number should be generated. A pattern consists of keywords that will create a number that is a bit more difficult to guess. Available keywords are listed below and must be included between [ and ].
|
Card Print Object Type | The type of object used for generating printing for the member card |
Card Print Object ID | The object ID used for generating the printout. |
| |
Ticket Item Barcode | This barcode is created as a sales line in environment of Ticketing. It is not used for Loyalty purpose. |
Anchor | ||||
---|---|---|---|---|
|
The next step is to set the parameters for the sales of the membership.
...
FIELD NAME | DESCRIPTION |
---|---|
Type | An option to define what type of "item" we are selling.
|
No. | The Item or Account used for membership sales |
Membership Code | Links the Membership Setup table. The item sold will create a membership of this type. |
Blocked | If parameter is not used, then it is blocked |
Blocked At | Date the block was done |
Valid From Base | An option to define how the membership time frame start date should be calculated.
|
Sales Cut-Off Date Calculation | Reserved for future use. |
Valid From Date Calculation | Date formula for activation date |
Valid Until Calculation | An option to define the duration of the membership. Options are;
|
Duration Formula | Date formula for duration |
Assign Loyalty Points On Sale | Determine whether points should be assigned when sales are done on this membership type |
Anchor | ||||
---|---|---|---|---|
|
The member for the group will be created from the "Create membership" shortcut in the Home Tab from the Membership Sales Setup.
If in the configuration of Member Community, we have set the Membership to Customer Relation to Yes, then a customer file will be created as well as the Membership Card. We can see the display of which customer is created in the list in:
Menu: Departments > Retail Add Ons > Members > Memberships
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The solution Loyalty will be available under Transcendence. The process is to attached a sale to the member while doing the sale from the POS. If the member who has a Loyalty Reward Program configured.
From the POS, use the Select Membership function to set the sale to the member:
By selecting the member number, the customer attached to the member will be selected as well.
Then we can sell an item under the Loyalty Reward Program and based on the configuration, the points will be allocated accordingly.
If we have a look at the "Memberships" card in the menu: Departments > Retail Add Ons > Members > Memberships, then we can see the statistics on the Points allocated to the member.
Note:
The points are not computed on the Member Card, but it is on the Membership Card of the member which belongs to a particular Membership. The logic is that the member is allocated points due the status he or she has as being under a membership. The Loyalty Reward Programs reward the Membership as a group and consequently a member belonging to the membership.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The reports regarding Loyalty Reward Programs are found in the Action Tab in Memberships.
Menu: Departments > Retail Add Ons > Members > Memberships
Anchor | ||||
---|---|---|---|---|
|
Based on table MM Membership 6060127 where you find all fields except Customer Name:
...
The content for one membership code should be something similar to this:
Anchor | ||||
---|---|---|---|---|
|
Similar to the previous report, but we will translate the Remaining Points to monetary value.
There are setup from several table required.
...
- Date Filter (flow filter) on Membership
- Membership Code
Anchor | ||||
---|---|---|---|---|
|
This is a plaint list of a membership points entries
...
- Date Filter (flow filter) on Membership
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
FIELD NAME | DESCRIPTION |
---|---|
Issue Coupon Module | Issuing module needs to be Member_Loyalty |
...
The coupon discount will be added in the sale and applied to the sale transaction as shown below:
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Membership Sales Setup
FIELD NAME | DESCRIPTION |
---|---|
Auto-Renew To | Item to Auto-Renew To |
...