Support Guest / Non-Member Orders

This outlines how to support the placing of Guest/Non-Member Orders within OrderAway, TouchMini and/or 3rd Party Ordering systems.

---

Subjects      ▼

• What Is It?
• Why It Is Needed?
• Who Can Do It?
• When Should It Be Done?
• Integrating To A Third Party Gaming/Membership System?
• How Is It Done?

---

What Is It?      ▲ ▼

A Guest/Non-Member Order is an Order that does not have a Member/Account assigned to it. These Orders are placed via OrderAway and/or TouchMini devices where the Allow member sign in option is not selected. They may also be placed by 3rd party Ordering systems that wish to submit Orders through to SwiftPOS, but have no Member/Account assigned to it..

SwiftPOS requires any Orders being placed to have a Member/Account assigned to them. So when Orders need to be placed for Guests, a Guest/Non-Member Member needs to be created in order for it to be used as the default Member/Account assigned to every Guest Order placed.

---

Why Is It Needed?      ▲ ▼

A Guest/Non-Member Member Record is required due to a business rule that swiftpos has in that any type of Order being submitted must have a member or account assigned to it.

---

Who Can Do It?      ▲ ▼

A person that has:

• Back Office Clerk Security access to the following menus:
  • Members > Member Records.
  • Members > Member Classifications.
• Sound knowledge of the membership systems being used/integrated to at a Venue.

---

When Should It Be Done?      ▲ ▼

The first time it's identified that Orders need to be placed which are for Guests/Non-Members, the configuration should be completed. Once the work has been completed once for a Venue, the same configuration can be used for multiple Locations within the same Venue.

---

Integrating To A Third Party Gaming / Membership System?      ▲ ▼

If a Location within a Venue is integrating to a 3rd party Gaming or Membership system (so members of these systems are recognised and may be able to accrue/redeem loyalty points), some configuration is required in these systems FIRST, prior to completing the setup of a Guest/Non-Member Member Record within swiftpos itself. Ensure that the Venue have a contact at the 3rd party company they can contact for assistance with the configuration.

---

How Is It Done?      ▲ ▼

This section outlines what is required to be done to support the following scenarios. Select one that applies to the Venue:

• No Third Party Gaming/Membership Integration
• Integration To A Third Party Gaming System
• Integration To A 3rd Party Membership system (E.G. MSL OMNIS/Virtual Manager)

---

No Third Party Gaming / Membership Integration      ▲ ▼

The creation of a swiftpos Member Classification and Member Record is required within swiftpos Back Office. To do this follow the steps below:

1. Create a Guest/Non-Member Classification
2. Create Guest/Non-Member Member

Once created, the Guest/Non-Member Member should then be used to set the value of the Member for guest orders setting in the POS tab of OrderAway and TouchMini.

---

Integration To A Third Party Gaming System      ▲ ▼

Configuration work is required in both the Gaming system as well as swiftpos Back Office. To do this follow the steps below:

• Configure the Gaming System - It is recommended that the Venue consult with the Gaming system support team to assist with this configuration.
  • Create a Gaming Tier in the Gaming system which is separate from all other Members. That is, it does NOT receive any Member benefits assigned and does NOT accrue any points. Provide this information to the swiftpos implementation team.
  • Create a Member in the Gaming system which is then linked to the same Gaming Tier created above. To do this follow the steps below:
    • Create a Member in the Venue's Gaming system with a name that adequately identifies it's existence. For example, SwiftPOS Guest/Non-Member Order.
    • Where possible, set the Member's expiry date to a date far into the future. For example, 31/12/2050.
    • Ensure a Member Card Number is generated.
    • Ensure the Member does NOT receive any Member benefits or accrue any points by assigning it to the Gaming Tier created above.
    • Provide the above Member information to the swiftpos implementation team.

• Configure swiftpos Back Office
  • Create a Guest/Non-Member Classification

• Map the Gaming Tier to the swiftpos Classification - This is done via the NetPOS Service. To do this follow the steps below:

