How BudLogix links what a vendor sends to your products
A vendor names things their way. Your catalog, synced from Dutchie, names them yours. BudLogix keeps three links between the two so ordering, receiving and invoicing all count the same thing.
Brand to vendor
The coarsest link. On Vendors & Brands you say which brands each vendor supplies. Product search on an order looks only at those brands unless you tick Search all products, and reorder suggestions are grouped under the vendor through it.
Vendor catalog item to product
A vendor's catalog lists what they sell with their own names, SKUs and case sizes. Each catalog item can be linked to one of your products. The link gives an order line its case size, lets invoice lines inherit the right product, and lets a receipt count against it.
Links are made in four places:
- On an order, the Link button on a line opens Match to vendor catalog. Search the vendor's catalog and pick the item; the button becomes Linked. Unlink removes it.
- On Unlinked vendor products, where every unmatched catalog item, invoice name and manifest line waits with ranked suggestions.
- At receiving, when a new product is created or linked on the Reconciliation cockpit. The order line it was Ordered as gives the vendor's listing - the Apex listing the line was ordered from - and a package whose Metrc tag is on one of your Leaf Trade orders gives that Leaf Trade product. The link shows as Linked at receiving, and the listing learns the package's Metrc item id, so a later link for the same Metrc item finds this listing instead of making a new one.
- On their own, when an Apex order or a catalog import can resolve an item without doubt. A tincture, edible, drink or topical is matched by brand, product line, flavor and dose instead ("Good Vibes X Orange Creamsicle Syrup | 1000mg" is the listing "Good Vibes x Orange Creamsicle Syrup (1000mg THC) - Distru"; "NO Flavor" is Unflavored), and a concentrate by its type and weight. Those show as Auto-matched or Backfilled rather than Confirmed by hand. A listing already linked to another of your products is never moved, and a near miss waits on Unlinked vendor products.
A link is permanent until you unlink it, and an unlinked match is remembered as wrong.
A link also reaches your purchase orders. An order line that names the item - one written from an Apex order, or built from the vendor's listing - and has no product yet takes the linked product as soon as the link is made, so the order counts as ordered for that product and its receipts can be counted against the line. A line that already has a product is never changed, and nothing is matched by name.
Vendor identity
Behind both sits the question of who the vendor is. Dutchie holds a license number for each vendor; METRC manifests name the shipper. When they disagree, Vendors & Brands raises an advisory. BudLogix never changes vendor identity; the fix is in Dutchie.
What breaks without the links
A product not linked to Dutchie is flagged on the order page as not in your POS yet. The order still goes out, but receiving it is harder until the product exists. An unlinked catalog item leaves its invoice lines without a case size and its receipts unmatched.
A line with no product at all
An order line can be typed in with its own name, case size and price when the vendor sells something you do not carry yet. It shows New product and is not linked to anything until the goods arrive: receiving pairs the received product with the line carrying its name, and the line then shows Ordered as "(the name you typed)". A product is never created from the order itself, and nothing is written to the vendor's catalog, which is shared with every other store ordering from that vendor. See Order a product that is not in the catalogue yet.
Where you see this
Link to vendor catalogue... in a line's ... menu on the purchase order page; the Not linked to vendor badge in product search; Unlinked vendor products; matching in Receiving and Invoices.
Last checked against the product on 10 Oct 2026. This is the same article operators read inside BudLogix.