<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>The Ops Community ⚙️: Victoria Hodgson</title>
    <description>The latest articles on The Ops Community ⚙️ by Victoria Hodgson (@victoria_hodgson_8b0ee248).</description>
    <link>https://community.ops.io/victoria_hodgson_8b0ee248</link>
    <image>
      <url>https://community.ops.io/images/ynCBGOciN3_fqoE23NW5zTr3ThwZgF1cgGeRNEUA9oE/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly9jb21t/dW5pdHkub3BzLmlv/L3JlbW90ZWltYWdl/cy91cGxvYWRzL3Vz/ZXIvcHJvZmlsZV9p/bWFnZS80NDc2My9m/M2NiMDJkMy1kZWJm/LTRiNDItOWFjNy05/YWQ2ZGNkYjMzN2Eu/cG5n</url>
      <title>The Ops Community ⚙️: Victoria Hodgson</title>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://community.ops.io/feed/victoria_hodgson_8b0ee248"/>
    <language>en</language>
    <item>
      <title>Metrc sync recovery when a dispensary package changes mid-count</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:30:40 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/metrc-sync-recovery-when-a-dispensary-package-changes-mid-count-3f51</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/metrc-sync-recovery-when-a-dispensary-package-changes-mid-count-3f51</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/3zifb0z1ht74ye7tf82w.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/3zifb0z1ht74ye7tf82w.png" alt=" " width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A package can change while an employee is still counting it. A sale removes stock, another employee records an adjustment, or a movement appears after the physical count was entered. By the time the counter confirms the result, the saved observation and the displayed balance may describe different moments.&lt;/p&gt;

&lt;p&gt;That mismatch needs investigation before anyone treats it as missing inventory or a failed integration. Repeating a transaction or applying an adjustment without checking its history can make the next comparison harder to explain.&lt;/p&gt;

&lt;p&gt;When evaluating &lt;a href="https://indicaonline.com/roles/inventory-manager/" rel="noopener noreferrer"&gt;metrc inventory sync software&lt;/a&gt;, examine how staff can review package activity, count records, and reporting status. Recovery depends on establishing what happened to the stock and which operations each system has recorded. A matching balance alone cannot answer those questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pause the affected package’s count confirmation
&lt;/h2&gt;

&lt;p&gt;Leave the disputed count pending while you preserve the evidence. Record the package identifier, location, unit of measure, physical quantity, and when the observation was made. Save the displayed POS and Metrc quantities with their observation times.&lt;/p&gt;

&lt;p&gt;Keep the original count distinguishable from any later recount. Replacing it without an explanation removes evidence that could help establish whether the apparent difference came from a subsequent movement.&lt;/p&gt;

&lt;h3&gt;
  
  
  Confirm that every record refers to the same package
&lt;/h3&gt;

&lt;p&gt;Use the tracked package identifier, rather than the product name alone, to connect records. Check the store or facility context and confirm whether the quantity represents weight or individual units.&lt;/p&gt;

&lt;p&gt;Also check the count’s physical scope. A count of stock in a particular storage area should not be compared with a total covering additional locations unless those quantities have been accounted for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reconstruct what changed during the count
&lt;/h2&gt;

&lt;p&gt;Build a timeline from the physical observation through the attempted confirmation. Review the relevant sale, adjustment, or other inventory movement and connect it to supporting records.&lt;/p&gt;

&lt;p&gt;Distinguish when stock physically moved from when staff entered the operation and when it appeared in the receiving system. A late entry can make an earlier physical movement look like a new change. An operation entered before counting may already be reflected in the observation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compare quantities at a common point in time
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Bring the records to a common time before calculating a discrepancy.&lt;/strong&gt; Establish which movements occurred before the count and which occurred afterward. Preserve the original observation while documenting how it relates to the current balance.&lt;/p&gt;

&lt;p&gt;If the sequence cannot be reconstructed reliably, arrange a brief period without movements of the affected stock and recount it. Record the new observation time. Avoid reconstructing a physical quantity from assumptions about when a sale must have happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check whether the audit updated its expected quantity
&lt;/h2&gt;

&lt;p&gt;Separate the system’s expected balance from the quantity entered by the employee. Updating the first does not establish that the second still describes the stock currently present.&lt;/p&gt;

&lt;p&gt;Dutchie’s &lt;a href="https://support.dutchie.com/hc/en-us/articles/12882342121875-Conduct-an-inventory-audit-in-Dutchie-POS" rel="noopener noreferrer"&gt;inventory audit instructions&lt;/a&gt; describe an alert when sales or another user’s adjustments change an expected quantity during an audit. Depending on the scenario, confirming or refreshing updates the expected quantity without changing the entered count. This is documented Dutchie behavior, rather than a universal rule for every POS.&lt;/p&gt;

&lt;h3&gt;
  
  
  Revalidate the count before confirming it
&lt;/h3&gt;

&lt;p&gt;Treat that alert as a reason to revisit the timeline. Determine whether the saved count remains applicable, needs a documented update under the audit procedure, or requires a recount.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Refreshing an expected balance does not perform a physical recount.&lt;/strong&gt; Read the affected row and any proposed adjustment again before confirming it. An adjustment calculated before the movement may no longer represent the difference you need to resolve.&lt;/p&gt;

&lt;h2&gt;
  
  
  Refresh the comparison before changing inventory
&lt;/h2&gt;

&lt;p&gt;Check what the available action actually does. Fetching current package data, resending a failed operation, and changing a balance are different actions, even if their labels all suggest synchronization.&lt;/p&gt;

&lt;p&gt;Use the platform’s documented method for refreshing comparison data. Preserve the earlier observations, then inspect the current values and reporting status. Establish whether the apparent difference persists after the records are current.&lt;/p&gt;

&lt;p&gt;A refreshed screen is evidence of a new observation, not proof that every underlying operation completed. If an error remains, retain its message and the affected identifiers so the next reviewer can investigate the same event.&lt;/p&gt;

&lt;h2&gt;
  
  
  Resolve the missing operation before adding an adjustment
&lt;/h2&gt;

&lt;p&gt;Follow the operation behind the quantity change. Compare its POS record with the corresponding evidence available in Metrc and the integration’s reporting status.&lt;/p&gt;

&lt;p&gt;Determine whether it is waiting to report, failed, or already recorded. A general inventory difference does not identify which of these occurred. Keep the sale or adjustment reference attached to the investigation instead of relying only on package totals.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check for an existing submission before retrying
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Confirm the original operation’s status before sending it again.&lt;/strong&gt; Look for the corresponding receiving-system record and use the platform’s documented recovery process where a retry is appropriate.&lt;/p&gt;

&lt;p&gt;If completion remains uncertain, give support the package identifier, transaction reference, relevant times, and error message. Do not create a replacement operation merely to make the balances match. Likewise, avoid an inventory adjustment that would account for a movement already represented by a sale.&lt;/p&gt;

&lt;h2&gt;
  
  
  Apply a correction only to the remaining discrepancy
&lt;/h2&gt;

&lt;p&gt;Once the relevant operations have been checked, compare the current physical stock with records referring to the same point in time. Identify any remaining unexplained difference separately from movements already resolved.&lt;/p&gt;

&lt;p&gt;Use the supported correction workflow for the platform and the store’s applicable procedures. Confirm which records the action changes and how it affects reporting before applying it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Correct the verified remaining difference, with its explanation attached.&lt;/strong&gt; Preserve the original quantity, the validated observation, the reason, and the operations reviewed. If the evidence supports no adjustment, record that outcome rather than forcing a quantity change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify recovery before closing the audit
&lt;/h2&gt;

&lt;p&gt;Review the affected package against a short completion checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Package identity, location, and units match across the comparison.&lt;/li&gt;
&lt;li&gt;The count has a clear observation time and physical scope.&lt;/li&gt;
&lt;li&gt;Movements during the investigation have been accounted for.&lt;/li&gt;
&lt;li&gt;Relevant operations have verified reporting outcomes.&lt;/li&gt;
&lt;li&gt;Any correction has a documented basis and an identified reviewer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Assign responsibility for the disputed row until that review is complete. If the package changes again before closure, return to the timeline and revalidate the count instead of approving the earlier calculation automatically.&lt;/p&gt;

&lt;p&gt;For the next live count, agree in advance how staff will flag a package that changes and who will review it. Keep that instruction beside the audit procedure so an unexpected sale leads to a traceable review rather than an unexplained adjustment.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to test budtender POS search for lookalike products</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:19:02 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/how-to-test-budtender-pos-search-for-lookalike-products-1anl</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/how-to-test-budtender-pos-search-for-lookalike-products-1anl</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/ewdkoa4phpshcr2n0l51.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/ewdkoa4phpshcr2n0l51.png" alt=" " width="1731" height="909"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A search can return the right product name while leaving a budtender looking at the wrong package size. If the difference appears only inside a detail screen, selecting the first familiar result may put a different item in the cart.&lt;/p&gt;

