Skip to content

Module 05 · Close plan and up

Plan supply across your licenses, counting only product that has passed testing.

A planning and control layer over purchasing, transfers, inventory and production. It nets demand against on-hand, in-transit and lab-cleared supply and open POs, works out the permitted path for each move, and drafts transfers and purchase orders into Approvals. Every plan is scoped to one state.

By BudAlly

Published

  • 01 · SUPPLY PLAN

    Net requirements per SKU, store and week.

    The plan takes the demand forecast and subtracts on-hand, in-transit and lab-cleared supply, then splits the gap into an inter-license transfer, an open PO or a new buy. Buys are bounded by your open-to-buy cap and each vendor's credit limit, and use landed cost. Lab-pending units are shown as excluded, not counted. Every proposal goes to Approvals and waits for a person.

  • 02 · TRANSFER PATH

    Each inter-license move gets the path your state's rule pack allows.

    For a proposed transfer, the resolver works out the carrier type the pack requires — a licensed distributor, a secure transporter or your own vehicles — adds the intercompany price and runs the lab gate per package. It previews the intercompany journal and adds distributor fees and freight to landed cost. A path the pack doesn't hold returns UNKNOWN and blocks.

  • 03 · PRODUCTION AND ATP

    Release dates come from harvest, cure and your labs' real lead times.

    Lead time is tracked per lab as a median and a 90th percentile, with fail rate, and feeds a release forecast and available-to-promise by week. A batch that fails a test drops out of available-to-promise. BudAlly reads the BOM and schedule from your production tool and overlays lab timing; it doesn't schedule rooms, feeding or kitchen runs.

  • 04 · EXPIRY

    Lots near expiry or COA age get an action ladder with the margin impact.

    Each lot is bucketed by days to expiry and COA age, with a proposed transfer, markdown, bundle, return or destroy and what each does to margin. COA age and sell-by date are checked at planning time, not only before a shipment. Destroy proposals go to Adjustments for approval. Where shelf life is unknown, no action is proposed and the lot goes to a person.

  • 05 · CONTRACTS AND ALLOCATION

    Scarce lots are allocated by contract, then payment status, then priority.

    Supplier contracts record commitment type, minimum and maximum quantities and effective dates, with a burn-down of committed against taken and price variance against contract. When a scarce SKU is oversubscribed, allocation follows the rules above and never exceeds what is available to promise. A shortfall produces a pro-rata proposal that needs your approval.

  • 06 · TRANSPORT

    Transport slots are booked against capacity and credential checks.

    A day-by-slot board covers your own fleet and third-party carriers, with capacity by weight and value and the carrier type shown on each slot. Driver, vehicle and carrier licenses and insurance are checked when the slot is booked and again at departure. Freight cost per stop feeds cost-to-serve.

  • 07 · SUPPLIER SCORECARDS

    Suppliers are scored on what actually arrived.

    On-time-in-full, short-ships, rejections, COA failures, price variance and lead-time drift are computed from manifests, receipts, COAs and bills, with a 12-week trend and a drill-down to the evidence. A supplier with fewer than five deliveries shows "—" rather than a score. Price variances become claims in Bills and credit memos.

  • 08 · NETWORK AVAILABILITY

    In-state licensed supply, shown only where it has been shared with you.

    Search covers inventory that suppliers have granted to you or published through a marketplace feed, lab-filtered and limited to your own state, with license status and a freshness chip on every row. Any aggregate needs at least 8 contributors. "Request quote" creates a draft PO; the order itself goes to the supplier through LeafLink or email.

What it never does

  • Never plans, buys, allocates or transfers across state lines; origin, destination and supplier must all be in the same state.
  • Never counts lab-pending, held or recalled packages as available.
  • Never picks a transport path the rule pack doesn't hold; it returns UNKNOWN and blocks.
  • Never assigns an unlicensed or expired driver, vehicle or carrier, and never changes a manifest after departure.
  • Never allocates to a buyer whose license is inactive or who is out of state.
  • Every Metrc write goes through Approvals under the approver's own key.

BUILT TO CONNECT WITH

  • Metrc
  • Canix
  • Distru
  • Flourish
  • Trym
  • LeafLink
  • Nabis

Questions

Does this replace our production or cultivation software?
No. BudAlly reads the BOM and production schedule from tools such as Canix, Distru, Flourish or Trym and adds lab lead time, the release forecast and available-to-promise on top. Room scheduling, feeding and kitchen execution stay in those tools.
Does BudAlly place orders with our suppliers?
It drafts them. A person approves the PO in BudAlly, and the order goes to the supplier through LeafLink, Nabis or email.
Can we plan supply across states?
No. Every plan, PO, transfer and allocation is scoped to one state, and a line whose origin, destination or supplier is in another state is rejected.
Which plan includes supply chain?
Purchasing, supply plans and supplier scorecards are part of the Close plan. Chain Ops adds network availability across brands and distributors.