What is Address Change Service (ACS)?
Address Change Service (ACS) is a USPS post-mailing service that allows mailers to receive change-of-address and other non-delivery reasons electronically instead of relying only on manual hardcopy address notices.
ACS belongs after a mailing has entered the mailstream. When a supported mailpiece generates a change-of-address or undeliverable-as-addressed signal, the operator should treat the result as feedback into the audience file, not as a one-off postal event. The useful record connects the original recipient, address, batch, campaign, returned reason, follow-up action, and date received.
How is ACS different from NCOA?
NCOA is commonly used before mailing to update lists with change-of-address data. ACS is post-mailing feedback: it reports change-of-address information or reasons a mailed piece could not be delivered when the mailpiece and ACS setup support it.
Use this simple split: NCOA helps reduce bad addresses before a batch is released; ACS helps learn from what happened after a batch was mailed. Both belong in a durable list hygiene loop because both can affect future audience eligibility, suppression, deduplication, and address review.
Operator rule: do not let ACS results live only in a download folder or mail vendor portal. Put the decision back into the customer, lead, household, or address record that will be used for the next campaign.
Where does ACS fit in a direct-mail workflow?
ACS fits after the mailing is released and before the next audience build. It turns mailstream feedback into a record that can update address data, create suppression reasons, trigger manual review, or confirm that a future mailing should use a different address state.
A practical workflow has four stages: prepare the mailing with the right address-update method and mailpiece setup, release the batch, retrieve ACS feedback when available, then write the outcome back to the list system before another campaign uses the same record.
| Stage | Operator question | Record to keep |
|---|---|---|
| Before release | Which address-update method or ACS setup applies? | Method, endorsement or barcode setup, batch ID, and owner. |
| After mailing | Did the mailpiece generate a change-of-address or non-delivery signal? | Recipient key, old address, campaign ID, and ACS result. |
| Review | Does the result change future eligibility? | New address, non-delivery reason, suppression reason, or manual-review state. |
| Next audience build | Has the feedback been applied before the next send? | Updated address state, applied date, reviewer, and exception notes. |
How do ancillary service endorsements affect ACS?
Ancillary service endorsements tell USPS how to handle undeliverable-as-addressed mail and whether the sender can receive forwarding address information or a non-delivery reason. For ACS workflows, the endorsement and service setup should be recorded with the batch.
PostalPro explains that ancillary service endorsements can provide a forwarding or new address when the addressee filed a change-of-address order, or a reason the mailpiece was not delivered. For operators, the important control is consistency: the endorsement, return address, mail class, barcode setup, and batch record should tell the same story.
This article is an operational guide, not a postal ruling. Teams using ACS should confirm the exact endorsement, class, barcode, and account requirements against USPS resources or their postal operations owner before releasing production mail.
What should operators record from ACS feedback?
Operators should record the original recipient key, old address, ACS result, new address or non-delivery reason, batch ID, campaign ID, ACS method, endorsement, received date, reviewer, and next action.
The record should answer two questions later: what did the mailstream tell us, and what did we do with that information? A change-of-address result may update a future recipient address. A non-delivery reason may create a suppression rule, manual review task, or source-system exception. A hardcopy notice may still need a separate review path because ACS does not completely replace every manual notice in every case.
| ACS output | Likely workflow action | Why it matters |
|---|---|---|
| Change-of-address information | Review and update the address state for future campaigns. | Prevents repeated use of an outdated address. |
| Reason for non-delivery | Create a suppression, exception, or manual-review record. | Stops the next campaign from ignoring the same failure signal. |
| Fulfillment file or portal download | Attach the file date and batch identifier to the audit record. | Shows when the feedback entered the workflow. |
| Manual hardcopy notice | Route to the same review queue as electronic feedback. | Keeps manual and electronic corrections from splitting the source of truth. |
How does ACS relate to Move Update?
USPS Move Update resources describe ACS, NCOA Link, and ancillary service endorsements as preapproved methods tied to address-update standards for certain commercial mailings. Operators should record the update method and date, not make unsupported compliance claims.
The safe operational takeaway is simple: keep proof that the mailing list was reviewed with the chosen address-update method before release, and keep post-mailing ACS feedback in the same address-quality history. That helps future operators understand why an address was mailed, updated, suppressed, or held for review.
What should feed back into list hygiene?
ACS feedback should feed address standardization, suppression, deduplication, source-system traceability, and future audience reviews. The output is most useful when it changes the next send decision, not just the last campaign report.
For example, a new address may need standardization and duplicate review before it becomes the surviving address. A non-delivery reason may belong in the suppression list. A mismatch between the source-system address and the mailing address may need a note in the direct mail audit trail so the next import does not overwrite the correction.
What should a Sendvo-style workflow keep visible?
A Sendvo-style workflow should keep the ACS result, source record, mailing batch, campaign ID, address state, suppression decision, and follow-up owner visible together before the next campaign uses the same recipient or household.
Sendvo is in beta, so product language should stay capability-framed. The workflow principle is stable: direct-mail systems should not treat delivery feedback as an isolated report. Address feedback should move back into the audience, proofing, batching, and audit trail that control the next mail decision.
FAQ
What is Address Change Service (ACS) in direct mail?
Address Change Service (ACS) is a USPS post-mailing service that helps mailers receive change-of-address and non-delivery information electronically. In a direct-mail workflow, ACS feedback should be treated as an address-quality signal that can update records, feed suppression decisions, and preserve audit evidence for later campaigns.
Is ACS the same as NCOA?
No. NCOA is commonly used before mailing to update address lists with change-of-address data. ACS is post-mailing feedback: it reports change-of-address information or reasons a mailed piece could not be delivered when the mailpiece and service setup support it.
What should teams do with ACS records?
Teams should save the recipient key, old address, new address or non-delivery reason, mailing batch, campaign ID, ACS method or endorsement, received date, and follow-up action. The output should update list hygiene, suppression, deduplication, and future audience review records.