&lt;p&gt;Test that moment before accepting a search demonstration as proof that the workflow suits your store. Finding a recognizable name, distinguishing its variants, and selecting the intended inventory are separate tasks. The test should follow the employee through each.&lt;/p&gt;

&lt;p&gt;When comparing the &lt;a href="https://indicaonline.com/roles/budtender/" rel="noopener noreferrer"&gt;best budtender pos systems&lt;/a&gt;, use products from your own assortment to assess those tasks. A useful demonstration lets staff explain why they chose a particular result, then verify that the cart matches the physical package.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build a test set from products staff can confuse
&lt;/h2&gt;

&lt;p&gt;Start with products whose names or packaging are similar. Include the same product in different package sizes, closely named variants from a shared brand, and products whose packaging looks alike despite different contents. Use actual catalog records rather than inventing sample names that make the distinction obvious.&lt;/p&gt;

&lt;p&gt;For each scenario, write down the intended product and the attributes that distinguish it from nearby alternatives. Keep the competing records available during testing so the employee faces the choice you want to examine.&lt;/p&gt;

&lt;h3&gt;
  
  
  Establish the expected result before testing
&lt;/h3&gt;

&lt;p&gt;Compare the reference record with the physical package. Confirm its name, form, size, and identifying code, along with the inventory information needed for selection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Define the correct selection before watching someone search.&lt;/strong&gt; Otherwise, a plausible result can become the accepted answer simply because nobody checked the reference. Use a demonstration environment or an available test mode that avoids creating real sales or inventory movements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Search the way budtenders actually search
&lt;/h2&gt;

&lt;p&gt;Ask staff to enter the words they would use at the counter. Try the full name, a shortened name, and the brand combined with package size. Include a changed word order or a plausible typing error.&lt;/p&gt;

&lt;p&gt;These are test cases, not assumptions about features every platform supports. Record which queries work and whether the supported search behavior is understandable to employees.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check recovery when the first query fails
&lt;/h3&gt;

&lt;p&gt;When a search returns nothing, ask the employee what they would try next. Watch whether they can revise the query, inspect an active filter, or use another documented lookup method.&lt;/p&gt;

&lt;p&gt;Distinguish a missing result from an ambiguous result. The first may require a different query; the second requires enough information to separate competing products. In either case, note whether the employee needs a supervisor or guesses.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inspect what distinguishes each search result
&lt;/h2&gt;

&lt;p&gt;Look at the results on the device staff actually use. Check whether the distinguishing package size or product form is visible in the list, hidden behind another action, or cut off by the screen layout.&lt;/p&gt;

&lt;p&gt;Ask the employee to identify the evidence behind their choice. “It was at the top” gives the manager a different finding from “The package size and form match the request.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A recognizable image or shared name is insufficient evidence of the intended variant.&lt;/strong&gt; Check the supporting attributes. Opening a detail screen is acceptable when it provides the necessary information; record that step so the evaluation reflects the full task.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test barcode scanning separately from typed search
&lt;/h2&gt;

&lt;p&gt;Run the same intended product through manual search and barcode scanning. Compare the result, any additional selection required, and the final cart entry. Record which label was scanned, especially when the package carries multiple codes.&lt;/p&gt;

&lt;p&gt;Flowhub’s &lt;a href="https://help.flowhub.com/en/articles/9627237-use-upc-and-sku-to-track-inventory" rel="noopener noreferrer"&gt;UPC and SKU documentation&lt;/a&gt; explains why the paths can differ. In Flowhub, UPCs belong to the Product level, while SKUs belong to Inventory. Scanning a UPC can present inventory associated with that product for selection; scanning a SKU brings up the specific inventory item linked to it. This behavior is platform-specific and should be checked against your system’s documentation. &lt;a href="https://help.flowhub.com/en/articles/9627237-use-upc-and-sku-to-track-inventory?utm_source=chatgpt.com" rel="noopener noreferrer"&gt;Flowhub Help Hub&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Verify the inventory selection behind the product
&lt;/h3&gt;

&lt;p&gt;Where the workflow asks for a batch or inventory choice, include that step in the test. Compare the selected record with the package in hand and the reference prepared earlier.&lt;/p&gt;

&lt;p&gt;A successful scan confirms that the system recognized a code. The test still needs to establish that the code is associated with the intended record and that any required selection was made correctly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate legitimate variants from duplicate records
&lt;/h2&gt;

&lt;p&gt;Similar names deserve investigation before anyone changes the catalog. They may represent different package sizes, related products, separate inventory records, or accidental duplicates.&lt;/p&gt;

&lt;p&gt;Compare the attributes and identifiers behind each result. Do not remove a record simply because its name matches another. Ask the person responsible for catalog maintenance to establish whether the distinction is intentional.&lt;/p&gt;

&lt;p&gt;Keep cleanup separate from the search session. Document the confusing records and follow the platform’s supported correction process. Afterward, repeat the original query to confirm that the change resolved the ambiguity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record selection errors alongside search time
&lt;/h2&gt;

&lt;p&gt;Measure time across the complete task, including detail screens and inventory selection. Record correctness beside duration. A fast wrong selection should remain visible in the findings.&lt;/p&gt;

&lt;p&gt;Keep a short test log containing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The query or scanned code and intended product.&lt;/li&gt;
&lt;li&gt;The result selected and whether it matched the reference.&lt;/li&gt;
&lt;li&gt;Extra steps needed to confirm the variant or inventory.&lt;/li&gt;
&lt;li&gt;Any error, where it was detected, and how staff recovered.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Judge success by the item selected, not merely by whether search returned results.&lt;/strong&gt; Review the cart’s product, size, quantity, and inventory details where available. Also note mistakes employees corrected themselves before adding the item.&lt;/p&gt;

&lt;h3&gt;
  
  
  Distinguish catalog problems from training gaps
&lt;/h3&gt;

&lt;p&gt;Match the remedy to the observed cause. Missing size information may require a catalog update. A distinguishing attribute that is present but difficult to find may warrant a display or configuration review.&lt;/p&gt;

&lt;p&gt;An employee who does not understand an inventory selection prompt may need targeted instruction. Capture the question they struggled with so training addresses the actual decision. Avoid treating every hesitation as a need for faster typing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Retest the difficult cases during onboarding
&lt;/h2&gt;

&lt;p&gt;Repeat failed scenarios after changing records, configuration, or instructions. Keep the original request and expected result so the comparison tests the repair rather than an easier task.&lt;/p&gt;

&lt;p&gt;Use these cases in cannabis POS training for new employees. Let the employee find the product, explain the distinguishing attributes, and confirm the cart without hints about the correct row. Observe how they recover when an initial query fails.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keep unresolved ambiguity visible until the workflow supports a reliable choice.&lt;/strong&gt; Start the next review with similar products currently on your shelves. Prepare the expected selections, then ask a new employee to find each item and justify the choice using the information on screen.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why a green compliance dashboard is not proof of a clean audit</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:04:46 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/why-a-green-compliance-dashboard-is-not-proof-of-a-clean-audit-4me3</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/why-a-green-compliance-dashboard-is-not-proof-of-a-clean-audit-4me3</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/ear1rtvx9ui64ro7vmzh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/ear1rtvx9ui64ro7vmzh.png" alt=" " width="1731" height="909"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The dashboard shows green, but a stock count finds a package in the wrong room and another quantity that does not match the records. Before treating either finding as a software failure, establish what the green indicator actually checked. A successful system operation and verified physical inventory answer different questions.&lt;/p&gt;

&lt;p&gt;When reviewing information through a &lt;a href="https://indicaonline.com/roles/dispensary-owner/" rel="noopener noreferrer"&gt;dispensary owner mobile app&lt;/a&gt;, ask how to move from the summary to the records behind it. A convenient owner view can help direct attention, but readiness for an audit requires evidence tied to the review’s scope. Start by separating connection status, recorded transactions, physical stock, and the procedures used to investigate exceptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  A green status answers a limited question
&lt;/h2&gt;

&lt;p&gt;Ask the provider to define the indicator in plain language. It might describe an available connection, a completed submission, or the absence of detected errors in a particular queue. Those are possible meanings to investigate, not definitions that apply to every dispensary platform. A status is useful only when you know what was checked.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ask what the indicator actually checks
&lt;/h3&gt;

&lt;p&gt;Write down the data source, last evaluation time, included locations, and exclusions. Ask whether the system confirms delivery, acceptance, or a comparison between records. Also ask what would make the status change and where exceptions appear.&lt;/p&gt;

&lt;p&gt;Save the answer with the operating procedure so managers do not assign different meanings to the same display. Include the account role used to view the status. If the owner and inventory manager see different information, verify whether permissions or filters explain the difference before concluding that either screen is inaccurate.&lt;/p&gt;

&lt;h2&gt;
  
  
  Matching digital records does not verify physical stock
&lt;/h2&gt;

&lt;p&gt;A comparison between recorded quantities can show agreement without establishing what is on the shelf. If a physical movement was never entered, the records being compared may lack the same event. Agreement therefore needs a defined boundary: which systems, which products, which locations, and which point in time were examined?&lt;/p&gt;

