US DSCSA · Dispensers & pharmacies

DSCSA at the pharmacy counter.

US DSCSA · §582 dispenser obligations · unit-level tracing in force · product without data is product you cannot accept.

For dispensers, DSCSA's enhanced phase turns receiving into a data checkpoint: product must arrive with matching electronic transaction data, suspect product must be quarantined and verified, and records must be producible on request. The pharmacies handling this well have made verification a scan, not a project.

DSCSA §582Dispenser dutiesEPCIS 2.0GS1 DataMatrixIn force
What the rule requires

Receiving is now a verification event.

Only product with data

Dispensers may only accept product with the required transaction information and statement — arriving electronically, matched to what is physically in the tote.

Suspect-product duties

On suspicion — wrong seal, price too good, diverted lot — quarantine and investigate, verify the product identifier, and notify FDA and trading partners if illegitimate.

Records on demand

Transaction records must be maintained and producible (six years). In an investigation, the pharmacy that can answer in minutes is a partner; the one that cannot is a suspect.

Saleable returns discipline

Returns re-entering stock need verified identifiers. The wrong-item-in-the-right-box problem is not just an aftermarket disease — it walks through pharmacy returns too.

The dates

The timeline, as it stands.

The dispenser obligations are live. The practical burden concentrates at receiving and returns — the two moments where physical product and electronic data must agree.

Dispenser tracing dutiesin force
Six-year recordsrolling
NDC-12 relabeling reaches pharmacy systemsby 7 Mar 2033
What to do now

Three moves that de-risk the deadline.

01 · Step

Make receiving a scan

Verify identifiers against transaction data at the point of receipt — a phone or dock read, not a back-office reconciliation two weeks later.

02 · Step

Write a suspect-product playbook

Who quarantines, who verifies, who files the 3911 — decided before the day it happens. FDA expects a process, not improvisation.

03 · Step

Test your recordkeeping

Pull a random six-month-old transaction and reproduce its full record. If that takes longer than a coffee, fix the system before an investigator asks.

How Aeroz fits

Verification that fits behind a counter.

Aeroz makes the physical check instant: a tap or dock read verifies a unit's cryptographic identity against its EPCIS record — no new hardware beyond a phone, no line at receiving. For pharmacy groups, the same log answers investigators, narrows recalls to exact units on exact shelves, and keeps returns honest.

FAQ

DSCSA for dispensers, answered.

What must a dispenser check before accepting product?

That product arrives with the required electronic transaction information and statement from an authorized trading partner, and that the physical product matches that data. Product without data is product you cannot accept.

What triggers suspect-product handling?

Anything that casts doubt — packaging anomalies, implausible pricing, diverted or stolen-goods signals. The duty is to quarantine, investigate, verify the identifier, and notify FDA (Form 3911) plus partners if the product is illegitimate.

How long must records be kept?

Six years, producible on request. Electronic, searchable records turn a subpoena into an export; paper turns it into a bad month.

Is this practical for a small pharmacy?

Yes — if verification is a scan rather than a project. That is the design goal of Aeroz's dispenser deployment: phone-tap verification, automatic event logging, and records that assemble themselves.

Readiness audit

Know exactly where you stand — in 14 days.

A fixed-fee Aeroz audit maps your products against dscsa for dispensers requirements and returns a written readiness assessment, a data-mapping review, and a scoped pilot plan with cost and timeline.

Fixed fee 14-day written report No commitment to proceed