Enabling and Setting Up Branches in HirePOS
This guide provides a complete checklist for enabling the Branches module and moving from a non-branch HirePOS setup to two or more operational branches.
It also includes a shorter process for adding another branch when branches are already in use.
Important: plan the change before enabling branches
Enabling the Branches module does not automatically move your existing items, stock or transactions into the branches you create.
Each new branch starts as an empty operational location. Existing records remain unassigned until they are allocated or updated.
If items and active transactions are not assigned correctly:
Items may not appear available at the required branch.
Incorrect availability or double-booking warnings may appear.
Sales-stock quantities may be inaccurate.
Purchases may update stock at the wrong location.
Revenue and other branch reports may be incomplete.
Maintenance and inspection availability may be misleading.
Once branch-based records are in use, returning HirePOS to its previous non-branch structure is difficult and may not completely restore the original behaviour.
Complete this process as a controlled cutover. If possible, choose a time when normal transaction entry and stock movement can be limited.
Use an unrestricted Administrator account for the setup and verification. A user restricted to one branch may be unable to see records that remain unassigned or belong to another branch.
Before you begin
Decide and prepare the following:
The name and purpose of every initial branch
Which branch represents the business’s original physical location
Which branch will be the global default
The physical location of every hire item and sales-stock quantity
Each branch’s address and contact details
Each branch’s ABN or NZBN, where applicable
Each branch’s banking details
Staff default branches
User branch or state restrictions
Xero tracking categories or MYOB jobs
Branch-specific payment or integration settings
How active bookings, invoices and other transactions will be allocated
Whether completed historical records will remain under No Branch
Whether HirePOS Support will be needed for bulk allocation
Record or export your existing item quantities and current transactions before starting. This provides a reference for checking the completed setup.
Step 1: Enable the Branches module
Go to Setup > Preferences > Modules.
Enable Branches.
Save the changes.
Enabling the module makes branch setup and branch fields available. It does not migrate any existing records.
Step 2: Create all initial branches
Go to Setup > Branches.
Select New Branch.
Enter the branch name.
Enter a short branch code if it will be used for online-store, website-booking or API allocation.
Complete the branch address, phone and email details.
Enter the branch ABN or NZBN where applicable.
Enter branch banking details if documents for this branch should show a different bank account.
Configure any available accounting tracking, payment, SMS or delivery integration settings.
Save the branch.
Repeat for every initial operational location.
The first branch is not automatically the original business or a replacement for the previous non-branch level. If the business now operates from two locations, it will normally require two branch records.
Step 3: Select the global default branch
Open the branch that should be used as the system-wide default and enable Default Branch.
Only one branch can be the global default.
The default helps prefill branch selections but does not move existing records into that branch.
Step 4: Configure staff default branches
Go to Setup > Staff.
Open a staff member.
Select the staff member’s Default Branch.
Save the changes.
Repeat for each relevant staff member.
A staff member’s default branch can be used when new invoices and purchase orders are created. It may take precedence over the global default branch.
Where a staff member is associated with a login user, ensure their email addresses match.
Do not enable user branch restrictions until the staff default branches have been checked.
Step 5: Allocate singular hire items
A singular hire item has a Quantity For Hire of 1.
To allocate one manually:
Go to Setup > Items.
Open the item.
Select its branch from the Branch dropdown.
Save the item.
Repeat this for every singular hire item.
For a large number of singular items, the Items CSV importer can update them in bulk:
Prepare an Items CSV containing the item code and branch name.
Go to Setup > Items.
Select Options > Import Items CSV.
Match existing items using Item Code.
Map the branch column to Branch.
Preview and verify the updates before importing.
The branch value must match the branch name in HirePOS.
Step 6: Allocate bulk hire items
A bulk hire item has a Quantity For Hire greater than 1.
Manually allocate a bulk item
Go to Setup > Items.
Open the bulk hire item.
Open Branch Quantities or Serial Tracking beside Quantity For Hire.
Enter the quantity held at each branch.
If serial tracking is used, assign each serial-tracked unit to its branch.
Confirm that the combined branch quantities equal the item’s total Quantity For Hire.
Save the changes.
Repeat for every bulk hire item.
Allocate a large number of bulk items
There is no standard direct CSV mapping for separate bulk hire quantities at each branch.
For a large item list, use the advanced custom-field preparation process and ask HirePOS Support to complete the branch allocation:
Import Bulk Hire Item Quantities by Branch
The process is not complete until HirePOS Support confirms that the temporary quantities have been moved into the Branch Quantities or Serial Tracking records and verified.
Step 7: Initialise and count sales stock
Stocked sales items require a separate stocktake quantity for each branch.
Create missing branch stocktake records
After all initial branches have been created:
Go to Setup > Branches.
Open a branch.
Enable Populate Branch Last Stocktake Dates/Qty’s on Save.
Save the branch.
This is normally a one-time setup process. Although the option is selected from one branch, it creates missing sales-stock records across the configured branches.
It does not copy or divide the previous business-wide stock quantity. Missing records are initialised with zero quantity, so a real branch stocktake is still required.
The option can also be useful later when many new sales items have been added without branch stocktake records. It does not replace existing stocktake records.
Enter each branch’s physical sales stock
For each branch:
Physically count the sales stock held at the location.
Go to Setup > Sales Stocktake.
Select the branch.
Create a new stocktake.
Enter, scan or import the counted quantities.
Preview the stocktake.
Check the quantities and branch.
Select Commit All.
Repeat for the next branch.
Future invoices, received purchase orders, adjustments and transfers must use the correct branch for sales stock-on-hand figures to remain accurate.
Step 8: Update active sales and hire records
Once hire items have been correctly allocated, assign the relevant current and future sales/hire records to their branches.
Prioritise:
Current on-hire invoices and contracts
Future bookings and reservations
On-hold transactions with active dates
Other non-cancelled records that currently or later reserve hire stock
Quotes and estimates if Include Quotes is enabled for availability
To update a record:
Open the quote, booking, invoice or contract.
Select the correct branch.
Save the record.
Review its availability warnings.
Changing the invoice branch does not:
Reassign its items
Change associated payments
Change maintenance or inspection records
Create a branch transfer
The record will begin checking availability against the branch selected on it. If the required items have not been allocated to that branch, availability warnings may appear.
Credit notes do not consume hire availability.
Step 9: Decide how to treat historical invoices
Completed historical invoices do not have to be allocated before branches can be used.
Choose one of the following approaches.
Leave historical invoices under No Branch
This is generally acceptable if the business understands that:
Earlier sales remain reported under No Branch.
The history of the original physical location consists of its new branch activity plus the older No Branch activity.
New transactions must be consistently assigned to branches.
Ask HirePOS Support to allocate the history
HirePOS Support can bulk-allocate existing records to one nominated branch. This can make historical reporting for the original location easier.
This is a broad bulk update and is not intended for selectively dividing individual historical transactions among several branches. Contact HirePOS Support to discuss the required scope and allow time for the update.
Step 10: Review purchase orders
Purchase orders should be assigned to the branch receiving the stock.
Review:
Open purchase orders
Partially received purchase orders
Recently received purchase orders where stock levels must be attributed correctly
Be careful when changing the branch on a purchase order that has already received sales items. Changing the branch moves the associated received-stock effect from the previous branch to the new branch.
For example, changing a purchase order containing four received items from Branch A to Branch B reduces Branch A’s calculated stock by four and increases Branch B’s stock by four.
Confirm where the stock was physically received before changing the branch.
Step 11: Review payments
Payments have their own branch and are not automatically tied to the invoice branch.
An invoice for Branch A can legitimately have a payment recorded against Branch B, such as when the customer pays at a different physical location.
Changing an invoice’s branch does not change its payments.
Review existing payments where branch reporting is important. New payments may default to the logged-in user’s staff branch, but users should still check the branch before saving.
If separate PIN Payments accounts are used for different branches, review the dedicated Branch-Specific PIN Payments Accounts guide before processing or storing cards.
Step 12: Review active maintenance and inspections
Active maintenance records and unfinished inspection checklists can affect item availability.
Prioritise records that are:
Currently active
Pending with no confirmed finish date
Scheduled for future dates
Associated with items required for upcoming bookings
Older completed maintenance and inspection records can generally be reviewed or cleaned up later if required for branch reporting.
For bulk hire items, check that the maintenance Service Branch or Inspection Branch matches the location whose availability should be affected.
For singular hire items, active maintenance or inspections can affect the item’s availability regardless of the branch selected on the maintenance or inspection record.
Step 13: Enable branch requirements
After branch defaults, stock allocations and active records have been reviewed:
Go to Setup > Preferences > Restrictions.
Enable the required branch settings for:
Invoices and related sales/hire records
Payments
Purchase orders
Maintenance and inspections
Save the changes.
These restrictions prevent new records from being saved without a branch.
If sales stock is physically managed by location, ensure Disable Sales Stock Control at Branch Level is not enabled under the miscellaneous preferences.
Step 14: Configure user restrictions
After each staff member’s default branch has been confirmed:
Go to Setup > Preferences > Users.
Open the required user.
Enable the restriction to the user’s default branch or state.
Save the changes.
Ask the user to log out and back in.
Restricted users may be unable to see unassigned records or records belonging to other branches. Use an unrestricted Administrator account for final migration checks.
Step 15: Verify the cutover
Do not assume the setup is complete because the branches and visible stock quantities look correct.
Check sales and hire records
Go to Sales/Hire > Find Sales/Hire.
Use the cog menu to display the Branch column.
Use a suitable date range.
Sort or filter the Branch column.
Review records with a blank branch.
Confirm that all current and future availability-affecting records are assigned correctly.
Check singular hire items
Go to Setup > Items.
Display the Branch column.
Sort or filter the list.
Review singular hire items without a branch.
Check bulk hire items
There is no complete standard report showing all bulk hire quantities that remain unassigned.
Ask HirePOS Support to reconcile each item’s total Quantity For Hire against the quantities allocated to branches, particularly after a large migration.
The Hire Stocktake screen only shows stock already allocated to the selected branch. It cannot confirm that every bulk quantity has been allocated somewhere.
Check sales stock
Run the applicable sales-stock-on-hand reports by branch and compare the results with the physical quantities at each location.
Check payments
Go to Home > Payments > Find Payments.
Clear the Branch filter.
Select a sufficiently broad date range.
Sort the displayed Branch column.
Review payments with a blank branch.
Check purchase orders
Run Reports > Purchase Orders > Purchase Orders by Branch.
Purchase orders without a branch appear in a blank branch group.
Check maintenance records
Go to Home > Maintenance Records.
Clear the Service Branch filter.
Sort the Branch column.
Review active records with a blank branch.
There is no reliable standard aggregate screen for finding every inspection checklist without an Inspection Branch. Ask HirePOS Support for assistance if existing inspections require a complete reconciliation.
Step 16: Test normal branch workflows
Before completing the cutover:
Create or inspect a booking for each branch.
Confirm that it checks the correct branch’s hire availability.
Test a known double-booking scenario.
Preview an invoice or quote for each branch.
Confirm the branch name, address, ABN/NZBN and banking details.
Check any custom invoice, quote or docket templates.
Confirm that purchase orders use the correct branch.
Confirm that sales-stock quantities change at the correct branch.
Check payment branch defaults.
Test General user branch restrictions.
Run hire stock, sales stock and sales reports by branch.
Correct any unexpected results before normal processing resumes.
Adding another branch when branches are already in use
When adding a branch to an existing multi-branch HirePOS setup:
Plan the new branch and its required details.
Create the branch.
Configure its identity, banking, accounting and integration settings.
Assign relevant staff and configure user access.
Use Branch Transfers to move existing hire or sales stock from another branch.
Allocate any newly created bulk hire quantities.
Establish the branch’s sales-stock opening quantities.
Assign relevant bookings, invoices and purchase orders.
Enable or confirm branch-required restrictions.
Test documents, availability, payments, stock and reporting.
Use Branch Transfers when existing physical stock moves between established branches. This preserves the movement history instead of simply replacing the previous branch allocation.
Other areas to review
Depending on the features your business uses, also review:
Xero tracking categories
MYOB jobs or tracking categories
Branch-specific PIN Payments accounts
Bank accounts and payment defaults
Online store branch filtering
Website bookings and API branch codes
SMS settings
Delivery integrations
Custom reports and document templates
Reminder branches
Maintenance reminders have an independent Reminder Branch. A new reminder defaults to the logged-in user’s staff branch, not the maintenance record’s Service Branch. Check the Reminder Branch when creating reminders for work at another location.
Ongoing branch management
After setup:
Check the branch on new transactions.
Receive purchases into the correct branch.
Use Branch Transfers when stock physically moves.
Keep staff defaults and user restrictions current.
Review branch stock and sales reports regularly.
Check branch allocation when troubleshooting availability or stock discrepancies.
A consistent branch selection process is essential for reliable availability, stock control and reporting.