&lt;h3&gt;
  
  
  Compare the same inventory at the same point in time
&lt;/h3&gt;

&lt;p&gt;Dutchie’s guidance on &lt;a href="https://support.dutchie.com/hc/en-us/articles/38560156984211-Best-practices-for-inventory-auditing-and-reconciliation-in-Dutchie-POS" rel="noopener noreferrer"&gt;physical inventory reconciliation&lt;/a&gt; describes comparing physical on-hand inventory, POS quantities, and traceability quantities. It recommends ensuring that inventory-affecting events are recorded before counting. Use that documented workflow as an example, rather than assuming another platform performs the same checks automatically.&lt;/p&gt;

&lt;p&gt;For your review, identify the packages and locations included, record the count time, and account for movements during the comparison. Where the store remains active, agree how sales, transfers, and returns during the count will be tracked. Otherwise, a later quantity may be compared with an earlier observation without anyone recognizing the timing difference.&lt;/p&gt;

&lt;h2&gt;
  
  
  No visible errors does not mean every event was recorded
&lt;/h2&gt;

&lt;p&gt;Consider an exchange that happened at the counter but was not entered into the system. A review limited to submitted records cannot establish the details of that missing event. Staff observations, receipts, and related inventory movements may be needed to explain the difference. The absence of a visible error is not evidence that every event was captured.&lt;/p&gt;

&lt;h3&gt;
  
  
  Investigate the event before adjusting the balance
&lt;/h3&gt;

&lt;p&gt;Dutchie identifies unrecorded exchanges as a cause of discrepancies and explains that quantity adjustments do not always resolve the issue after synchronization. Its guidance recommends checking for pending or failed transactions that might later succeed.&lt;br&gt;
Before authorizing a correction, determine whether a sale, exchange, movement, or count error explains the result. Do not create a replacement transaction unless the underlying event is supported by evidence and the appropriate workflow has been confirmed.&lt;/p&gt;

&lt;h2&gt;
  
  
  A completed correction still needs supporting evidence
&lt;/h2&gt;

&lt;p&gt;Changing a recorded quantity, explaining a discrepancy, and confirming the outcome are separate steps. A balance that now agrees with the count does not describe why the original difference existed. For an internal review, preserve the initial finding and its explanation alongside the authorized correction. This is a recommended evidence practice, not a universal legal retention rule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep the explanation attached to the record
&lt;/h3&gt;

&lt;p&gt;Build a short chain that another reviewer can follow: what was found, which source records supported the explanation, what changed, and who checked the result. Include identifiers and relevant times instead of relying on a screenshot alone. Closing an exception should preserve the reason it was closed. If the cause remains unknown, record that uncertainty rather than presenting an adjustment as a completed investigation.&lt;/p&gt;

&lt;h2&gt;
  
  
  One dashboard cannot establish the scope of an audit
&lt;/h2&gt;

&lt;p&gt;Clarify whether the review concerns inventory reconciliation, a particular operational process, or a broader compliance inspection. Then identify the evidence requested for that scope. Inventory quantities do not automatically answer questions about staff actions, supporting documents, or access decisions. Avoid treating a general dashboard label as a complete statement about areas it was never designed to examine.&lt;/p&gt;

&lt;h3&gt;
  
  
  Separate software coverage from review coverage
&lt;/h3&gt;

&lt;p&gt;Map each review question to a record, observation, or procedure that can support an answer. Ask the reviewer or responsible compliance lead to confirm the applicable requirements rather than importing a checklist from another jurisdiction. A system’s feature list describes its capabilities; your evidence map should describe what was actually examined. Keep unresolved questions visible even when the main dashboard status is green.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn the status into a verification routine
&lt;/h2&gt;

&lt;p&gt;Use the dashboard as a starting point for a repeatable review. For each selected indicator, record its meaning and follow it through to the supporting evidence. A compact checklist can help:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm the indicator’s definition and last evaluation time.&lt;/li&gt;
&lt;li&gt;Identify the stores, packages, and reporting period covered.&lt;/li&gt;
&lt;li&gt;Compare the relevant digital records with physical observations.&lt;/li&gt;
&lt;li&gt;Review open exceptions and transactions awaiting resolution.&lt;/li&gt;
&lt;li&gt;Verify authorized corrections against their supporting records.&lt;/li&gt;
&lt;li&gt;Assign an owner and next action to every unresolved finding.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the result specific. “No submission errors found in the reviewed records” communicates something different from “physical inventory reconciled for the selected packages.” State the period and coverage with the finding. If a location, room, or transaction category was excluded, make that visible. Report the evidence and its limits, so the owner can distinguish completed checks from work still pending.&lt;/p&gt;

&lt;p&gt;Retest the procedure after a change to an integration, reporting filter, or staff responsibility. Confirm that the supporting record is still available and that the assigned person can reach it. A previously successful review should remain reproducible under the current configuration, with any changed assumptions recorded.&lt;/p&gt;

&lt;p&gt;Choose a green indicator used in your daily review and ask its assigned manager to trace it to the underlying records. Have another person follow the same evidence and explain what the check establishes. If they cannot identify the scope, source, and unresolved exceptions, revise the procedure before using that status to support an audit-readiness report.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to test cannabis inventory reservations across channels</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:01:55 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/how-to-test-cannabis-inventory-reservations-across-channels-4kl4</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/how-to-test-cannabis-inventory-reservations-across-channels-4kl4</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/ud276isw3qzf1cq0f97x.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/ud276isw3qzf1cq0f97x.png" alt=" " width="1731" height="909"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The last available unit is still visible on your online menu when a budtender scans it at the register. Meanwhile, an online customer submits an order containing that same item. Your staff now need to establish which order has a valid claim and what the other customer should see.&lt;/p&gt;

&lt;p&gt;Testing this situation means checking more than whether inventory eventually updates. You need to identify when a reservation begins, which channels respect it, and what releases the stock. Start with documented expectations, then follow the item through competing orders, cancellations, and delayed updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Map which inventory each channel can sell
&lt;/h2&gt;

&lt;p&gt;When assessing &lt;a href="https://indicaonline.com/business-type/multi-location-operator/" rel="noopener noreferrer"&gt;cannabis multi-channel selling capabilities&lt;/a&gt;, first identify the inventory source behind each ordering channel. IndicaOnline describes a centralized catalog and visibility into stock across offices and storage locations. Those capabilities provide context for testing, but do not establish exactly how reservations behave across every connected channel.&lt;/p&gt;

&lt;p&gt;Select a product and record its store, inventory location, and identifying details. Confirm which register, website, and marketplace can sell that stock. Similar product names are not enough to prove that two channels draw from the same quantity.&lt;/p&gt;

&lt;p&gt;Use an approved test environment where available. Agree on the procedure with the staff responsible for inventory and order fulfillment so they can distinguish test activity from customer work.&lt;/p&gt;

&lt;p&gt;A shared catalog does not necessarily mean a shared pool of available inventory. Establish that relationship before interpreting any result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define when a reservation should begin and end
&lt;/h2&gt;

&lt;p&gt;Write down the expected behavior at each order stage: adding an item to a cart, submitting the order, accepting it for fulfillment, and completing the sale. Identify which event should reduce availability for another buyer.&lt;/p&gt;

&lt;p&gt;The official &lt;a href="https://support.blaze.me/hc/en-us/articles/retail-committed-inventory" rel="noopener noreferrer"&gt;BLAZE committed inventory documentation&lt;/a&gt; illustrates why these distinctions matter. It describes configurable online cart commitments, cart expiration, and changes as orders enter processing. It also documents an exception allowing an in-store purchase to override a commitment in an online cart that has not yet become a submitted order. These are BLAZE-specific behaviors, not rules to assume for IndicaOnline.&lt;/p&gt;

&lt;h3&gt;
  
  
  Separate physical stock from available stock
&lt;/h3&gt;

&lt;p&gt;A unit can remain on the shelf while being reserved for an order. Record physical quantity, reserved quantity, and available quantity separately wherever the system exposes them.&lt;/p&gt;

&lt;p&gt;If availability looks wrong, find the associated order before adjusting inventory. Increasing stock to compensate for an unexplained reservation can create a second problem when the original commitment is released.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test competing orders for the last available item
&lt;/h2&gt;

&lt;p&gt;Begin with a sequential test. Establish the reservation through an online channel, then attempt to purchase the same remaining item at the register. Record whether the sale is blocked, requires an override, or proceeds under a documented priority rule.&lt;/p&gt;

&lt;p&gt;Reverse the sequence. Process the register transaction first, then attempt the online order from a menu that was already open. Repeat the relevant scenario between your own website and another connected online channel.&lt;/p&gt;

&lt;p&gt;After the sequential checks, coordinate nearly simultaneous attempts. Record the order of actions and the identifiers of accepted orders. Do not rely on staff recollection to decide which request arrived first.&lt;/p&gt;

