Application File Imports Release Notes Sync Web Services FAQ

Transaction Type

System LocationAdmin / Transaction Types

transaction type acts a governing template for transactions.  This allows for transactional information to be entered into the system in a specific manner by utilizing a different transaction name, transaction point formula and other configurable options.  Furthermore, specific transaction types can be isolated for use in segments and promotions.

For example, instead of having a single transaction type for retail transactions at one location, different transaction types can be setup to distinguish between a "gift shop purchase" and a "restaurant purchase".  Alternately, different locations could be setup to accommodate this.

Furthermore, upon initial transaction type configuration, the control method for transaction types must be configured.  This control method segregates transaction types in how they are utilized, as well as maintained in day-to-day operations. 

Note: When working in a new instance, be sure to configure transaction types before transactions occur. If transactions occur before their associated transaction types are configured, configured transaction types will be ignored for that specific date of occurrence.

Managing Transaction Types

To create a new transaction type, click the "Add Transaction Type" link at the top of the page.  It is a good practice to only create new transaction types when necessary as a large amount of transaction types can make system management much more difficult.

Alternately, to manage an existing transaction type, click the "Edit" link within the grid for the associated transaction type.  A transaction type can also be deleted from the edit page, in the event that it is unused.

The initial two text boxes require input detailing the transaction type name, and external reference.

 

Transaction Type

The below option is used to categorize the transaction type, which governs its usage and also its inclusion in some statistics.

  • Purchase Transaction - Used for "Point-of-Sale" transactions, typically for purchases and returns.
    • Location/Day Pairs - Offers the flexibility for the transaction point formulas, profit formulas, and rules to be modified on a per-day, per-location basis within the Calendar menu.  Although this is the most customizable transaction type for daily usage, it can also be the most labor-intensive to maintain.
    • Stand-Alone (Manual Entry or Importing) -  Does not offer the flexibility offered by the location/day pair. It will inherit the formulas and rules specified on this page.
  • Promotional Transaction - Only for use within transaction-based promotions.
  • Miscellaneous Transaction - Used for non-"Point-of-Sale" transactions, typically for point-only transactions.
    • Location/Day Pairs - See above definition for Location/Day Pairs.
    • Stand-Alone (Manual Entry, Importing or Point Transfers) - See above definition for Miscellaneous Transaction.
  • Survey Transaction - Only for use within the Survey menu and its related functionality.

 

Analytics Settings

These options affect the influence of the transaction type on the RFM metric and various Analytics pages.

  • Transaction Type to be used when counting a 'Visit' or 'Trip' - In Analytics pages where visits or trips are referenced, this option affects this transaction type's influence on related statistics.
  • Transaction Type to be used when counting a 'Active' Player - In Analytics pages where players are referred to as "active", this option affects this transaction type's influence on related statistics.
  • Use In 'Recency' Calculation for RFM - If enabled, the transaction type influences the recency component of RFM.
  • Use In 'Frequency' Calculation for RFM - If enabled, the transaction type influences the frequency component of RFM.
  • Use In 'Monetary' Calculation for RFM - If enabled, the transaction type influences the monetary component of RFM.

Monetary

For transactions controlled by location/day pairs, or stand-alone settings, these options affect monetary-related components of the transaction.

  • Requires Transaction Value - If enabled, transactions of this type must be accompanied by a currency value.
  • Disable Transaction Value - If enabled, transactions of this type will be entered with a value of $0.00, unless a value is forced by external means (web services).
  • Uses Win Amount - If enabled, transactions of this type will allow for entry of winnings.  Only specialized transactions and entry methods support this functionality.

Manual Entry Settings

The manual entry setting will affect users' ability to issue a manual transaction via the Clienteling Services page.

No Point Formula - Direct Entry

If enabled, transaction point formulas will not be used and the exact point amount will accompany the transaction.  Note, that this will be the base point amount, before any active bonus promotions.

Store Booking Date

If enabled, booking date can be stored within transaction data if supported by entry method.

Enforce Maximum Base Point Limit Per Transaction

If enabled, transactions for this transaction type will be rejected if the base point amount exceeds the amount configured here.

Product Settings

If enabled, transactions of this type will be accompanied by product-specific data.  Only specialized transactions and entry methods support this functionality.  Optionally, limited product information can be displayed in "Quick Details" columns in member activity grids.

Transaction Entry Issues Club Enrollment

If enabled, any recipient of this transaction will be added to the specified club.

Default Point Formula

The transaction point formula defines the amount of points received as a result of a transaction.  This particular formula setting serves as the primary formula for transactions controlled by stand-alone settings and serves as the master default for transactions controlled by location/day pairs.

Within location/day pairs, this formula is only used when a new location is created, so it is a good practice to maintain this.  Any changes to this will be propagated to the location defaults if the associated "Update" checkbox is checked upon saving.

Note: In transaction types with product item-level details where baskets are processed, formulas are applied at the product item level.  This includes flat-rate point formulas.

Default Profit Formula

The transaction profit formula defines the amount of approximate profit earned by the organization as a result of a transaction.  This transaction profit formula serves as the primary formula for transactions controlled by stand-alone settings and serves as the master default for transactions controlled by location/day pairs.

Within location/day pairs, this formula is only used when a new location is created, so it is a good practice to maintain this.  Any changes to this will be propagated to the location defaults if the associated "Update" checkbox is checked upon saving.  Product item-specific profit can be forced in at the product level regardless of profit formula setting, which may cause a mismatch between transaction profit value and cumulative product profit value.

Default Rule

The transaction issue rule defines limitations on how many times that transactions of this type can be issued on a per-member basis.  This rule serves as the primary rule for transactions controlled by stand-alone settings and serves as the master default for transactions controlled by location/day pairs.

Within location/day pairs, this formula is only used when a new location is created, so it is a good practice to maintain this.    Any changes to this will be propagated to the location defaults if the associated "Update" checkbox is checked upon saving.

Descriptors

    Main Article: Descriptor

Optional descriptors may exist for selection.

 

Please note: All external ALP SaaS links and references are directed to US datacenter unless specifically noted.


Tags:
Home: Aimia Loyalty Platform SaaS Wiki
Copyright © 2019 Aimia Inc. All Rights Reserved.
What's new: Recently changed articles