Skip to main content

Approach to Configuration

Retail and POS Configuration Overview​

Slide 6

Configuration Categories​

Organisation Structure
Organisation Structure
RegionsDevicesLocationsPOS TerminalsLocation TemplatesPOS Terminal Templates
Human Resources
Human Resources
Users
User Templates
Roles
Business Rules
Business Rules
ReasonsTaxMenusFunction Auth CodesRoles
Product Data
Product Data
ProductsSelling CodesPricesSizesGroupsColoursPromotions
Tendering and Cash Management
Tendering & Cash Management
TendersCash ManagementCard TypesCard AuthorisationIIN RangesVoucher TypesGift Card Types
CRM and Loyalty
CRM & Loyalty
Customers
Customer Accounts
Customer Groups
Loyalty Scheme

Regional Configuration​

Regional
All Regions
Organisation Hierarchies
MM GroupMenu GroupProduct GroupPrice Group
Business Rules
ReasonUser TemplateRole
Country
Templates for Country
Location TemplatePOS Terminal Templates
Business Rules
ReasonTenderUser TemplateRole
Sub-Region
Warehouse A
Store A1Store A2
Store / Location
Apply / Override Configuration
LocaleCurrencyPrice GroupMenu GroupTax SchemeTax Region
POS Terminal
Apply / Override Configuration
LocaleCurrencyPrice GroupMenu GroupTax SchemeTax RegionReceipt ThemeStyle Sheet
GENERIC
SPECIFIC
Non-Regional
MenuUserReceipt
Product Data
ProductSelling CodeProduct PriceImagesColourSize
Localisation
Country CodeLocaleCurrencyTax DataTranslations

Standard Configuration​

Enactor provides several classes of configuration out of the box:

  • Base - system settings to ensure basic functionality of the application
  • Standard - key configuration data that can be used as a starting point for a new organisation, and can potentially be employed (with modifications) right through to production
  • Reference - examples of configuration and master data to be used as models for designing and building the retailer's own specific data

Configuration Templates​

Templates are available for the following entities:

  • Users
  • Locations
  • POS Terminals
  • Products

The purposes of templates include:

  • Codifying business rules
  • Providing a means of reducing configuration work where there is a large volume of similarly-configured entities
  • Simplifying integration, minimising interface data as far as possible

Note: Changes to templates affect all the entities that employ that template. Using templates is not essential, but is considered best practice for managing Users, Locations and POS Terminals.