What BudLogix can and cannot do in Metrc and Dutchie for people

BudLogix connects to Dutchie and Metrc for products, orders and packages. For people, the connections are one-way: BudLogix reads, it never writes.

Dutchie

BudLogix reads the employee list from Dutchie. That is what Sync from Dutchie, under the ⋯ menu on the Roster, does, and what the nightly sync at 2 AM does for every organization with a Dutchie API key.

What the sync does:

• Matches each Dutchie employee to a login here: first on email, then on an exact name, then on a close one.
• Never matches a BudLogix platform administrator's login, so their account is never renamed or ended by the sync. A Dutchie employee whose only match is one is skipped, not given a new login.
• Creates a login here for an active Dutchie employee with no match - unless all of their Dutchie access is office only (Admin, Reporting Only, Security, Inventory and Sales Reports or individual permissions). Those wait under Not on roster on the Roster until somebody says whether they are staff.
• Skips any Dutchie account marked not staff, so an outside accountant with reports access never comes back as an employee.
• Corrects the name and email on a matched login to what Dutchie holds.
• Gives someone Dutchie marks as a sales user the Budtender role here.
• Deactivates someone here when Dutchie marks them inactive.
• Leaves someone alone if they are already inactive in BudLogix.
• Remembers each person's Dutchie name and groups, so a manager's discounts can be told apart from a budtender's in loss-prevention reports, and a sale can be matched to whoever rang it.

What it cannot do: create a Dutchie login, set a PIN, or change anyone's groups in Dutchie. A new hire's Dutchie login is created in the Dutchie back office; the next sync then matches it to their record here.

Metrc

Nothing in the Team module talks to Metrc about people. Agent registration is applied for, issued and carried outside the app, and a Metrc id is made by the person themselves. BudLogix only writes down what has happened: the CORI report a registration rests on, filed as a document; the registration number with its issued and expiry dates; and the Metrc id the licence admin needs in order to add them. It is typed in on the employee record, never read back from Metrc.

Why it matters

Any step that seems to offer "create this person in Dutchie" or "register this agent in Metrc" does not exist, because the connections cannot do it. Onboarding in BudLogix is a record of what has been done, not a way of doing it in those systems.

Where you see this

• Roster - Sync from Dutchie.
• Employee record - where the registration, the Metrc id and the CORI are written down.
• Onboarding: from offer to cleared to work