Metrc synchronization and data ownership

Imported records

• Facilities available to the saved Metrc user key.

• Active and inactive items.

• Active, on-hold, and inactive packages, including quantity, unit, status, source labels, and package details.

• Lab results, lab test types, and lab test states returned for supported packages.

• Inbound, outbound, and rejected transfers, deliveries, transporters, package details, and package wholesale prices returned by supported endpoints.

Triggers and timing

• Save the API key, then import facilities before package work can be associated correctly.

• Importing a facility queues its item and package backfill. Sync Transfers requests transfer work separately.

• Schedule Full Import queues historical work from the credentialed date, capped at two years. Package backfill is divided into daily jobs.

• The application scheduler runs hourly in America/Los_Angeles and queues item, package, lab-state, lab-type, and transfer synchronization for businesses with a key.

• Queue timing depends on pending work. A button press is a request, not proof of completion.

Evidence of completion

Inventory > Sync Status shows each resource, Last Sync, and running, ok, or error. An error includes Last Error text. Successful evidence is a recent ok status plus a known source record whose facility, quantity, unit, state, and lab values match Metrc.

Corrections and overwritten fields

• Correct Metrc-owned facilities, items, package quantity, package state, source labels, transfers, and lab results in Metrc, then sync again.

• A later sync can overwrite imported values with the next Metrc response.

• Maintain product identity, product variants, menu inclusion, partner pricing, buyer orders, and product-to-inventory links in Higher Origins.

• No supported Higher Origins workflow writes these corrections, orders, menus, or product records back to Metrc.

Permissions

The API key belongs to a Metrc user. That user must be able to access each needed facility and resource in Metrc. Share access by granting the appropriate Metrc permissions to the person who owns the integration key; never share the key itself in support evidence.

Related guidance

• Connect Metrc and confirm your inventory imported correctly: perform setup and a known-record comparison

• My Metrc package did not import: diagnose a missing package