Beverage Alcohol Compliance Software: What Happens When a Price Posting Misses the Deadline

Why one missed filing stops selling, and nothing else in software works like that

It is the last week of the month and the compliance manager at an importer is working through a list. Each row is a state, a brand, a size and a price for next month's posting period. Several states operate price posting or post and hold regimes where a schedule has to be filed with the state authority and become effective before you may sell at that price, with the filing window closing on a specific day. Miss it and you do not get a warning letter. You simply cannot sell that item in that state at that price for the period.

This is what makes beverage alcohol different from every other compliance category we build in. In most industries a compliance failure is a fine and a remediation plan. Here it sits directly on revenue. An unregistered brand cannot be sold. An unposted price cannot be charged. A shipment to a retailer whose licence lapsed is a violation, and the retailer will not tell you their licence lapsed.

There are good products. Sovos ShipCompliant is the market standard, particularly for direct to consumer shipping and product registration, and its rules content is deep and maintained, which is genuinely hard work that we would not advise anyone to replicate. Park Street combines software with back office services for importers and suppliers. Avalara handles tax determination well. The gap is not in the rules library. The gap is that the rules library sits beside your order entry rather than inside it, and the moment that matters is when a rep quotes a price on a phone in a parking lot.

Problem 1: the registration matrix is bigger than anyone thinks

Your compliance obligation is not per product. It is per product, per state, per label version, per size, and sometimes per supplier or brand owner. A portfolio of 300 SKUs across 20 states is thousands of registration records, each with its own effective date, expiry and renewal rule, because some states renew annually, some biennially, and some registrations persist until something changes.

The word changes is where it bites. A supplier reformulates, moves the alcohol by volume by half a point, redesigns the front label or changes the bottle size. That is a new federal label approval and, in many states, a new registration. If the sales team starts selling the new packaging before the registration lands, you are selling an unregistered product, and the person who caused it had no idea a label refresh was a compliance event.

What a custom build does: model the SKU, the label version and the registration as separate linked records, so a label change creates a new version that is explicitly not registered anywhere until it is. Then the calendar generates itself: renewals, expiries and pending applications with owners and due dates, and a queue that tells you what is at risk this month rather than a spreadsheet somebody has to read. Supplier label change notifications feed the same queue, so the compliance team learns about a packaging update from the system rather than from a case arriving in the warehouse.

Problem 2: price posting is a deadline engine, not a document

In posting states the schedule is a filing with a window, an effective period and a format the state dictates. Some regimes allow competitors to view filings and respond within a defined period, which means your posting is a commercial decision as well as a compliance one, and it has to be made before you know what anyone else did.

Rules content platforms will tell you the deadline. What they do not do is know that your supplier confirmed a cost increase yesterday, that your commercial team has not yet decided the new front line price, and that the window closes on Thursday. So the deadline is tracked in one place and the decision is made in another, and the coordination is email.

What a custom build does: run the posting calendar as a workflow with the commercial decision inside it. Each posting period generates a task list per state with the items due, pre-populated with the current price, routed to whoever must approve a change, with a hard cutoff before the state deadline. Escalation fires early, not on the day. After filing, the effective prices become the reference that order entry uses, so what was posted and what can be charged are the same data rather than two versions of the truth. When a state acknowledges or rejects a filing, that status attaches to the record, because an assumed filing and an accepted filing are different things and only one of them lets you sell.

Problem 3: the check has to happen where the order is written

A rep is in a retailer's back room. They quote an item and a price, take an order on a tablet, and it flows into the ERP (Enterprise Resource Planning). Three questions needed answering at that moment. Is this item registered in this state today. Is this price the posted price for this period. Is the buyer's licence valid, unsuspended and of a type permitted to buy this product.

What a custom build does: expose the compliance state as a service that order entry calls before the order is accepted, returning allowed, blocked with a reason, or requires approval. Blocking a rep is a delicate thing, so the message matters: this item is not registered in Ohio, expected approval date the eighth, contact named person, is far better than a generic error that teaches reps to work around the system. Licence validation runs against state licence data where it is published, with a status and a last verified date on every trade customer, and a rule that an expired licence blocks shipment rather than generating a report somebody reads later.

Problem 4: reporting is a second full time job

