Skip to main content

How to Pair Each StoreHub Pay Terminal with One POS Register

Who Is This For?

StoreHub merchants with more than one StoreHub Pay terminal and more than one POS register in the same store, who want each terminal to belong to one specific register, so a cashier can only ever charge the terminal sitting at their own counter.

Overview

By default, a StoreHub Pay terminal you add in BackOffice is available to every register in that store. That is the cheaper setup, one terminal serves the whole counter but any cashier can send a payment to it, so your cashiers have to coordinate who is using it. That setup is covered in How to Share One StoreHub Pay Terminal Across Multiple POS Registers.

If you have bought one terminal for each register, you do not want that. You want Register 1 to charge Terminal 1 only, Register 2 to charge Terminal 2 only, and so on.

You do this with the 'Registers' field on each StoreHub Pay payment option. This article shows you how.

Before You Begin

  • You have admin access to your StoreHub BackOffice.

  • The terminal is already set up and working with your StoreHub POS app.

  • You have the 'Terminal ID' for each terminal. It looks like 'AMS1-000123456789' and is printed on the back of the terminal.


How Terminal-to-Register Pairing Works

  • One StoreHub Pay payment option equals one physical terminal. Two terminals means two payment options, each with its own 'Terminal ID'.

  • Each payment option has a 'Registers' field. That field alone controls which registers can see and charge that terminal.

  • Selecting 'All Registers' means every register in the store sees that terminal and can charge it.

  • Selecting exactly one register means only that register sees it. Every other register in the store will not show it at all.

  • Pairing only holds if you set the 'Registers' field on every StoreHub Pay payment option in the store. A register keeps seeing every terminal that still has it selected.


Step-by-Step Guide

Write down your terminal-to-register pairing

Listing your terminal-to-register pairing helps you keep track of which terminal belongs to which register before you set up BackOffice.

1. In your StoreHub BackOffice, go to 'Settings', then click 'POS Registers'. The list shows the 'ID', 'POS Register Name', 'Store', 'POS Layout' and 'Activation Status' of each register.

The POS Registers page in StoreHub BackOffice, showing a table of registers with the POS Register Name column outlined in red.

2. Write out the pairing. For example:

Register (from POS Registers)

Terminal ID (back of terminal)

Payment option name to use

Counter 1

AMS1-000123456789

StoreHub Pay – Counter 1

Counter 2

AMS1-000123456790

StoreHub Pay – Counter 2

Counter 3

AMS1-000123456791

StoreHub Pay – Counter 3

Tip:

  • Name each payment option after the register it belongs to, and never give two of them the same name. The Payment Options list does not show a Registers column, so identical names mean opening each row just to work out which is which. Your Payment Method report will also show them as separate rows with the same name, with no way to tell which counter each one is.

Set the 'Registers' field on each StoreHub Pay payment option

1. Go to Settings, then Payment Options.

The Payment Options page in StoreHub BackOffice. The column header row is outlined in red, showing Payment Option Name, Type, Stores, Status and Actions but no Registers column. The Edit button on the StoreHub Pay row is also outlined.

2. If the terminal is already set up, find its 'StoreHub Pay' row and click 'Edit' in the 'Actions' column, then go to step 6.

3. If the terminal is not set up yet, click '+ Add Payment Option'.

4. Fill in the payment option:

  • 'Name': for example, StoreHub Pay – Counter 1

  • 'Type': 'Payment Terminal'

  • 'Payment Terminal Provider': 'StoreHubPay'

  • 'Payment Terminal Type': 'AMS1'

  • 'Stores': the store this terminal sits in

  • 'Terminal ID': the ID printed on the back of that terminal

  • 'Store ID': the Store ID for that terminal

New Payment Option page with Payment Terminal option.

5. Check the 'Terminal ID', 'Store ID', 'Type', 'Payment Terminal Provider', 'Payment Terminal Type' and 'Stores' before you save.

Note:

  • Once the payment option is saved, those fields become read-only. To correct any of them, you have to delete the payment option and create it again.

6. Open the 'Registers' dropdown. On a new payment option, it is usually set to 'All Registers', with every register ticked.

The Registers dropdown open in the New Payment Option window, outlined in red, showing All Registers ticked along with every individual register

7. Click 'All Registers' once to clear every register, then click the one register this terminal belongs to. Nothing else should be ticked.

The Registers dropdown open, outlined in red, with All Registers unticked and exactly one register ticked.

