HaloPSA product sync: Internal Product ID and Xero Product ID
Salesbuildr does not send Internal Product ID to HaloPSA and does not fill Halo's Xero Product ID. See which product fields are pushed, and how to set Xero Product ID on the Halo item yourself.
Written By Bram Fofana
Last updated 10 days ago
When Salesbuildr creates or updates a HaloPSA item from a product, two fields customers often expect are not sent:
- The productβs Internal Product ID in Salesbuildr is not included in the product push.
- HaloPSAβs Xero Product ID (on the item Billing tab) is left empty unless you, or another Halo workflow, fill it.
There is no Salesbuildr setting to map Internal Product ID to Xero Product ID. This article lists what is sent, and how to populate Xero Product ID yourself.
HaloPSA must already be connected. For the first connection, see HaloPSA Setup. Halo uses the term Items for what Salesbuildr calls products.
Internal Product ID is not sent to HaloPSA
Internal Product ID on a Salesbuildr product is your own reference for tracking in Salesbuildr. It is not written to any HaloPSA item field.
That is different from Autotask, where Internal Product ID is sent to Autotask. HaloPSA has no equivalent mapping.
You can still use Internal Product ID inside Salesbuildr β on the product, in search, and in imports. It simply does not travel with the Halo product push.
Xero Product ID is not filled by Salesbuildr
On a HaloPSA item, open the Billing tab. The field labelled Xero Product ID is Haloβs link from that item to a product in Xero.
Salesbuildr does not send a value for that field:
- When Salesbuildr creates an item in Halo, Xero Product ID stays empty.
- When Salesbuildr updates an item, it still does not send Xero Product ID β so a value you already entered in Halo is left as you set it.
Salesbuildr does not show an error when the field is empty. Product sync can look healthy while Xero Product ID is blank.
Income account code and Expense account code are a different mapping. Those are sent (see below). They are not the same as Xero Product ID.
What is pushed to HaloPSA
A product is sent to Halo when it is created in Salesbuildr, or when you edit a product that is already linked and Synchronize to HaloPSA is on. That toggle is on Settings β Integrations β HaloPSA β Products β Defaults. New products are still sent when the toggle is off. You can also use Synchronize to PSA on the product page. See Importing Products and PSA integration best practices.
These Salesbuildr fields are included in the product push:
For a service or labour product that is already linked to Halo, a later update does not send sell price, cost, or markup. Halo stays the source of those amounts. New items still receive the price fields above.
Account codes come from Halo first (run Synchronize or Synchronize only fields on Settings β Integrations β HaloPSA β Synchronize so the dropdowns are filled), then you map them per product group on the Account Codes tab. A code you set on the product overrides the group default. See HaloPSA Setup.
If you need Xero Product ID populated
Set it in HaloPSA. Salesbuildr will not fill it for you, and there is no toggle or field mapping for it.
- Open the item in HaloPSA.
- Go to the Billing tab.
- Enter Xero Product ID.
- Save the item.
Later product updates from Salesbuildr do not overwrite that field.
If many items need the same treatment, use a HaloPSA workflow or another process you already run in Halo β not a Salesbuildr setting.
If you expected Internal Product ID to flow through to Xero unchanged, that mapping is not available today. Keep Internal Product ID in Salesbuildr for your own reference, and maintain Xero Product ID on the Halo item.
See also
- HaloPSA Setup β connect HaloPSA, map product groups, and configure account codes
- Importing Products β Synchronize to HaloPSA and category mapping
- Product Detail β Internal Product ID, MPN, pricing, and account codes on the product
- HaloPSA opportunity custom fields and quotes β custom fields are also not synced
- PSA integration best practices β when product edits are pushed back
- Duplicate name in HaloPSA β when Halo rejects a product because the name is already in use
Was this helpful?
More in Integrations
IntegrationsPax8KPN / RoutITLeaderCloudStill need help? Ask the team