We are looking for advice on how to handle custom-configured instruments in Acumatica.
We purchase assemblies/instruments where the hardware may share the same base inventory ID or vendor part number, but each unit has a project-specific tag or configuration known at the time of purchase. Today, we can assign serial/lot information at receipt, but we have not found a good way to capture the tag/configuration at PO creation so it stays tied to the PO line through receiving.
Example:
We may order three pressure transmitter assemblies from the same vendor.
All three use the same Acumatica inventory ID:
ASH ASSEMBLY
However, each assembly is configured for a different project tag:
| PO Line | Inventory ID | Project | Tag / Configuration | Real Serial Number |
| 1 | ASH ASSEMBLY | 2593001 | PT-101 | Unknown until receipt |
| 2 | ASH ASSEMBLY | 2593001 | PT-102 | Unknown until receipt |
| 3 | ASH ASSEMBLY | 2393001 | PT-101 | Unknown until receipt |
At the time of purchase, Purchasing already knows the project and tag/configuration. But because all three lines use the same inventory ID, Acumatica treats them as the same item until Receiving enters a serial/lot value.
The challenge is that the project tag is not necessarily the manufacturer's serial number. The assembly may also not have one overall serial number, even though one component inside the assembly may have its own serial number.
Ideally, we would like Purchasing to enter the project tag/configuration on the PO line, then have Receiving confirm or add the real manufacturer serial number later.
Has anyone solved this “same part, different configuration/tag” issue in Acumatica?
Our main goal is to capture the tag/configuration at purchase time and carry that information through receipt, while still allowing us to track the real serial number where needed.
Appreciate any advice or even suggestions for third-party solutions.