Note:

  • Always open the 'Registers' dropdown and set it yourself, even if it already looks correct. Never leave it empty, then BackOffice will let you save it with no register selected, and the terminal will not be paired to anything.

8. Click 'Save'.

9. Repeat steps 2 to 8 for every StoreHub Pay payment option in the store.

Important:

  • This only works if you do all of them. If you pair Terminal 2 to Register 2 but leave Terminal 1 on 'All Registers', Register 2 will still show both terminals and a cashier can still charge the wrong one.

On an existing payment option, the 'Registers' field stays editable even though the other fields are locked, so moving a terminal to a different register is a normal edit.

The Edit Payment Option window in StoreHub BackOffice. The Registers field is outlined in red and editable, while the greyed-out Terminal ID and Store ID fields are also outlined.

Sync each POS register

To update your register with the new settings from BackOffice, follow these steps on your register device:

1. On each POS register, open the main menu and click 'Sync' twice to pull the updated payment options onto the device.

The StoreHub POS main menu with the Sync option highlighted.

Check each register sees only its own terminal

To verify that your register is paired correctly, follow these steps to test the payment screen:

1. On each register, ring up a test bill and open the payment screen. You should see only the StoreHub Pay option belonging to that register.

The StoreHub POS payment screen showing one StoreHub Pay payment option.

2. If you see two, go back to 'Set the 'Registers' field on each StoreHub Pay payment option'. One of the other payment options still has this register selected.


Quick Do's and Don'ts

Do

Don't

Create one payment option per physical terminal, each with its own 'Terminal ID'.

Reuse the same 'Terminal ID' on two payment options, as BackOffice will not stop you, and both will point at the same terminal.

Set the 'Registers' field on every StoreHub Pay option, not just the new one.

Leave one option on 'All Registers' and assume the others override it.

Check the 'Terminal ID', 'Store ID' and 'Stores' carefully before the first save.

Expect to fix them later, as they lock after saving.

Give each payment option a distinct name, matching its register.

Leave two options sharing a name, as the Payment Method report will show them as two identical rows you cannot tell apart.

Sync every register after saving, then check the payment screen.

Assume the change is live on the POS without syncing.


Troubleshooting

Issue

Solution

A register still shows more than one StoreHub Pay option.

Another payment option still has that register selected, often still on 'All Registers'. The Payment Options list does not show registers, so click 'Edit' on each StoreHub Pay row and confirm only one register is ticked.

A register shows no StoreHub Pay option at all.

That register was not ticked on any payment option. Edit the option for its terminal and tick that register.

The change is not showing on the POS.

On that register, click 'Sync' twice in the POS main menu.

A payment goes to the terminal at the wrong counter.

The 'Terminal ID' on that payment option does not match the terminal physically at that register. Check the ID on the back of each terminal against the 'Terminal ID' field. 'Terminal ID' cannot be edited, so delete the payment option and create it again with the correct ID.

You need to change the 'Terminal ID', 'Store ID', 'Stores', 'Type' or 'Payment Terminal Provider'.

Those fields lock after the first save. Delete the payment option, create a new one with the correct details, then set its 'Registers' field and sync.


FAQs

1. Do I need one terminal per register?

No. One shared terminal is the cheaper setup and works fine for quieter counters. See How to Share One StoreHub Pay Terminal Across Multiple POS Registers. Pair one terminal to one register when your counters are busy enough that cashiers keep clashing on a shared terminal.

2. Can I mix the two setups?

Yes. With three registers and two terminals, you can give Terminal 1 to your busiest register and let the other two registers share Terminal 2. Tick the registers accordingly on each payment option.

3. Can two registers use the same terminal at the same time?

No. A terminal handles one transaction at a time. That is exactly the clash that giving each register its own terminal removes.

4. Will each terminal show separately in my reports?

Yes. Your Payment Method report gives every payment option its own row.

5. If I rename a payment option, what happens to my past reports?

The report shows the new name everywhere, including on transactions from before the rename. Your past rows are relabelled, not split, and your totals do not change.

6. What if I move a terminal to a different counter?

Edit that payment option, change the 'Registers' selection to the new register, save, and sync both registers. The 'Registers' field stays editable after saving.


Need Help?

Contact StoreHub Support via live chat in your StoreHub app or email [email protected].


Was this article helpful?

Let us know below or contact support for further assistance.

Did this answer your question?