• Map the Gaming Tier to the swiftpos Classification continued ...
  • Via swiftpos Back Office locate NetPOS General Settings.
    • Select the Backup Settings button to backup the current settings.
    • Select the Venue's Gaming system Interface from the Interfaces listed.
      • In the Field Mapping tab, ensure the Gaming Tier is mapped to the swiftpos Guest/Non-Member Classification created above.
      • In the Tiered Loyalty tab, ensure the Tiered Loyalty option is selected.
    • Save the changes and restart NetPOS.
  • Via swiftpos Back Office locate NetPOS General Settings.
    • Select the Backup Settings button to backup the current settings. This will ensure there is a Before and After backup of the settings.

• Testing - Before attempting to place a Guest/Non-Member Order, the following should be tested and confirmed that all is functioning as expected. To do this follow the steps below:
  • Testing The Gaming Guest/Non-Member Member Provided - The easiest way to do this is to swipe the Member Card (that was generated in the Create a Member step above) at any swiftpos Touch Terminal that communicates with the NetPOS service. Confirm the result of the Card swipe is successful and as expected.
  • Alternatively, testing can also be done on the POS server or site controller where the NetPOS service is installed. To do this follow the steps below:
    • On the POS server or site controller where NetPOS is installed, open Windows File Explorer and browse to "C:\Program Files (x86)\Samford Software\BackOffice" directory.
    • Locate and open the MemberValidation.exe application, then:
      • Populate the Connection Details so a connection can be made to the NetPOS service successfully.
      • Select the Get Interfaces button and wait for the application to respond.
        • If successful, check the Interface drop-down and a list of the interfaces (including the Gaming system) should exist. Select the Gaming system interface from the drop-down.
          • If the Gaming Interface has an access code populated within NetPOS, enter this into the Access Code field under the drop-down so it's able to connect successfully.
      • Populate the fields LocationId and TerminalId with valid values that exist in swiftpos Back Office.
      • Within the Member Type, select Standard which means Card Number in the context of Gaming.
      • Populate the MemberId field with the Card Number provided by the Gaming system for the Guest/Non-Member Record.
      • Select the Get Member button to test end to end communications with the Gaming system to ensure the details which have been provided, work. The Full Response will contain the result and also show whether the Classification mapping setup above is working correctly.
      • Close the application.
  • Ensuring the Guest/Non-Member Member exists in swiftpos Back Office - The final test is to ensure the Guest/Non-Member Member exists in swiftpos Back Office so it can be assigned to Guest/Non-Member Orders. Depending on the current configuration of NetPOS or the Service Monitor (specifically relating to Member Syncing):
    • If Member syncing is configured, the Member should already exist at this point and be in the right Classification. To test, do as follows:
      • In swiftpos Back Office, navigate to Member Records.
        • Search for the Member using the Member Card Number provided by the Gaming system by using the Card/Alternate ID as the search filter. The Member should be found.
          • If not, select Reset and then search again, instead this time using the Member Number as the search filter. It may be that Card Numbers are being mapped to the Member Number field at the Venue.
          • If found, confirm the Member is assigned to the correct Member Classification.
            • If it not, ensure the Member details are edited and the Member is updated with the correct Member Classification field.
              • Then repeat the previous Testing steps and ensure the Member Classification assignment is still correct. If it not, this may mean the mapping in NetPOS isn't working and will need to be troubleshooted further.
    • If Member syncing is NOT configured, the Member can be added manually in swiftpos Back Office. Refer to How To Create a Guest/Non-Member Member for more information.

Once created, the Guest/Non-Member Member should then be used to set the value of the Member for guest orders setting in the POS tab of OrderAway and TouchMini.

---

Integration To A Third Party Membership System (E.G. MSL OMNIS / Virtual Manager)      ▲ ▼

Configuration work is required in both the Membership System as well as swiftpos Back Office. If the Membership system is an MSL-owned system, a request can be sent to membership_support@mslsolutions.com for the this to be configured. If not, do as follows:

