Inside Audit Shield Reconcile
Turn an inventory question into a specific, reviewable next step. See the evidence, the proposed change and the approval it needs. Keep the outcome on the record.
036000291452The product exists. Its barcode connection is missing.
Connect the code to the existing product.
Quantity unchanged · no Metrc changeReview the prepared action before it runs.
Awaiting the required approvalCheck the next scan. Retain who approved and what happened.
Sample case · approval depends on the location's policy.
The source records, the proposed correction and its approval path come together around one case.
Review the records considered, the likely cause and the basis for the conclusion. A missing count or an ambiguous match stays visible instead of becoming an invented answer.
See which supported action is proposed, the system and fields it would affect, and the expected result. A suggestion is kept separate from permission to carry it out.
The person's role and the action's risk determine the approval path. A safe local barcode mapping has a separate, explicit location setting for automatic repair.
The case retains who authorized the action, what ran, what was verified and why it was closed or left open. An attempted change remains distinct from a confirmed result.
This illustrative local barcode example uses sample records. It shows the review path without implying a live transaction or a change to Metrc.
The employee opens Fix Inventory. The workflow checks the known product, package and identifier records before proposing a new connection.
The proposal identifies the existing product and the missing barcode mapping. If the match is ambiguous, ask for the additional scan or manager review instead of guessing.
Apply the action only through the applicable approval policy. Verify that the barcode now resolves, and retain the action and its result on the case.
The decision stays attributable.
Autopilot changes a record only after a named person approves the prepared correction (a safe barcode mapping may apply on its own where an owner or compliance manager has switched that on for the location), and every change is recorded with who authorized it, on which device, and what actually happened.
AI may investigate, reason, recommend, simulate and prepare. Humans authorize consequential changes. Smoke Alarm records both.
The exact discrepancy and the records affected.
The root-cause analysis and the evidence considered, with confidence.
The exact actions, systems, fields and expected effects.
Employee identity, role, terminal or device, timestamp.
API calls, mutations, responses, retries, failures.
Confirmation that the expected state now matches the resulting state.
Choose a Reconcile tier that includes the required remediation capability, then agree which workflows are ready for the location. A plan entitlement is not a go-live approval.
Set up the supported POS import or connection and authorized Metrc access where needed. Verify identifiers, source times and the evidence each proposed correction will rely on.
Name the approvers, review permissions, and rehearse the supported actions. Keep automatic low-risk repair off unless the owner or compliance manager explicitly enables it for the location.
Batch review, multi-location remediation and dual approval are part of the proposed Enterprise scope. Confirm their delivery and readiness separately; they are not currently active workflows.
Choose the monthly plan for each location, then agree on the workflows and setup your team needs. One-time implementation is priced separately.
Prepared corrections
$399
per location a month
One-time implementation: $750–$1,500.
Reconciliation with investigation, prepared corrections and the approval and verification record. Facility activation depends on the supported workflows agreed during setup.
Discuss this planBroader operating scope
From $799
per location a month
One-time implementation: $2,500 or more.
Plan for wider oversight and approval needs. Separate the currently supported reconciliation work from Enterprise remediation workflows awaiting delivery.
Discuss this planThese are planning prices, not a quote. Confirm your locations, implementation scope and available workflows in the agreement.
Autopilot is a capability level within Audit Shield Reconcile. Reconcile Pro includes the remediation level; Enterprise adds a proposed broader scope. It is not a separate standalone plan. Confirm the enabled workflows and facility rollout when choosing a tier.
Autopilot changes a record only after a named person approves the prepared correction (a safe barcode mapping may apply on its own where an owner or compliance manager has switched that on for the location), and every change is recorded with who authorized it, on which device, and what actually happened.
No. The proposal must match a supported action, the evidence must be sufficient, and the facility and person must have the required authority. An external step can remain a documented handoff. Missing evidence, unsupported actions and higher-risk decisions stay with a person.
Yes. Audit Shield Reconcile can work beside an existing POS through supported export imports. The available correction tools depend on the connected systems and the facility's setup; comparing an export does not grant permission to write to that POS.
Walk through the source records, the proposed correction and the approval path with us. Leave knowing which steps can be supported for your facility.