&lt;p&gt;The expected result must follow the configured reservation policy. A permitted override and an unexplained acceptance of conflicting orders require different responses.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check the order result, not just menu visibility
&lt;/h3&gt;

&lt;p&gt;Observe three separate outcomes: whether the item appears, whether it can enter a cart, and whether the order is accepted.&lt;/p&gt;

&lt;p&gt;A visible listing alone does not prove that unavailable inventory can be purchased. Conversely, removing an item from the menu does not establish what happens to carts opened earlier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test cancellation, quantity changes, and expiration
&lt;/h2&gt;

&lt;p&gt;Create a reservation and cancel the order through the normal workflow. Check when the item becomes available again at the register and across connected menus. Confirm that the canceled order no longer retains an active claim.&lt;/p&gt;

&lt;p&gt;Next, remove a product from an open order and reduce the quantity in another test. The released amount should match the change. Check unaffected items as well, since editing one line should not silently release the entire order.&lt;/p&gt;

&lt;p&gt;Test expiration only if the platform supports it and the setting is enabled. Use the configured period rather than inventing a deadline.&lt;/p&gt;

&lt;p&gt;Where supported, verify that a repeated cancellation action or integration retry does not release the same quantity again. Afterward, confirm both availability and order history. A restored number without an understandable transaction trail is an incomplete result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test stale menus and delayed synchronization
&lt;/h2&gt;

&lt;p&gt;Keep a customer-facing menu open while changing availability through another channel. Then attempt to continue shopping from that older view. Establish where the system checks inventory again and what happens if the requested quantity is no longer available.&lt;/p&gt;

&lt;p&gt;Coordinate any interruption or delayed-update simulation with the vendor in an approved test environment. Record when the source inventory changed and when each connected channel reflected it.&lt;/p&gt;

&lt;p&gt;Measure synchronization against confirmed integration behavior, not an assumed instant update. Ask the provider to explain expected timing and how failures become visible to staff.&lt;/p&gt;

&lt;p&gt;Also inspect the customer message. A clear unavailable-item response should leave staff able to identify the affected order. A generic error needs investigation if it is unclear whether an order or reservation was created.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check location boundaries before testing transfers
&lt;/h2&gt;

&lt;p&gt;For multi-store cannabis inventory management, repeat the availability check with the same product at another location. Stock elsewhere in the network should not automatically count as inventory that the selected store can fulfill.&lt;/p&gt;

&lt;p&gt;Confirm that changing the pickup location changes the inventory source as intended. Check existing carts after that change, including whether a reservation remains attached to the original store.&lt;/p&gt;

&lt;p&gt;If your operation uses inventory transfers, test availability before dispatch and after confirmed receipt under your established process. Do not assume that stock visible in transit is ready for sale.&lt;/p&gt;

&lt;p&gt;Centralized visibility helps staff locate inventory. The test must separately establish when that inventory becomes eligible for an order.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record failures so the team can reproduce them
&lt;/h2&gt;

&lt;p&gt;Use a consistent record for every scenario. Screenshots are helpful, but they need enough context to explain the sequence.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Record&lt;/th&gt;
&lt;th&gt;What to capture&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Inventory source&lt;/td&gt;
&lt;td&gt;Store, storage location, and product identifier&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Starting position&lt;/td&gt;
&lt;td&gt;Physical, reserved, and available quantities&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Order activity&lt;/td&gt;
&lt;td&gt;Channel, order identifier, status, and action time&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Expected result&lt;/td&gt;
&lt;td&gt;Behavior confirmed by settings or documentation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Actual result&lt;/td&gt;
&lt;td&gt;Accepted order, rejection, override, or unresolved state&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Follow-up&lt;/td&gt;
&lt;td&gt;Responsible person, correction, and retest outcome&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Separate a failure from an unanswered configuration question. If nobody can explain when a reservation should start, obtain that answer before marking the test as passed.&lt;/p&gt;

&lt;p&gt;Assign each mismatch to someone who can investigate the relevant system or integration. After a correction, repeat the original scenario with the same sequence. Close the issue only when staff can reproduce the intended result and account for the remaining inventory.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>IndicaOnline POS vs staff scheduling tools for dispensaries</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Fri, 20 Nov 2026 03:58:28 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/indicaonline-pos-vs-staff-scheduling-tools-for-dispensaries-2dig</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/indicaonline-pos-vs-staff-scheduling-tools-for-dispensaries-2dig</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/xqhtjgxnoyggpu7x9drl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/xqhtjgxnoyggpu7x9drl.png" alt=" " width="1731" height="909"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A budtender calls out before the afternoon rush. The manager finds someone to cover, but that employee also needs the right register access, clear instructions, and an accurate record of hours worked. Filling the empty slot solves only part of the problem.&lt;/p&gt;

&lt;p&gt;For dispensary managers, comparing a POS with staff scheduling software means following those separate tasks. Publishing next week’s roster, recording attendance, approving a refund, and reviewing sales require different controls. The useful comparison is how each tool handles the work your store needs done.&lt;/p&gt;

&lt;h2&gt;
  
  
  What IndicaOnline documents for store managers
&lt;/h2&gt;

&lt;p&gt;The official page for &lt;a href="https://indicaonline.com/roles/store-manager/" rel="noopener noreferrer"&gt;IndicaOnline dispensary manager software&lt;/a&gt; describes register shift controls, staff permissions, budtender performance reporting, and daily reports. These capabilities address decisions made while the store is operating: who can approve an action, what employees are selling, and what the manager needs to review at close. &lt;br&gt;
That operational focus matters when evaluating employee management software. Permission to work a scheduled shift and permission to perform a POS action are separate decisions. A replacement budtender may be available to cover the floor without being authorized to approve refunds or change inventory.&lt;/p&gt;

&lt;p&gt;IndicaOnline’s manager page also mentions shift scheduling. However, that reference alone does not explain every scheduling workflow. Before deciding whether an additional tool is necessary, ask for a demonstration of availability requests, published schedule changes, replacement shifts, and employee notifications. Treat undocumented details as questions to verify.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check in dedicated staff scheduling tools
&lt;/h2&gt;

&lt;p&gt;Start with the changes that create the most coordination work. A recurring availability restriction requires a different response from an unexpected absence after the roster has been published.&lt;/p&gt;

&lt;h3&gt;
  
  
  Availability and schedule changes
&lt;/h3&gt;

&lt;p&gt;Ask how employees submit availability and how managers distinguish a preference from approved time off. Then check what happens when availability changes after a shift has already been assigned.&lt;/p&gt;

&lt;p&gt;The demonstration should show the manager’s view and the employee’s view. Can both identify the current schedule? Does a revision require acknowledgment? If a manager edits a shift, check where the change appears and how the affected employee learns about it.&lt;/p&gt;

&lt;p&gt;For a dispensary, coverage also depends on assigned work. Someone available for checkout may still need instruction before handling receiving or closing responsibilities. Build the schedule around those assignments.&lt;/p&gt;

&lt;h3&gt;
  
  
  Shift swaps and manager approval
&lt;/h3&gt;

&lt;p&gt;A shift swap should have a clear status from request to approval. Managers need to know whether the original employee remains responsible while a replacement is being arranged.&lt;/p&gt;

&lt;p&gt;The official &lt;a href="https://help.wheniwork.com/articles/scheduling-settings/" rel="noopener noreferrer"&gt;When I Work scheduling settings documentation&lt;/a&gt; describes configurable options for releasing, dropping, and swapping shifts, including manager review and timing restrictions. Available settings depend on the account’s plan. This provides a concrete example of the scheduling controls to inspect during a comparison.&lt;/p&gt;

&lt;p&gt;Test a replacement request from both sides. Check who receives it, which employees can respond, and when the schedule becomes final. Do not assume that a scheduling approval also changes access in IndicaOnline POS.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scheduled hours and worked hours need separate checks
&lt;/h2&gt;

&lt;p&gt;A published roster records the staffing plan. A time record captures attendance. Those records can differ when someone arrives late, stays to finish closing, or covers only part of another employee’s shift.&lt;/p&gt;

&lt;p&gt;A schedule is not evidence of the hours actually worked. When comparing dispensary employee time tracking software, inspect how the system handles missing entries, corrections, and manager review.&lt;/p&gt;

&lt;p&gt;Use a realistic example: an employee finishes closing but forgets to clock out. Ask who can correct the entry, whether the original record remains visible, and how the revised hours reach the person preparing payroll.&lt;/p&gt;

&lt;p&gt;Keep payroll questions specific. Recording hours, exporting approved time, and calculating payroll are different capabilities. Confirm each required step rather than treating a time tracker as a complete payroll service. Apply the same scrutiny to IndicaOnline and any separate scheduling product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare the tools against the same store scenarios
&lt;/h2&gt;