• Configure the Membership System - It is recommended that the Venue consult with the Membership system support team to assist with this configuration.
  • Create a Member Category/Type in the Membership system which is separate from all other Members. That is, it is NOT included in statistics, resignation processes etc. Provide this information to the swiftpos implementation team.
  • Create a Member in the Gaming system which is then linked to the same Gaming Tier created above. To do this follow the steps below:
    • Create a Member in the Venue's Gaming system with a name that adequately identifies it's existence. For example, SwiftPOS Guest/Non-Member.
    • Where possible, set the Member's expiry date to a date far into the future. For example, 31/12/2050.
    • Ensure the Member does NOT receive any Member benefits or accrue any points by assigning it to the Gaming Tier created above.
    • Provide the above Member information to the swiftpos implementation team.

• Configure swiftpos Back Office
  • Refer to How To Create a Guest/Non-Member Classification for more information.

• Map the Member Category/Type to the swiftpos Classification - This is done via the NetPOS Service. To do this follow the steps below:

• Map the Member Category/Type to the swiftpos Classification continued ...
  • Via swiftpos Back Office locate NetPOS General Settings.
    • Select the Backup Settings button to backup the current settings.
    • Select the Venue's Membership system Interface from the Interfaces listed.
      • In the Field Mapping tab, ensure the ClassificationID row has the AddUpdate option selected and the Map set to This Interface.
      • In the Tiered Loyalty tab:
        • Ensure the Tiered Loyalty option is selected.
        • Populate the value of the Loyalty Tier column with the ID of the Member Category/Type provided.
    • Save the changes and restart NetPOS.
  • Via swiftpos Back Office locate NetPOS General Settings.
    • Select the Backup Settings button to backup the current settings. This will ensure there is a Before and After backup of the settings.

• Testing - Before attempting to place a Guest/Non-Member Order, the following should be tested and confirmed that all is functioning as expected. To do this follow the steps below:
  • Testing The Membership Guest/Non-Member Member Provided - The easiest way to do this is to locate the Guest/Non-Member Member using the Customer POS Key (#102) at any swiftpos Touch Terminal that communicates with the NetPOS service. Confirm the result is successful and as expected.
  • Alternatively, testing can also be done on the POS server or site controller where the NetPOS service is installed. To do this follow the steps below:
    • On the POS server or site controller where NetPOS is installed, open Windows File Explorer and browse to "C:\Program Files (x86)\Samford Software\BackOffice" directory.
    • Locate and open the MemberValidation.exe application, then:
      • Populate the Connection Details so a connection can be made to the NetPOS service successfully.
      • Select the Get Interfaces button and wait for the application to respond.
        • If successful, check the Interface drop-down and a list of the interfaces (including the Membership system) should exist. Select the Membership system interface from the drop-down.
          • If the Membership Interface has an access code populated within NetPOS, enter this into the Access Code field under the drop-down so it's able to connect successfully.
      • Populate the fields LocationId and TerminalId with valid values that exist in swiftpos Back Office.
      • Within the Member Type, select Standard which means Card Number in the context of Gaming.
      • Populate the MemberId field with the Guest/Non-Member Member Number provided by the Membership system.
      • Select the Get Member button to test end to end communications with the Membership system to ensure the details which have been provided, work. The Full Response will contain the result and also show whether the Classification mapping setup above is working correctly.
      • Close the application.
  • Ensuring the Guest/Non-Member Member exists in swiftpos Back Office - The final test is to ensure the Guest/Non-Member Member exists in swiftpos Back Office so it can be assigned to Guest/Non-Member Orders. Depending on the current configuration of NetPOS or the Service Monitor (specifically relating to Member Syncing):
    • If Member syncing is configured, the Member should already exist at this point and be in the right Classification. To test, do as follows:
      • In swiftpos Back Office, navigate to Member Records.
        • Search for the Member using the Member Number provided by the Membership system by using the Member Number as the search filter. The Member should be found.
          • If it not, ensure the Member details are edited and the Member is updated with the correct Member Classification field.
            • Then repeat the previous Testing steps and ensure the Member Classification assignment is still correct. If it not, this may mean the mapping in NetPOS isn't working and will need to be troubleshooted further.
    • If Member syncing is NOT configured, the Member can be added manually in swiftpos Back Office. Refer to How To Create a Guest/Non-Member Member for more information.

Once created, the Guest/Non-Member Member should then be used to set the value of the Member for guest orders setting in the POS tab of OrderAway and TouchMini.

End of article.      ▲