Vertical SaaS · Saas

Medical Device Distribution Vertical on Acumatica

Medical Device Distribution Vertical on Acumatica: a practical Acumatica fit review focused on identity, minimum-necessary access, auditability, consent, and integration boundaries. It separates documented product capability from configuration, integration, and customisation work.

John Kihiu12 min read

A medical device manufacturer I worked with in Nairobi made a point of telling me, in the first scoping call, that their previous ERP had "traceability" as a checkbox feature nobody had actually tested against a real recall. That is the bar for this vertical: it is not enough to store a lot number, you need to be able to answer "which finished units, at which customers, contain component lot X" inside the hour a recall notice lands on your desk. Acumatica's Manufacturing Edition genuinely earns its keep here — this is one of the verticals where I can recommend it without a paragraph of caveats.

Lot genealogy is not an add-on, it is the data model

Acumatica tracks lot and serial numbers natively through the Lot/Serial Class configuration on inventory items, and — critically for device manufacturers — that tracking survives through production. When a work order consumes lot-tracked components into a lot-tracked finished good, the resulting genealogy links are queryable: given a finished-good lot, you can trace every component lot that went into it, and given a component lot, every finished-good lot it touched.

BQL · GENEALOGY TRACE
SELECT INTran.LotSerialNbr, INTran.InventoryID, INTran.RefNbr
FROM INTran
JOIN AMBatch ON AMBatch.OrderNbr = INTran.RefNbr
JOIN AMBomTran ON AMBomTran.OrderNbr = AMBatch.OrderNbr
WHERE AMBomTran.LotSerialNbr = @componentLot
  AND INTran.TranType = 'IN' -- finished-good receipt

That query (simplified — the real genealogy chain in production code walks AMBomTran and AMProdItem across multiple operations) is the difference between a recall that takes an afternoon and one that takes a week of grepping through paper batch tickets.

UDI: real requirement, custom implementation

If you sell into the US market, FDA's Unique Device Identification rule means every device needs a UDI on its label, tied to a GUDID submission. Acumatica has no native UDI module — I want to be direct about that rather than imply otherwise. What it has is the raw material to build one: lot/serial classes for the device identifier and production/expiry components of a UDI, custom fields on the Stock Item screen for the GTIN/device identifier portion, and a Report Designer label layout that concatenates the fixed and variable UDI segments with a barcode control. I have built this as a thin customization project three times now; it is a few days of work, not a platform gap.

Do not assume regulatory certification transfers

Acumatica being SOC 2-audited and running on Azure/AWS infrastructure says nothing about your device's regulatory status. ISO 13485 quality system requirements, FDA 21 CFR Part 820, and UDI/GUDID submission are your company's compliance obligations, not the ERP's. Acumatica can be the system of record for the traceability data those regimes require, but the quality management system sits alongside it — usually as a separate QMS product integrated via the REST API, not built inside the ERP.

Choosing serial over lot for implantables and Class III devices

The distinction matters more here than in most industries. Lot tracking groups a manufacturing batch; serial tracking gives every physical unit its own identity. For a Class I disposable, lot tracking with FEFO (first-expired-first-out) issuing is proportionate and keeps transaction volume sane. For an implantable or a Class III device, I push clients toward serial tracking even though it is heavier on the data entry side — a recall or adverse event report naming one serial number, not a lot of eight hundred units, is a materially smaller problem for the patient and the business.

Wrapping up

Medical device is one of the few healthcare-adjacent verticals where I recommend Acumatica's core manufacturing and inventory functionality with real confidence — lot genealogy, FEFO issuing, and serial tracking are native and solid. UDI labeling and formal QMS certification are not native, and I would tell any client that up front: budget for a labeling customization and treat quality management as a separate, integrated system.

John Kihiu
Acumatica ERP Developer · Laravel Engineer

Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.