&lt;p&gt;Feature lists become more useful when every vendor demonstrates the same task. Bring examples from your store and record what happens, including any manual handoff.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Store task&lt;/th&gt;
&lt;th&gt;What to verify&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Publish the roster&lt;/td&gt;
&lt;td&gt;Employees can identify their assigned shifts and the latest revision.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Replace an absent employee&lt;/td&gt;
&lt;td&gt;Requests, eligibility, approval, and final responsibility are clear.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Correct worked hours&lt;/td&gt;
&lt;td&gt;Authorized staff can review changes before hours are approved.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Approve a refund&lt;/td&gt;
&lt;td&gt;The POS applies the intended permission and approval process.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Review budtender sales&lt;/td&gt;
&lt;td&gt;The manager can identify the reporting period and employee attribution.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Close a register&lt;/td&gt;
&lt;td&gt;The manager can complete the required checks and review exceptions.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For IndicaOnline, distinguish the documented register, permission, and reporting capabilities from scheduling details still awaiting demonstration. For a dedicated scheduler, apply the same rule to claims about POS access, sales data, and payroll connections.&lt;/p&gt;

&lt;p&gt;Do not turn “not demonstrated” into “not available.” Mark unresolved capabilities for follow-up. That keeps the comparison fair and prevents a purchase based on assumptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep scheduling decisions separate from POS permissions
&lt;/h2&gt;

&lt;p&gt;Suppose an employee covers a shift at another location. The scheduling decision answers where and when that person will work. The access decision answers which records and actions they should be able to use there.&lt;/p&gt;

&lt;p&gt;IndicaOnline documents role-based permissions for actions such as discounts, refunds, and inventory access. Use that distinction when planning replacement coverage: verify the employee’s access before the shift begins, then review any temporary changes afterward.&lt;/p&gt;

&lt;p&gt;The same approach applies when a budtender temporarily takes on supervisory duties. Identify the additional approvals required and who authorizes them. A job title entered on a roster should not be treated as proof that the employee’s POS permissions have changed.&lt;/p&gt;

&lt;p&gt;If your store uses separate systems, assign responsibility for these checks. A manager should know who confirms coverage, who updates access, and who removes temporary permissions when the assignment ends. Avoid shared credentials as a shortcut for getting a replacement onto the register.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the workflow before adding another subscription
&lt;/h2&gt;

&lt;p&gt;Run a trial that follows an actual staffing change. Publish a shift, request a replacement, approve the change, verify register access, and review the resulting attendance record. Have the manager and employee complete their respective steps.&lt;/p&gt;

&lt;p&gt;Record every point where someone must re-enter information or send a separate message. Some manual work may be acceptable for your store. Repeated uncertainty about the current roster or approved hours deserves closer attention.&lt;/p&gt;

&lt;p&gt;Choose an additional tool around a demonstrated gap. If IndicaOnline supports your required process, evaluate whether another subscription adds enough value. If a dedicated scheduler handles availability or replacement coordination more effectively, confirm how your team will manage the boundary between systems.&lt;/p&gt;

&lt;p&gt;Before committing, write down where the approved schedule lives, where worked hours are reviewed, and who controls POS permissions. Then repeat the trial with a last-minute change. The result should give your closing manager a clear answer about who is working, what they can do, and which records still need attention.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Montana dispensaries should own their POS exports</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:07:55 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/why-montana-dispensaries-should-own-their-pos-exports-14o0</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/why-montana-dispensaries-should-own-their-pos-exports-14o0</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/images/nATWgQBtEnIJ5nHZoQD7oPao57sGaFvN2adgO5Na3e0/rt:fit/w:800/g:sm/q:0/mb:500000/ar:1/Li4u" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/images/nATWgQBtEnIJ5nHZoQD7oPao57sGaFvN2adgO5Na3e0/rt:fit/w:800/g:sm/q:0/mb:500000/ar:1/Li4u" alt="Uploading image" width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A dispensary owner needs to explain a refund from an earlier reporting period. The saved report contains a sales total, but no transaction reference connecting the adjustment to the original purchase. The file opens correctly. It still cannot answer the question.&lt;/p&gt;

&lt;p&gt;Montana dispensaries should treat usable exports as part of ordinary operations. Here, “own” means having an established way to obtain, store, and inspect the files your business needs. Contractual ownership rights are a separate question to review in your vendor agreement.&lt;/p&gt;

&lt;p&gt;When evaluating &lt;a href="https://indicaonline.com/markets/montana/" rel="noopener noreferrer"&gt;Indica Online cannabis software in Montana&lt;/a&gt;, request sample exports alongside the dashboard demonstration. Ask your inventory manager and bookkeeper to work through them. Their ability to explain a transaction is a more useful test than simply confirming that an export button exists.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make export access an operating requirement
&lt;/h2&gt;

&lt;p&gt;Define the work your files need to support. Examples include investigating a stock discrepancy, explaining a refund, checking a purchasing decision, or preparing information for a future system change. Each task requires an appropriate level of detail.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Export access should be tested while the store is operating normally.&lt;/strong&gt; Waiting until an urgent question arises leaves little time to discover missing fields or unfamiliar filters.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ask what staff can export without outside help
&lt;/h3&gt;

&lt;p&gt;Confirm which roles can request exports, which periods are accessible, and which file formats are available. Ask whether staff can obtain the relevant records themselves or must submit a support request.&lt;/p&gt;

&lt;p&gt;Document the process and test it with an authorized employee. Clarify any charges, access restrictions, or account conditions directly with the vendor rather than assuming that dashboard access includes unrestricted export access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Request records that explain the total
&lt;/h2&gt;

&lt;p&gt;Start with a specific question and identify the fields needed to answer it. For a refund investigation, those might include the original order reference, affected items, refund amount, status, and related payment reference.&lt;/p&gt;

&lt;p&gt;For inventory work, ask which identifiers connect a sale or receipt to the relevant product and package records. Verify that the export contains those connections instead of relying on product names that employees may have changed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep order, item, and payment relationships intact
&lt;/h3&gt;

&lt;p&gt;Look for stable references linking the order, its individual lines, and the associated payment activity. Ask what each reference represents and whether it remains usable across different reports.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://help.shopify.com/en/manual/fulfillment/managing-orders/exporting-orders" rel="noopener noreferrer"&gt;Shopify’s order export documentation&lt;/a&gt; illustrates why file structure matters. It describes separate order and transaction-history exports, and explains that additional items within an order appear on separate rows. These are Shopify-specific details; inspect your POS files independently.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A useful export preserves enough context to explain how records belong together.&lt;/strong&gt; If an employee must match purchases by approximate time and amount, identify what additional reference or supporting file would make the connection reliable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test completeness before trusting the file
&lt;/h2&gt;

&lt;p&gt;Record the filters used to create an export. Check the date range, location, selected statuses, and any other restrictions. Establish which timestamp controls inclusion and how the file represents time zones.&lt;/p&gt;

&lt;p&gt;Select known examples from the source system: a completed sale, a cancellation, and a refund. Find them in the export and compare their relevant fields with the original records. Investigate absent or unexpected entries before using the file for wider analysis.&lt;/p&gt;

&lt;p&gt;Distinguish an empty field from a confirmed zero. Ask whether blank values mean that information is unavailable, inapplicable, or recorded elsewhere.&lt;/p&gt;

&lt;h3&gt;
  
  
  Reconcile totals without counting the same order twice
&lt;/h3&gt;

&lt;p&gt;Determine whether each row represents an order, an item, or a payment event. A file containing several rows for one purchase needs different calculations from a file containing one row per purchase.&lt;/p&gt;

&lt;p&gt;Test your calculation on the selected examples before applying it to the full period. Compare equivalent totals with equivalent filters, keeping refunds, discounts, and other components distinguishable.&lt;/p&gt;

&lt;p&gt;A disagreement deserves investigation. Changing a spreadsheet calculation until it matches the dashboard can conceal a misunderstanding of the data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Store exports with enough context to reuse them
&lt;/h2&gt;

&lt;p&gt;Save the original file together with its extraction date, reporting period, filters, and source report name. Keep a short explanation of unfamiliar columns or status values with the same set of records.&lt;/p&gt;

&lt;p&gt;Use a working copy for sorting, formulas, and annotations. &lt;strong&gt;Preserve the original export so another reviewer can repeat the analysis.&lt;/strong&gt; A spreadsheet that has been edited without a record of the changes is harder to compare with its source.&lt;/p&gt;

&lt;p&gt;Choose a file-naming and storage approach that employees can follow consistently. The practical test is whether someone other than the person who downloaded the file can locate the correct version.&lt;/p&gt;

&lt;h3&gt;
  
  
  Assign access and a responsible owner
&lt;/h3&gt;

&lt;p&gt;Name the person responsible for obtaining and checking exports, and arrange coverage when that person is unavailable. Give colleagues access appropriate to their task.&lt;/p&gt;

&lt;p&gt;Review whether the file includes personal information before sharing it. An inventory investigation may need product and transaction references without requiring a customer’s contact details. Keep the scope of shared data aligned with the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat an export as one part of recovery planning
&lt;/h2&gt;

