What we commit to before there is a contract.

Using this website

You may read it, print it, quote it and link to it. The compliance material we publish is intended to be cited; if you are a guild, an accountant or another vendor and you find it useful, cite it with the date you retrieved it, because these things change.

Nothing on this site is tax or legal advice. It describes how our software behaves. It does not tell you what you owe, when you owe it, or what a regulator will accept.

What we do not claim

We do not say that BrewCraft makes you compliant, keeps you compliant, or satisfies a named obligation. We do not describe it as certified, approved, guaranteed, audit-proof or CRA-compliant. We do not publish a duty rate, a tax rate, a markup, a deposit amount, a stewardship fee, a threshold, a filing deadline or a form number.

Inside the product, every rate BrewCraft applies comes from a dated table that cites its published source, and BrewCraft shows its working rather than asserting a figure.

Pricing, when there is one

There is no published price yet, and we would rather say that than publish one nobody owns. These are the commitments that will apply to it:

• Priced per Producer, per month, in Canadian dollars. A Producer is the licensed legal entity that holds the excise licence and files the return. Not per seat — in a ten-person brewery one person is often the brewmaster, purchasing and compliance, and pricing per seat taxes exactly the behaviour we want. The workaround for per-seat pricing is a shared login, which breaks the audit trail's record of who did what, and that is a real audit failure rather than a minor one.
• Unlimited users. Please do not share a login; we would rather know who released the batch.
• Prices are shown exclusive of tax, with applicable taxes added. We do not display a tax rate, because the applicable rate depends on your place of supply and on our registration status, and neither is something to guess at in a footnote.
• Nothing compliance-critical is ever behind a tier. Not the duty ledger, not traceability, not audit-log depth, not record retention, not export. Withholding a compliance capability to drive an upgrade is selling a compliance gap, and it is the one line a pricing page must not cross.

Price changes

• A price quoted in a proposal is honoured for the validity window printed on the quote , which will be at least thirty days.
• An existing customer's price holds for the remainder of their term and renews at the then-current price with ninety days' written notice.
• Beta customers get a longer lock: twenty-four months from their start date, then at most one increase, still with ninety days' notice. A number and a date rather than “forever” — a careful buyer discounts “forever”, and rightly.

Your data

• Your production records are yours. Export is available on every plan, at every stage, and is never gated behind a payment or a renewal.
• The export is complete and documented, in a structured, commonly used, machine-readable format. This is a design obligation rather than a courtesy: a producer who entered real production data may have a statutory retention obligation on records they made in our system.
• If a trial ends without a conversion, the account becomes read-only for thirty days — everything readable, everything exportable, nothing writable — and after written notice the data is deleted sixty days after the trial ends.

Filing

BrewCraft does not file anything with any government, on any plan, at any price. It keeps the duty ledger, reconciles each period and prepares the figures with the ledger that supports them. You, or your accountant, review and file.

Beta

BrewCraft is in private beta, and capabilities reach beta partners in stages. Beta describes the pace of change. It does not qualify the durability of your data, and it does not qualify anything on this page. The private beta sets out what partners get.

Questions

Ask them in the beta application , which has a free-text box for them, and a person replies. For anything about your personal information, write to our privacy officer.