Map a product to HaloPSA

This popup lets you connect a product from your distributor (Pax8, Ingram, ITCloud, Twilio, or a CSV) with a product that already exists in your HaloPSA catalog. That mapping is what tells BillingBot which Halo item should be billed every time the distributor reports that product.

When to use this screen

This screen opens from several places in the system (for example, from the list of products to be mapped or from editing an existing mapping) whenever you need to assign or change which Halo product a distributor product corresponds to. Use it both to create a new mapping and to correct one that already exists.

What it shows

• Source Product Name and Source SKU: the name and code of the product as reported by the distributor. These are read-only.
• Mapped Halo Product and Halo SKU: the Halo product currently assigned (if a mapping already exists). These are also read-only and update automatically when you confirm a new assignment.
• Available HaloPSA Products: a table with the Halo product catalog, with ID, Product Name, Description, and SKU columns.
• A search box to filter the table by name, description, SKU, or ID.
• A button to toggle the table's filter mode (menu or filter bar).

Available actions

• Search products ("Search products..." field): type any text and the table filters instantly by name, description, SKU, or ID of the Halo product.
• Assign (button on each row): assigns that Halo product to the source product you are mapping. This action saves the mapping immediately, with no additional confirmation screen. ⚠️
• Close the dialog (close icon or click outside): closes the window without applying any change if you did not click "Assign".

Step-by-step flow

1. Open the dialog from the products-to-be-mapped screen (or wherever editing an existing mapping is indicated).
2. Review the source product (name and SKU) shown at the top, and if it already had a Halo product assigned, you will see it in the "Mapped Halo Product" and "Halo SKU" fields.
3. Use the search box to find the correct product in the "Available HaloPSA Products" table. If the product you are looking for does not appear, you must first create it directly in HaloPSA.
4. Once you find it, click the Assign button on the corresponding row.
5. The system saves the mapping automatically (creates a new one or updates the existing one) and closes the dialog.
6. If everything went well, you return to the previous screen with the product already mapped.

Common errors and how to resolve them

• "This Halo product (ID: ..., Name: ...) cannot be assigned because it does not have an Accounts ID (Halo SKU). ...": the Halo product you tried to assign does not have its accounting code (Accounts ID) configured in HaloPSA. Without that data, BillingBot cannot send the charges correctly. Solution: go to HaloPSA, add the Accounts ID to that product, and try the assignment again.
• "Warning: This Halo product (ID: ..., Name: ...) is already assigned to product '...'. ...": the Halo product you chose is already mapped to another distributor product. The system warns you but allows you to continue; keep in mind that this can create ambiguous lines that you will need to resolve manually when sending the information to Halo. If this was a mistake, close the dialog without confirming and look for the correct product.
• Generic error message when saving (for example, a connection or server issue): a notice appears with the details of the error returned by the system. Check your connection and try again; if it persists, contact support with the exact message that was shown.
• Unexpected error during assignment: a notice is shown indicating that an error occurred and that it was logged for technical review. You can try the operation again; if it happens again, report the issue to support.

Related screens

• Product Mapping
• Pax8 to Halo Products
• Edit Product Mapping
• Assign Product Without SKU