&lt;p&gt;Separate the ability to read a file from the ability to rebuild a working system. Ask which records, settings, attachments, and relationships an export actually contains.&lt;/p&gt;

&lt;p&gt;Before relying on files for migration or recovery, request a documented explanation of the destination’s import process. Test representative records and verify the result. A successful download alone does not establish that another application can reconstruct the original workflow.&lt;/p&gt;

&lt;p&gt;Keep an explicit list of what remains outside the files you have tested. That gives the person planning a transition a concrete set of questions to resolve.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep POS exports separate from required tracking records
&lt;/h2&gt;

&lt;p&gt;Use internal exports to support investigation and review while maintaining the required tracking processes for your Montana operation. A spreadsheet’s existence does not demonstrate that an underlying transaction was recorded correctly in every relevant system.&lt;/p&gt;

&lt;p&gt;Check applicable recordkeeping obligations separately before deciding what to retain or remove. A software export guide does not establish Montana retention requirements.&lt;/p&gt;

&lt;p&gt;If your analysis uncovers a discrepancy, preserve the evidence and route the correction through the appropriate authorized process. Editing the exported copy does not correct its source.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prove the workflow before you need it urgently
&lt;/h2&gt;

&lt;p&gt;Choose a manageable reporting period and export the records needed to explain a selected transaction. Ask another employee to locate the original sale, follow its related activity, and describe the final outcome without relying on your memory.&lt;/p&gt;

&lt;p&gt;Record any missing links or unclear fields and resolve them with the vendor. &lt;strong&gt;Make a repeatable explanation the acceptance criterion for your export process.&lt;/strong&gt; Once the employee can complete that task, document the steps and assign the next scheduled check.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Prepacked vs deli-style flower workflows in Oregon POS</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Mon, 09 Nov 2026 10:46:24 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/prepacked-vs-deli-style-flower-workflows-in-oregon-pos-459i</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/prepacked-vs-deli-style-flower-workflows-in-oregon-pos-459i</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/vi4p4bnql5tykde8qpul.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/vi4p4bnql5tykde8qpul.png" alt=" " width="1731" height="908"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A budtender scans a prepared flower package. At another counter, an employee weighs flower from bulk stock, prepares the customer’s container, and enters the quantity for sale. Both transactions sell flower, but the work behind them differs.&lt;/p&gt;

&lt;p&gt;For Oregon dispensary operators, the comparison starts with where measurement, packaging, and inventory changes occur. Prepacked flower moves some preparation ahead of checkout. Deli-style service places weighing within order preparation. Neither arrangement removes the need to verify what was received and sold.&lt;/p&gt;

&lt;p&gt;When evaluating &lt;a href="https://indicaonline.com/markets/oregon/" rel="noopener noreferrer"&gt;IndicaOnline cannabis software in Oregon&lt;/a&gt;, ask the vendor to demonstrate both workflows using your proposed setup. Follow the stock from receiving through sale and reconciliation. Compare the actions employees perform and the records managers can inspect afterward.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with how flower enters the inventory
&lt;/h2&gt;

&lt;p&gt;For prepacked flower, inspect the received package variant, quantity, and associated weight information. Confirm whether the receiving field represents individual retail units or another quantity.&lt;/p&gt;

&lt;p&gt;For bulk flower, inspect the recorded weight and its connection to the physical stock. Establish how staff identify the source record when preparing an order.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A correct product name does not establish a correct inventory connection.&lt;/strong&gt; Similar flower descriptions can conceal different packages or receiving records. Check those relationships before stock becomes available for sale.&lt;/p&gt;

&lt;h3&gt;
  
  
  Separate the product listing from the source package
&lt;/h3&gt;

&lt;p&gt;A catalog listing describes the product. A consumer container holds the purchased flower. A package record in the tracking workflow identifies inventory associated with its own reference.&lt;/p&gt;

&lt;p&gt;Do not assume those concepts map directly to each other. Ask the vendor to show which source record supports a prepared retail pack or a weighed portion.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare scanning a pack with weighing an order
&lt;/h2&gt;

&lt;p&gt;A prepacked workflow may involve selecting the correct variant, scanning its code, and confirming quantity. Verify that the scan identifies the intended product and weight rather than relying on similar packaging.&lt;/p&gt;

&lt;p&gt;A deli-style workflow requires staff to establish the quantity being sold during preparation. Inspect how the weight reaches the POS and how the employee confirms it.&lt;/p&gt;

&lt;p&gt;Avoid assuming that either workflow is always faster. Compare the actual preparation and checkout steps, including corrections, equipment handling, and the information needed to complete an order.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check tare and the weight passed to the POS
&lt;/h3&gt;

&lt;p&gt;Oregon’s Department of Agriculture explains the difference between net product weight and packaging weight, or tare, in its guidance on &lt;a href="https://www.oregon.gov/oda/agriculture-services/weights-measures/pages/operating-scale.aspx" rel="noopener noreferrer"&gt;operating a scale&lt;/a&gt;. It describes checking tare by placing the empty container on the scale and confirming a zero reading before filling it.&lt;/p&gt;

&lt;p&gt;Use that distinction when evaluating the weighing process. &lt;strong&gt;The quantity recorded for the flower should exclude its container.&lt;/strong&gt; Confirm whether weight transfers automatically or is entered manually, and compare the scale display with the POS record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make price rules match the selling method
&lt;/h2&gt;

&lt;p&gt;A prepared package may have a price attached to its specific variant. A weighed order needs a clear relationship between the measured quantity and the selling price.&lt;/p&gt;

&lt;p&gt;Ask the presenter to change the quantity and explain the resulting calculation. If the store uses quantity-based price levels, inspect which rule applies and how staff recognize it.&lt;/p&gt;

&lt;p&gt;Test a discount separately. Confirm whether it applies to the selected package, the weighed line, or the cart. Keep the expected result written down so an unfamiliar calculation does not become accepted merely because the screen displays it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Account for when packaging and labeling happen
&lt;/h2&gt;

&lt;p&gt;Prepared flower can arrive ready for retail handling or be packaged by the store before checkout. Deli-style preparation places packaging activity within the order workflow.&lt;/p&gt;

&lt;p&gt;Identify who prepares the container, checks the product information, and confirms that the packaging and labeling follow the applicable procedure. Include the equipment, supplies, and work area that each process needs.&lt;/p&gt;

&lt;p&gt;A printed label alone does not demonstrate that the underlying product information is correct. Inspect the connection between the flower selected, its measured or recorded quantity, and the information produced for the customer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow the inventory deduction through each workflow
&lt;/h2&gt;

&lt;p&gt;For prepacked sales, ask how a sold retail unit affects its associated inventory records. Check both the unit count and the weight information used by the system.&lt;/p&gt;

&lt;p&gt;For deli-style sales, follow the weighed portion back to its source balance. Confirm how the remaining stock is represented after the sale.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Trace the deduction to the source record as well as the overall product total.&lt;/strong&gt; A plausible total can hide an incorrect package connection or a movement recorded against the wrong stock.&lt;/p&gt;

&lt;h3&gt;
  
  
  Avoid counting bulk flower and prepared packs twice
&lt;/h3&gt;

&lt;p&gt;If staff prepare retail packs from bulk flower, ask how that preparation is recorded. Establish when the source quantity changes and when the prepared units become available.&lt;/p&gt;

&lt;p&gt;Check that the same flower has not remained fully available in bulk while also appearing as ready-to-sell packs. Then verify that selling a prepared pack does not cause an unintended additional deduction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare online availability and order picking
&lt;/h2&gt;

&lt;p&gt;For prepacked flower, test whether the menu offers the correct package variant and reserves the quantity needed for an accepted order.&lt;/p&gt;

&lt;p&gt;For deli-style flower, inspect how the requested quantity is reserved and what happens if the final prepared amount differs. Ask how staff communicate an unavailable quantity or proposed change.&lt;/p&gt;

&lt;p&gt;Do not assume that all POS systems reserve stock at the same stage. Follow the order through submission, acceptance, picking, and completion, checking availability at each relevant step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reconcile remaining packs and bulk weight separately
&lt;/h2&gt;

&lt;p&gt;Prepared stock may be checked through a retail-unit count alongside its associated inventory records. Bulk stock requires a physical weight comparison using the appropriate procedure.&lt;/p&gt;

&lt;p&gt;When a difference appears, review receiving, sales, preparation activity, and documented movements. Do not automatically attribute a shortage to changes in the flower itself.&lt;/p&gt;

&lt;p&gt;Keep the evidence connected to the affected inventory. An adjustment that makes the total match without explaining the cause can leave the same error ready to recur.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare the operational tradeoffs side by side
&lt;/h2&gt;