Federal excise reporting to the Alcohol and Tobacco Tax and Trade Bureau on its own schedule. State excise and volume reports on theirs, in their formats. Direct to consumer shipping reports where you hold those permits, with per consumer and per state volume limits that have to be enforced at the point of sale (POS) rather than discovered in a report. Then supplier depletion reporting, which is not a legal requirement but is a contractual one, and in most distributors it consumes as much manual effort as everything else combined.

What a custom build does: build reporting off one transaction store rather than assembling each report from scratch. The shipment record carries everything the reports need: product, size, alcohol by volume, state, licence type, customer, date and quantities in the units each authority wants, which are not the same units. Then each report is a defined transformation with a preview, a submission record and an archived copy of exactly what was filed. Depletion reporting to suppliers runs off the same store in each supplier's required format, which is the feature that gets the project funded by operations rather than by compliance.

Problem 5: the portfolio and the licence footprint keep moving

You take on a new supplier with 40 SKUs. You gain distribution rights in four more states. A supplier terminates and franchise laws in several states restrict how brand terminations work, which is a legal matter for counsel but an operational one for you, because the inventory, the registrations and the open orders all need handling.

What a custom build does: treat the licence footprint as data. Which entity holds which licence type in which state, with expiry dates and the products that depend on it. Onboarding a supplier becomes a generated task list of registrations required across your footprint with realistic lead times, so the commercial team gets a truthful launch date instead of an optimistic one. That single output ends a recurring argument in almost every beverage alcohol business we have worked with, because sales has always assumed a new brand can ship next month and compliance has always known it cannot.

What this costs and how long it takes

Across the 2,000 plus projects Digital Heroes has delivered, the shape here is this. A first release covering the product, label version and registration model, the licence footprint, the posting and renewal calendar with escalation, and a compliance check service called by order entry runs 65,000 to 140,000 dollars over 12 to 18 weeks. A full platform adding filing generation and submission tracking, excise and volume reporting, licence validation for trade customers, direct to consumer volume limits and supplier depletion reporting runs 170,000 to 400,000 dollars phased over 6 to 12 months.

What drives cost up in this category specifically: the number of states, because each one is its own rule set and its own forms. Whether you need filings generated in state specific formats or only tracked, which is a large difference in effort. Direct to consumer, which brings its own permits, volume limits, age verification and carrier requirements. Multi entity structures, common in importers with separate licensed entities. And ERP integration depth, since a compliance check that order entry does not actually call is decoration.

One thing we will not quote for: maintaining a fifty state rules library. That is the core product of the compliance platforms and it is a serious ongoing content operation. If your build needs current rules content, subscribe to a provider and consume it, or keep the rules the compliance team maintains and design the system so updating a rule is a data change rather than a code change.

Build versus buy, and when buying is clearly right

Buy if you operate in a handful of states with a modest portfolio, or if you are a winery whose main compliance surface is direct to consumer shipping. Sovos ShipCompliant is the right answer for a lot of that market and it will cost far less than a build. If you are an importer who would rather outsource the operation than run it, Park Street exists for that reason and it is a legitimate strategy. If your problem is tax determination, Avalara does that job.

Build when two or more of these are true. First, you sell in enough states that the calendar is a full time role and the risk is concentrated in one person's spreadsheet. Second, you need the compliance check inside order entry, in real time, because reps quoting unregistered or unposted items is a recurring event. Third, your supplier depletion reporting burden is large, since that is contractual work no compliance platform will do for you. Fourth, your portfolio changes constantly through new supplier agreements, which turns registration lead time into a commercial planning input. Fifth, platform pricing per SKU per state has started to scale badly against a wide portfolio, which is a common trigger for the conversation.

Our position: buy the rules content, build the operating system around it. The two are separate products and the mistake is assuming you have to choose.

How to choose a developer for beverage alcohol compliance software

Ask them what happens when a supplier changes a label. If they do not immediately separate the SKU from the label version and the registration, they will build you a product table and you will be selling unregistered packaging within a year.

Ask how order entry gets an answer in real time and what the rep sees when the answer is no. A generic validation error trains people to route around the system. The message needs the reason, the expected resolution date and a named contact.

Ask who owns the code, and get it in writing before kickoff, including the repository and the cloud accounts. This system decides whether you may sell. It should not depend on a supplier relationship you cannot exit. At Digital Heroes the client owns the code from the first commit, and none of this replaces advice from alcohol beverage counsel on your specific obligations.