QuickBooks-synced lists and the Mailchimp SMS age check that only opens at signup

QuickBooks merchants in the beer, wine and spirits trade keep hitting the same wall with Mailchimp’s text marketing. Age verification for SMS subscribers can only be switched on while a brand new SMS program is being enrolled. Once a program is live, the option is gone. Lists synced over from QuickBooks sharpen the problem, because a typical customer record carries no date of birth at all.

The check covers every way in

Mailchimp applies the age check at every point a contact can join an audience: signup forms, file imports, the API and manual additions. The system works out each contact’s age from the birthdate supplied at signup, using the phone number’s country code to set the legal threshold for that country. The birthdate itself is not stored. Mailchimp keeps only a flag marking each contact as eligible or excluded.

Why do QuickBooks contacts fail?

A QuickBooks customer list is built for invoicing. It holds names, addresses and balances, not birthdates. When that list lands in Mailchimp, the age check has nothing to work with. A contact whose birthdate is missing, or whose check fails, is saved with a non-subscriber SMS status. That person can stay on your email list, but text campaigns never reach them.

Contacts who sign up through a form and enter a valid birthdate clear the check normally. The gap sits with imported records. For a brewery or a bottle shop that grew its audience in QuickBooks, the effect is quiet: nothing breaks and no error appears. A large share of the synced list simply never gains SMS consent, and it stays that way until real birthdates are collected.

The signup-only rule

The second half of the trouble is the rule itself. Age verification can be selected only during the initial enrollment of a new SMS program. An active program cannot be converted into an age-gated one afterwards. The single exception covers accounts whose SMS application was refused earlier; they can enable the check when they reapply.

Merchants who started texting first and thought about compliance later are left with a choice. Keep the current program without age checks, or wind it down and enroll afresh. We found no settings toggle, no retrofit and no workaround that adds the check to a live program. Anyone planning a text campaign for an alcohol range should treat that constraint as fixed.

Who the feature is for

It is aimed at alcohol businesses such as breweries, vineyards and liquor stores. It requires a Standard, Essentials or Premium plan with the SMS add-on active. Enrollment also means accepting Mailchimp’s policies, together with the laws, regulations and carrier requirements that apply where your contacts live. A program that drifts outside those rules risks suspension or termination of the account.

Mailchimp does not decide what counts as lawful proof of age in your market. The tool records only that a contact passed or failed. Weigh whether that method satisfies the rules governing your own licenses before you rely on it.

Switching the check on

The option lives inside the enrollment flow rather than a settings page. You open the SMS section and begin a new enrollment. At the business information step you select retail as your category, then declare alcohol-related content at the use cases step. The age verification choice sits within that same signup sequence.

Because the decision is made once, make it deliberately. Before any customer data moves, work out how your jurisdiction expects age to be verified and how your audience will supply birthdates. A list built in QuickBooks will not do that on its own, so plan a consent form or signup page that collects the details at the source.

The takeaway

The order matters more than anything else here. Decide how you will collect proof of age, enroll the SMS program, then sync or import. Follow that sequence and a QuickBooks audience stays textable. Reverse it, and most of the list waits on the email side until birthdates arrive one by one.