&lt;p&gt;Use a comparison sheet that reflects the work your store would perform.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Area&lt;/th&gt;
&lt;th&gt;Prepacked workflow&lt;/th&gt;
&lt;th&gt;Deli-style workflow&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Receiving&lt;/td&gt;
&lt;td&gt;Verify retail variants and quantities&lt;/td&gt;
&lt;td&gt;Verify source stock and weight&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Checkout&lt;/td&gt;
&lt;td&gt;Identify the prepared pack&lt;/td&gt;
&lt;td&gt;Confirm the weighed portion&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Equipment&lt;/td&gt;
&lt;td&gt;Check scanning and product identification&lt;/td&gt;
&lt;td&gt;Check weighing and weight entry&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Packaging&lt;/td&gt;
&lt;td&gt;Review preparation before sale&lt;/td&gt;
&lt;td&gt;Review preparation during order assembly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Online picking&lt;/td&gt;
&lt;td&gt;Match the ordered pack variant&lt;/td&gt;
&lt;td&gt;Confirm the requested quantity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reconciliation&lt;/td&gt;
&lt;td&gt;Inspect unit counts and source records&lt;/td&gt;
&lt;td&gt;Compare remaining weight and movements&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Include preparation work in the comparison. Moving a task away from the register changes where staff perform it; it does not necessarily eliminate the task.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test both workflows before choosing the configuration
&lt;/h2&gt;

&lt;p&gt;Use demonstration data or a test environment where available. Receive sample stock, complete a sale, change an order, and inspect the resulting inventory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose the configuration your team can operate and verify.&lt;/strong&gt; Have the employees responsible for preparation, checkout, and reconciliation repeat the relevant steps. Record unresolved questions about equipment, source-package connections, and availability, then request a follow-up demonstration that addresses those exact gaps.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Discount mistakes that erode Michigan dispensary margins</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Mon, 09 Nov 2026 10:39:19 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/discount-mistakes-that-erode-michigan-dispensary-margins-4faf</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/discount-mistakes-that-erode-michigan-dispensary-margins-4faf</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/lxpfz729lt1yji5suf99.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/lxpfz729lt1yji5suf99.png" alt=" " width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;An automatic promotion reduces an item’s price, then a budtender adds a manual discount to resolve a customer question. The receipt looks ordinary. The final price, however, is lower than the manager intended when approving the offer.&lt;/p&gt;

&lt;p&gt;For a Michigan dispensary, the problem may lie in the interaction between promotions, staff overrides, product costs, and reporting. Reviewing those connections gives managers something specific to correct.&lt;/p&gt;

&lt;p&gt;When evaluating &lt;a href="https://indicaonline.com/markets/michigan/" rel="noopener noreferrer"&gt;Indica Online cannabis software in Michigan&lt;/a&gt;, bring your actual discount scenarios to the demonstration. Ask the vendor to show how permitted combinations, restricted overrides, and partial refunds appear in transaction records. Compare the result with your written promotion rules.&lt;/p&gt;

&lt;h2&gt;
  
  
  Letting promotions combine without a clear policy
&lt;/h2&gt;

&lt;p&gt;A product offer, a cart promotion, and a customer-group discount can each have a reasonable purpose. Allowing them to combine without reviewing the result can produce an unintended selling price.&lt;/p&gt;

&lt;p&gt;Write down which combinations are allowed and which should be blocked. Identify exclusions, including products already carrying a reduced price.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://help.shopify.com/en/manual/discounts/discount-combinations" rel="noopener noreferrer"&gt;Shopify documentation on combining discounts&lt;/a&gt; illustrates why the details matter: its platform distinguishes discount classes, application order, and manual adjustments. Use those distinctions as questions for your own POS, rather than assuming another platform follows the same rules.&lt;/p&gt;

&lt;h3&gt;
  
  
  Check the calculation order, not just the labels
&lt;/h3&gt;

&lt;p&gt;Ask what amount each discount uses as its calculation base. Determine whether a later discount applies to the original price or an already reduced subtotal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Approve the resulting price alongside the promotion rules.&lt;/strong&gt; Save a test receipt showing the intended calculation so staff and managers can recognize an unexpected result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treating manual overrides as harmless exceptions
&lt;/h2&gt;

&lt;p&gt;A manual adjustment may solve a service issue while adding another reduction to an already discounted purchase. If employees cannot see the existing adjustments clearly, they may not realize what they are adding.&lt;/p&gt;

&lt;p&gt;Define acceptable reasons for overrides, who can approve them, and what record should explain the decision. Check whether your proposed configuration supports those controls.&lt;/p&gt;

&lt;p&gt;An exception process should also be usable during a shift. If approval is difficult to obtain, investigate the workflow before broadening access.&lt;/p&gt;

&lt;h3&gt;
  
  
  Distinguish discounts, credits, and payment methods
&lt;/h3&gt;

&lt;p&gt;A smaller amount due does not necessarily mean another discount was applied. Review how your system treats loyalty benefits, customer credits, and payment methods actually used by the store.&lt;/p&gt;

&lt;p&gt;Follow each component through the transaction and reporting. Avoid deducting an amount again during analysis when the reported selling price already reflects it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Setting sale prices without reliable product costs
&lt;/h2&gt;

&lt;p&gt;A promotion reviewed against an outdated cost can look healthier than it is. Before approving an offer, confirm where the product cost comes from and whether it represents the inventory being sold.&lt;/p&gt;

&lt;p&gt;Inspect unit definitions too. A cost associated with a shipment, package, or individual item needs to be interpreted correctly before it supports a pricing decision.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A margin report is only as useful as its inputs.&lt;/strong&gt; Resolve missing or uncertain costs before treating a displayed margin as evidence that an offer meets your objective.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep margin and markup separate
&lt;/h3&gt;

&lt;p&gt;Gross margin measures sales revenue minus cost of goods sold relative to sales revenue. Markup measures that difference relative to cost. Confusing them can lead staff to approve a price using the wrong benchmark.&lt;/p&gt;

&lt;p&gt;Also establish which costs your report includes. Gross margin does not represent the business’s final profit after every operating expense.&lt;/p&gt;

&lt;h2&gt;
  
  
  Leaving expired or overly broad promotions active
&lt;/h2&gt;

&lt;p&gt;An offer can continue reducing prices after its intended purpose ends. Broad category rules may also pull newly added products into a promotion nobody reviewed for them.&lt;/p&gt;

&lt;p&gt;Assign an owner to each offer. Check its active period, eligible products, customer conditions, and exclusions before publishing it and when relevant settings change.&lt;/p&gt;

&lt;p&gt;Review the live configuration alongside the advertised terms. An accurate promotional message does not establish that the checkout rules match it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Applying different rules across checkout channels
&lt;/h2&gt;

&lt;p&gt;An online offer and an in-store offer may intentionally differ. The problem arises when staff cannot distinguish that decision from an incorrect configuration.&lt;/p&gt;

&lt;p&gt;Compare the same eligible basket across the channels you use. Inspect the price, applied promotions, and any conditions the customer must meet.&lt;/p&gt;

&lt;p&gt;If staff compensate for a channel mismatch with a manual reduction, record the reason. Otherwise, the workaround can obscure the original fault and become another unplanned discount.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking the customer total without reviewing tax lines
&lt;/h2&gt;

&lt;p&gt;Separate the discounted merchandise amount, tax components, and final payment. A customer-facing total does not explain how each component was calculated.&lt;/p&gt;

&lt;p&gt;Have the person responsible for tax configuration review unclear treatment. Do not change tax settings simply to make checkout match a desired promotional total.&lt;/p&gt;

&lt;p&gt;Keep the comparison tied to the actual customer category and transaction conditions. A test basket that behaves as intended does not prove every variation receives the appropriate treatment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measuring promotion success by revenue alone
&lt;/h2&gt;

&lt;p&gt;Higher promotional revenue does not establish that the offer improved profitability. Review the actual selling prices, associated product costs, refunds, and items included in the purchases.&lt;/p&gt;

&lt;p&gt;Determine what question the offer was meant to answer. Clearing selected stock requires a different review from assessing whether a discount encouraged additional purchases.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do not credit the promotion with demand your records cannot establish.&lt;/strong&gt; If you lack a suitable comparison, describe the observed results without claiming the offer caused them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Test a partial refund on a discounted order
&lt;/h3&gt;

&lt;p&gt;Use demonstration data to refund part of a discounted purchase. Inspect how the discount is allocated, what remains on the order, and how the refund appears in reports.&lt;/p&gt;

&lt;p&gt;Ask the vendor to explain any recalculation. Do not assume the remaining basket retains its original eligibility or that every system handles the change identically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run a discount test before publishing the offer
&lt;/h2&gt;

&lt;p&gt;Write the expected outcome before testing. Keep the basket and customer conditions consistent so a difference can be traced to the rule being examined.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scenario&lt;/th&gt;
&lt;th&gt;Result to verify&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Ordinary eligible purchase&lt;/td&gt;
&lt;td&gt;Intended offer applies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Permitted combination&lt;/td&gt;
&lt;td&gt;Final price matches the approved calculation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Prohibited combination&lt;/td&gt;
&lt;td&gt;Additional reduction is prevented or flagged&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Manual adjustment&lt;/td&gt;
&lt;td&gt;Authorization and reason remain identifiable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Partial refund&lt;/td&gt;
&lt;td&gt;Remaining sale and refund can be explained&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Check the transaction record as well as the screen. If staff cannot reconstruct the calculation afterward, ask what additional reporting or documentation is needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with an unexplained low-margin sale
&lt;/h2&gt;

