Licensed account gating
License status, expiry and permitted categories carried on the account.
A beverage order is three transactions pretending to be one. There is the product. There is the container, which is an asset you expect back and which carries a deposit that settles separately. And there is the delivery, which happens on a route, on a day, to an account whose license determines whether the order was legal in the first place.
Last updated
Uncap builds Shopify commerce for beverage distributors, breweries, wineries and non-alcoholic beverage operators where those three are handled as three things: licensed account structure with the compliance engine integrated rather than improvised, deposits and returnable containers tracked as assets, and route based delivery enforced at checkout.
Uncap is a Shopify Platinum Partner, on Shopify since 2013, with 380+ Shopify stores launched.
This page was split from the combined food and beverage page. Its sibling, Food Distribution, covers catch weight pricing, lot and expiry traceability and cold chain. Beverage is separated because the regulatory and logistics layers have no equivalent there. Operators who do both need both, and the account and ERP layers are shared.
A beverage order is three transactions pretending to be one.
A U.S. beverage operation runs on more than a storefront. Uncap scopes the commerce layer as one of four integrated systems, alongside compliance, ERP and delivery operations, rather than expecting one platform to carry the whole stack.
License status by account, product eligibility by state, volume limits, shipping eligibility, reporting obligations. This is a specialist compliance engine's job, and it changes by jurisdiction on a schedule nobody controls.
The architecture follows from that. Beyond the storefront, the build spans an alcohol compliance engine for rules and shipping eligibility, the ERP and order management, and route planning and delivery operations, with deposit and returnables logic running across them.
Uncap scopes alcohol compliance as a specialist integration, named in the scope, rather than as a platform setting.
A keg is not a product. It is a container you own, out on loan, with a deposit charged at delivery and credited on return, a balance per account, and a real financial exposure when it does not come back. The commerce layer models containers as deposit SKUs, container assets or refundable fees, and the balance is reconciled operationally in the ERP and delivery workflows rather than only in checkout.
The commerce layer captures the deposit. The ERP owns the balance.
Accounts sit on a route. Routes run on days. A cutoff governs what makes the next truck. An order accepted after cutoff that appears to promise tomorrow is a complaint, not a sale.
A licensed retail account and a consumer buying direct are governed by entirely different rules, in different states, with different eligibility. Running them on separate platforms doubles the surface where a compliance rule can be wrong.
Uncap builds the commerce layer and owns the integrations into the other three.
Commerce, compliance, ERP and delivery operations as four integrated systems rather than one platform pretending to be all four. Uncap builds the commerce layer and owns the integrations into the other three.
Uncap Connect is a Shopify-embedded app syncing ERP pricing, inventory, customer accounts and orders directly to Shopify, without a middleware subscription in between. Thirteen integrations are published, covering NetSuite, Microsoft Dynamics, SAP, Oracle, Epicor, Infor, Sage, Acumatica, Odoo, QuickBooks, Fishbowl, Cin7 and Syspro.
The compliance engine is a specialist integration rather than an Uncap product, and it is named as such in the scope. That is the honest position.
Uncap Portal provides multi-user accounts with roles and permissions, where each buyer sees their own assortment and pricing. License status, expiry and permitted product categories are carried on the account and gate what that account can see and order, refreshed from the compliance system rather than maintained by hand.
An account whose license has lapsed should not be able to place an order, and should not need a human to notice.
Deposits are captured at order as their own line, credited on return, and reconciled against a per-account container balance in the ERP where the financial record belongs. The commerce layer's job is to charge and credit correctly and to show the account its current balance, not to become the asset register.
Delivery day, cutoff time, branch and route are configured per account and enforced using Shopify's delivery customization capability, so an account on a Thursday route with a Wednesday cutoff sees the next real delivery date rather than an option nobody intended to honor.
Item level contract prices, depletion allowances and volume programs come from the ERP and enforce at checkout. Uncap Quotes runs the full configure, price, quote workflow inside the Shopify admin, with negotiated prices, tiers and volume breaks applied automatically, approvals routed to the right approver, revisions that keep the version history, and an approved quote converting to a Shopify order in one click for annual programs.
Uncap has built beverage and consumable brands on Shopify, including Vosges Chocolate and Soul CBD, which runs a subscription model, and Codex Beauty, which demonstrates the international selling and subscription pattern. None of those is a licensed alcohol distribution build, and that is stated plainly rather than implied away.
Product, container and delivery handled as three things.
License status, expiry and permitted categories carried on the account.
State by state eligibility, volume limits and reporting handled by a specialist system, named in the scope.
Charged at order, credited on return, with balances reconciled in the ERP.
Delivery day, cutoff, branch and route configured per account and enforced at checkout.
Prices, allowances and volume programs synced from the ERP.
Generated on schedule as editable drafts, under the same route and cutoff rules.
Roles and permissions for groups ordering across several licensed locations.
Both channels on one catalog and one inventory.
Thirteen published integrations syncing pricing, inventory, accounts and orders.
Licensed account gating. License status, expiry and permitted categories carried on the account, refreshed from the compliance system, gating catalog visibility and order eligibility.
Compliance engine integration. State by state shipping eligibility, volume limits and reporting handled by a specialist compliance system integrated into the order flow, named in the scope rather than claimed as a native feature.
Deposits and returnable containers. Deposits charged at order and credited on return, with per-account container balances reconciled in the ERP.
Route and cutoff enforcement. Delivery day, cutoff, branch and route configured per account and enforced at checkout using Shopify's delivery customization capability.
Contract pricing and depletion programs. Item level prices, allowances and volume programs synced from the ERP and enforced at checkout.
Standing and recurring orders. Regular account orders generated on schedule as editable drafts, subject to the same route and cutoff rules.
Multi-user account structure. Multi-user accounts with roles and permissions, where each buyer sees their own assortment and pricing, for groups ordering across several licensed locations.
One platform for licensed trade and consumer direct. Both channels on one catalog and one inventory, with eligibility rules applied per channel rather than maintained in two systems.
ERP integration. Thirteen published integrations, syncing pricing, inventory, customer accounts and orders directly to Shopify.
The four-system architecture is stated, not hidden. Commerce, compliance, ERP and delivery operations are separate integrated systems, and that is how the scope is written, including the parts Uncap does not build.
Compliance is named as a specialist integration. No claim that a commerce platform solves alcohol compliance, because the claim carries real liability.
Route logic uses a real platform mechanism. Shopify's delivery customization capability is the hook route and cutoff enforcement needs.
Scoped before it is built. The Uncap Blueprint maps the account and license model, compliance integration, deposit and container handling, route logic and ERP integration before any build begins.
Related pages: Food Distribution, the sibling page for catch weight, lot traceability and cold chain, and Restaurant and Hotel Supply for the accounts these routes already serve.
Bring one week of route schedules and one account's container balance. If those two can be made to agree with what the storefront shows, everything else follows.
Talk to Our Experts, or start with a Blueprint if what you need first is the four-system architecture written down and costed.
Uncap does not treat it as a platform feature. License status by account, product eligibility by state, volume limits and shipping eligibility belong in a specialist compliance engine integrated into the order flow. Uncap builds the commerce layer and the integration, and names the compliance system in the scope rather than absorbing it into a feature list.
Yes, as the commerce layer in a four system architecture rather than the whole answer. Shopify carries licensed trade and consumer direct ordering, while compliance, ERP and delivery operations stay in the systems built for them, integrated into the order flow.
The deposit is charged as its own line at order and credited on return, while the per-account container balance is reconciled in the ERP, which is where the financial record belongs. The account sees its current balance; the ERP owns it.
Yes. Delivery day, cutoff time, branch and route are configured per account and enforced using Shopify's delivery customization capability, so an order placed after cutoff shows the next real delivery date for that account rather than an option that was never going to be honored.
Yes, and it reduces compliance surface rather than increasing it. Both channels run from one catalog and one inventory, with eligibility rules applied per channel. Running them on two platforms means maintaining the same state by state rules twice, which is two places for them to be wrong.
The account stops being able to order, without a human noticing first. License status and expiry are carried on the account and refreshed from the compliance system, and they gate both catalog visibility and order eligibility.
Uncap has built beverage and consumable brands on Shopify, including Vosges Chocolate and Soul CBD. None of those is a licensed alcohol distribution build. That is worth saying plainly, and worth asking of any agency that shows you a beverage logo without saying which side of the license it sits on.
The regulatory and logistics layers. Food Distribution covers catch weight pricing, lot and expiry traceability and cold chain. This page covers licensing, state by state eligibility, deposits and returnable containers, and route based delivery. The account structure, contract pricing and ERP integration are shared between them.
Uncap publishes integrations for thirteen ERP vendors, and beneath those, pages for the individual products beverage distributors actually run. The ones that come up most here are SAP S/4HANA, Sage X3 and Infor M3. Each page covers what the integration involves on that specific system, including what the vendor documents and what it does not.