Built in Canada, for the rules that apply here.

A Canadian licensed producer sits inside a stack of obligations that exists nowhere else in that combination: federal excise under two separate statutes depending on what is in the tank, a liquor authority with its own markup in each of the 13 provinces and territories, container deposits and stewardship programs that differ by province and by container, and sales tax that depends on where the sale is made.

None of that is a localisation setting. Which statute applies is decided by what the drink was fermented from, not by what the label says — which is why cider and mead are classed as wine under federal excise law, and handled that way in BrewCraft. The compliance model is the product, and it was built here, for here.

A hectolitre of beer can be, at the same moment, inventory in a brite tank, work-in-process at a specific cost, an excise liability, an allocation against a board order and a traceability node linking four raw-material lots. Every one of those views has to agree with the others.

So BrewCraft was specified before it was coded: numbered rules, an explicit list of every status change, a glossary that pins down every term, and a batch traced end to end with real arithmetic. Every capability on these pages is described from that specification.

Every duty, markup, deposit and fee rate BrewCraft applies lives in an effective-dated table and traces to its published source. Where a question has no published answer, the product says so and shows you where, rather than filling the gap with a default.

A confidently wrong duty figure looks right, gets filed, and surfaces at audit. We would rather show you the one volume nobody can explain than hand your accountant a number to unwind.

The console runs in English, Canadian French and Simplified Chinese, chosen per person rather than per company — because a Québec compliance officer working in French and a cellar hand reading Simplified Chinese are often the same company on the same afternoon.