&lt;p&gt;Choose a sale whose result does not match the intended offer. Trace its original price, promotion sequence, manual adjustments, relevant credits, and recorded product cost.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Correct the established cause before changing the entire discount policy.&lt;/strong&gt; Update the affected rule, permission, or cost record through the appropriate process, then repeat the scenario. Give the promotion owner the verified result and identify any unresolved condition that still needs testing.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Receiving errors that distort New York dispensary stock</title>
      <dc:creator>Victoria Hodgson</dc:creator>
      <pubDate>Mon, 09 Nov 2026 10:34:30 +0000</pubDate>
      <link>https://community.ops.io/victoria_hodgson_8b0ee248/receiving-errors-that-distort-new-york-dispensary-stock-34i</link>
      <guid>https://community.ops.io/victoria_hodgson_8b0ee248/receiving-errors-that-distort-new-york-dispensary-stock-34i</guid>
      <description>&lt;p&gt;&lt;a href="https://community.ops.io/remoteimages/uploads/articles/0oiimju2u7q6bbtuh717.png" class="article-body-image-wrapper"&gt;&lt;img src="https://community.ops.io/remoteimages/uploads/articles/0oiimju2u7q6bbtuh717.png" alt=" " width="1732" height="908"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A pickup order reaches the packing station, but the employee cannot find the quantity shown in the POS. The delivery arrived earlier, and receiving looked complete. The discrepancy may have started before the product ever appeared on the menu.&lt;/p&gt;

&lt;p&gt;Receiving errors can spread into availability, purchasing records, and later inventory counts. Finding the cause means tracing the affected stock back to its delivery rather than repeatedly adjusting the balance.&lt;/p&gt;

&lt;p&gt;When evaluating &lt;a href="https://indicaonline.com/markets/new-york/" rel="noopener noreferrer"&gt;IndicaOnline dispensary software in New York&lt;/a&gt;, ask the vendor to demonstrate receiving and correcting a shipment discrepancy. Follow the physical product, package reference, and resulting inventory record. Check what staff can verify when the process produces an unexpected result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Accepting the manifest quantity without checking the delivery
&lt;/h2&gt;

&lt;p&gt;A manifest records the expected shipment. It does not replace inspecting what arrived. Accepting its quantity without a physical check can bring a shortage or excess into the store’s recorded balance.&lt;/p&gt;

&lt;p&gt;Compare the delivered product with its package references and shipment records before completing receiving. Make the person responsible for resolving discrepancies identifiable, especially when receiving and purchasing are handled by different employees.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The accepted quantity needs evidence from the actual delivery.&lt;/strong&gt; If something does not match, establish which record or physical count is wrong before selecting a correction.&lt;/p&gt;

&lt;h3&gt;
  
  
  Separate a delivery variance from a data-entry error
&lt;/h3&gt;

&lt;p&gt;A shortage in the delivered package differs from an employee entering an incorrect quantity after a correct delivery. The symptoms may look similar in the POS, but the investigation starts in different places.&lt;/p&gt;

&lt;p&gt;New York’s Office of Cannabis Management addresses shipment discrepancies in its bulletin on &lt;a href="https://cannabis.ny.gov/system/files/documents/2026/04/sts-bulletin-18.pdf" rel="noopener noreferrer"&gt;accepting transfers in Metrc when there is a variance&lt;/a&gt;. It describes different handling options for mismatched quantities and says financial records must reflect the inventory actually accepted.&lt;/p&gt;

&lt;p&gt;Use the applicable guidance to determine the handling process. Do not assume a general stock adjustment is the right response to every discrepancy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Matching the right product to the wrong package
&lt;/h2&gt;

&lt;p&gt;A familiar product name can encourage staff to select an existing record without checking the package connection. Similar packaging or repeated deliveries can make the mistake harder to spot.&lt;/p&gt;

&lt;p&gt;Verify the product variant and physical package reference against the record being received. Then inspect where the resulting quantity appears. A correct store total can still conceal stock attached to the wrong package.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep the catalog record separate from the received package
&lt;/h3&gt;

&lt;p&gt;The catalog describes the product. A received package represents a particular inventory record associated with that product. Sharing a catalog description does not make separate packages interchangeable.&lt;/p&gt;

&lt;p&gt;Ask staff to demonstrate how they identify the package behind an available item. If the answer depends on memory or an informal note, clarify the workflow before another receipt adds more uncertainty.&lt;/p&gt;

&lt;h2&gt;
  
  
  Confusing cartons, retail units, and weight
&lt;/h2&gt;

&lt;p&gt;Receiving fields can be misunderstood when shipping containers, individual products, and weight appear in the same workflow. A number entered under the wrong unit can distort quantity without looking obviously incorrect.&lt;/p&gt;

&lt;p&gt;Check what each quantity field represents. Compare it with the product’s packaging and the unit used in the source records.&lt;/p&gt;

&lt;p&gt;Review cost fields separately. Determine whether the amount refers to a unit, a package, or the shipment. A correct physical quantity paired with an incorrectly interpreted cost can still mislead purchasing and margin reports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Receiving the same shipment more than once
&lt;/h2&gt;

&lt;p&gt;A receiving screen stops responding. An employee cannot tell whether the action completed, so they import the shipment again or create a manual entry.&lt;/p&gt;

&lt;p&gt;Before retrying, search for the shipment and affected package references. Inspect the history and resulting stock rather than treating an absent confirmation message as proof that nothing happened.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An uncertain result is a reason to verify, not automatically repeat.&lt;/strong&gt; Record how staff should investigate interrupted receiving and who handles a result they cannot establish.&lt;/p&gt;

&lt;h3&gt;
  
  
  Verify completion before retrying
&lt;/h3&gt;

&lt;p&gt;Where receiving involves connected systems, inspect the relevant status in each. Determine whether the record exists, whether an exchange remains pending, and whether further action could duplicate existing work.&lt;/p&gt;

&lt;p&gt;Ask the vendor to explain recovery for the specific interruption. Avoid combining manual entry and repeated imports without understanding what each action will create.&lt;/p&gt;

&lt;h2&gt;
  
  
  Making unresolved stock available for sale
&lt;/h2&gt;

&lt;p&gt;An unresolved receiving discrepancy becomes more disruptive when the affected quantity appears online or at checkout. Staff may accept orders based on inventory they have not verified.&lt;/p&gt;

&lt;p&gt;Establish who decides when the product is ready for sale under the store’s applicable procedures. Check how the system represents stock awaiting review and whether that status affects customer-facing availability.&lt;/p&gt;

&lt;p&gt;Do not assume a software status establishes product eligibility by itself. The operational check is whether the responsible employee has resolved the relevant questions and confirmed the supported quantity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Correcting the total without finding the cause
&lt;/h2&gt;

&lt;p&gt;An overall adjustment can make a report match the shelf while leaving the original error intact. The problem might be a duplicate receipt, incorrect package connection, or misunderstood unit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Find the cause before choosing the correction.&lt;/strong&gt; Trace the affected quantity through the receiving history and supporting records. Explain the discrepancy in terms another employee can follow.&lt;/p&gt;

&lt;p&gt;Assign correction rights to the appropriate role. The person discovering a mismatch should know how to escalate it without making an unexplained change merely to finish the task.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep the correction connected to its evidence
&lt;/h3&gt;

&lt;p&gt;Retain the receiving reference, affected package, count result, reason for the correction, and any approval used in your process. Confirm which information the system preserves and what needs separate documentation.&lt;/p&gt;

&lt;p&gt;A note saying “fixed inventory” provides little help during the next review. Describe what was wrong and how the correction addresses it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the result across inventory, menus, and purchasing records
&lt;/h2&gt;

&lt;p&gt;After the authorized correction, compare the physical count with the affected inventory records. Inspect the package connection as well as the overall product quantity.&lt;/p&gt;

&lt;p&gt;Next, check availability at the register and online, where applicable. Confirm that the menu reflects the intended sellable quantity rather than assuming an internal correction has already reached it.&lt;/p&gt;

&lt;p&gt;Review the related purchasing documents with the person responsible for them. An inventory correction does not necessarily update an invoice or resolve a supplier dispute.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Close the issue when the related records support the same accepted delivery.&lt;/strong&gt; Leave any remaining mismatch assigned to someone who can resolve it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn a recurring discrepancy into a receiving check
&lt;/h2&gt;

&lt;p&gt;Choose a receiving error that has repeated and identify the point where staff could have detected it earlier. Add a specific check at that step, with an owner and a clear expected result.&lt;/p&gt;

&lt;p&gt;Apply it to the next comparable delivery. Follow the accepted stock into its package record, availability, and purchasing documentation, then confirm that the earlier error has not reappeared.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
