Configure your POS access URL
On this page
Add a store variable to create a URL that staff use to reach the POS. You only need to do this once per store, when you first set POS up.
Choose a path or a subdomain
Both options work the same way once set up. Choose before you start:
- A path off your store’s domain (
shop.example.com/pos) if you would rather not manage a POS subdomain through your DNS provider. - A subdomain (
pos.shop.example.com) if you want the POS on its own hostname. This requires a DNS record for the subdomain.
Option 1: add a path off your store’s domain
- Open your Store record in Salesforce.
- Go to Key Relationships > Store Variables and select New.
- Enter the variable details:
- Name:
POS Path - Key:
pos_path - Value:
pos
- Name:
- Select Save.
Staff can now sign in to the POS at shop.example.com/pos.
Option 2: use a subdomain for POS access
- Open your Store record in Salesforce.
- Go to Key Relationships > Store Variables and select New.
- Enter the variable details:
- Name:
POS Subdomain - Key:
pos_subdomain - Value:
pos
- Name:
- Select Save.
Staff can now sign in to the POS at pos.shop.example.com.
Keep POS devices on their current host when the storefront moves
Use this process when you move the storefront to a new domain but want POS devices to keep using the address they use now. Sign-in, outlet selection, and synced data are retained only while the device stays on the same host, so moving devices to a new domain means signing in and syncing every device again.
The pos_domain store variable keeps the store available at one extra host, the address your devices use now. That host serves the same things as before: the POS at <host>/<pos_path>, and storefront pages at every other address on the host.
Before you start
- The store has a
pos_pathstore variable, and devices reach the POS at<current host>/<pos_path>, for exampleshop.example.com/pos. A device that opens the POS at the root of a subdomain (Option 2 above) stops reaching the POS once the domain moves, because the root of apos_domainhost serves the storefront. Move those devices to the path address first. - The host the devices use has a Web Domain record with a Status of Success. If the host is the store’s current domain, the record already exists. Keep it after the move, because deleting it takes every device offline. For a host that is not yet connected, see connect a domain to StoreConnect.
- The new storefront domain is connected and ready to go live. See set your store domain and go live.
- The store does not share the storefront domain with other stores. If several stores share the domain, contact support before you set this up.
Set the POS host
Do these steps in order. Set the variable before you change the store domain.
- Open the Store record.
- Go to Key Relationships > Store Variables and select New.
- Enter the variable details:
- Name:
POS Host - Key:
pos_domain - Value: the host only, with no
https://, path, or trailing/. For example,shop.example.com.
- Name:
- Select Save.
- Change the Store Domain Name on the Store record to the new domain, as described in set your store domain and go live.
The variable has no effect while the value matches the store’s own domain. It starts working when the Store Domain Name changes, so check the value carefully before step 5: a value with a scheme or a path never matches.
For example, to move the storefront from shop.example.com to www.newbrand.com while devices stay on shop.example.com/pos, set pos_domain to shop.example.com and then set the Store Domain Name to www.newbrand.com.
After the domain change, open https://shop.example.com/pos in a browser. The POS sign-in page loads, and the storefront loads at https://www.newbrand.com.
Storefront pages and links on the POS host
The POS works on the POS host as before. These points cover the storefront pages that still load on that host, and the links that POS devices create for shoppers.
- Storefront pages still load on the POS host. They are not redirected to the new domain.
- A cart a shopper starts on the POS host does not persist between pages. Order and payment pages reached from older links still load.
- Links a POS device builds for shoppers, such as the pay by link QR code and order links, use the POS host. If the store uses reCAPTCHA, add the POS host to the reCAPTCHA key (see add reCAPTCHA to your checkout). If the store uses Apple Pay or Google Pay, verify the POS host with the payment provider as you did for the store domain (see express checkout).
- Each store takes one
pos_domainvalue, and each host belongs to one store.
Access a POS register via URL
To check the URL works, go to it in a browser. The POS sign-in form opens, with Username, Register code, and Pin code fields. To pair the browser with a register, see Connect a POS register.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.