Page Comparison

Identity is a separately licensed web application that is leveraged by Aspenware Commerce, Aspenware Arrival, and can be utilized by other 3rd party applications (such as your mobile resort app) as the authentication platform, enabling a single login (SSO) across various applications. Aspenware Identity integrates with your resort point of sale and all your guest engagement points to provide single sign-on and secure access to data.

...

• Implicit find me flows are more likely to catch guests who already have accounts, routing them to find their accounts and decreasing duplicate customers in your POS

• If multiple applications use Identity as an authentication platform, a guest who is logged in to Aspenware Arrival will also be logged into Aspenware Commerce and the mobile app, so they can seamlessly navigate between applications.

• More secure than standard login as Identity can require guests to reset their password if the password change date in RTP is past today’s date.

Multiple store-fronts and Identity

Aspenware Commerce can be configured to have multiple store-fronts operating from a single backend admin instance, where product configuration for the shop is done. Each storefront can have its own look and feel, language strings, custom domain, settings, products, and more. Similarly, Identity can be configured to work with multiple storefronts. A single instance of Identity can also be configured to work with multiple completely separate Aspenware Commerce stores, so that if you are logged in to one store you are logged into others, however, there are some limitations around what can be customized across store-fronts or unique shops for Identity.

If using the same identity across multiple storefronts and/or stores, the custom URL across the single instance of identity must remain constant. For example, Boyne Resorts uses a single Identity across all of its 7 resorts, so http://shop.bigskyresort.com redirects to http://id.boyneresorts.com but guests coming to this page from the Big Sky shop or Arrival see a Big Sky branded experience and language strings that correspond to Big Sky.

...

Other limitations include language strings, if two stores are operating out of a single Aspenware Commerce Instance, i.e. they share an admin backend, then they can have unique branding, but the language strings must remain the same across the stores. If two stores use the same Identity but have separate Aspenware Commerce admin instances, they can have unique brands AND language strings. For example, Boyne Mountain and Boyne Highlands, sister resorts in Michigan also use the same Identity as the other Boyne Resorts (http://id.boyneresorts.com ), however, these two storefronts share a single Aspenware Commerce Admin, so the Identity language strings for these two store-fronts are shared. In the image below, the items in yellow are shared across the store front’s views of identity, and the items in blue are unique.

...