An electronics manufacturer's first serious question about Acumatica is usually about serial tracking granularity — can the system track a unit by serial number from the moment a bare PCB comes off the line through final assembly, test, shipment, and eventually an RMA three years later. The short answer: yes, and this is one of the areas where Manufacturing Edition's stock serial-tracking is genuinely solid, but the RMA/warranty side needs deliberate configuration, because it is not a manufacturing feature — it is a Case Management feature wearing a manufacturing hat.
Serial assignment through production, not just at receipt
Serial-tracked items in Acumatica get serial numbers assigned at receipt by default, but for electronics you typically want serials assigned at a specific production step — after final test, not at raw-component receipt, because a bare board is not yet a serialized unit. That means configuring the item class serial assignment method and, for many boards, generating the serial number itself rather than accepting a system-sequential one (a scanned barcode fed by your test fixture, for instance).
// Override the default serial generator so production receipt accepts
// an externally-scanned serial (from the test station) instead of
// Acumatica's auto-numbering sequence.
protected virtual void INTran_RowInserting(PXCache cache, PXRowInsertingEventArgs e)
{
var row = (INTran)e.Row;
if (row.TranType == INTranType.Assembly && !string.IsNullOrEmpty(scannedSerial))
{
row.LotSerialNbr = scannedSerial; // bypass auto-numbering
}
}
RMA and warranty: this is CRM Case Management wearing a manufacturing hat
Acumatica has no dedicated "RMA module." What most electronics manufacturers actually deploy is the Case Management screen (CR/CS) with a custom case class for returns, linked to the original sales order and the serial number via the standard Inventory serial history, plus a Return Order type in Sales Order Management (SO with an RC/RM order type) to handle the physical inventory movement — credit, replace, or repair-and-return. Warranty entitlement itself (is this serial still under warranty, based on ship date plus a warranty term) is not a stock field; I build it as a calculated field off the original shipment date on the serial's transaction history, surfaced on the case screen so support reps see entitlement status without leaving the case.
Resist the temptation to build a separate "warranty tracking" table. Every fact you need — ship date, ship-to customer, original sales order — already lives against the serial in INTran/INLotSerTran history. A parallel tracking table just drifts out of sync. Query the existing history and surface it; don't duplicate it.
IPC-class traceability expectations
Electronics contract manufacturers serving regulated end markets (aerospace, medical, automotive-grade) often need component-level genealogy meeting IPC or AS9100-adjacent traceability — which components, which reel/lot, went into which serialized unit. This is the same lot-genealogy machinery covered for chemical manufacturing, applied per serial instead of per batch: Acumatica's native BOM consumption records the lot/serial of components issued to a specific production order, and a serial-to-serial trace report (again, a custom inquiry walking AMProdItem and INTran) gives you the as-built record. Acumatica does not ship this report; every electronics client I have built it for needed it as a first-project deliverable, not a nice-to-have.
Wrapping up
Electronics manufacturing on Acumatica leans on serial tracking done right at the production step where a unit becomes identifiable, and on Case Management repurposed deliberately for RMA rather than left as generic support tickets. Neither is a checkbox in the demo — both need real configuration decisions before the first serialized unit ships.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.