The Ops Community ⚙️

Victoria Hodgson
Victoria Hodgson

Posted on

Why Montana dispensaries should own their POS exports

Uploading image

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.

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.

When evaluating Indica Online cannabis software in Montana, 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.

Make export access an operating requirement

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.

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

Ask what staff can export without outside help

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.

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.

Request records that explain the total

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.

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.

Keep order, item, and payment relationships intact

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.

Shopify’s order export documentation 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.

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

Test completeness before trusting the file

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.

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.

Distinguish an empty field from a confirmed zero. Ask whether blank values mean that information is unavailable, inapplicable, or recorded elsewhere.

Reconcile totals without counting the same order twice

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.

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.

A disagreement deserves investigation. Changing a spreadsheet calculation until it matches the dashboard can conceal a misunderstanding of the data.

Store exports with enough context to reuse them

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.

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

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.

Assign access and a responsible owner

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

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.

Treat an export as one part of recovery planning

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.

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.

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.

Keep POS exports separate from required tracking records

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.

Check applicable recordkeeping obligations separately before deciding what to retain or remove. A software export guide does not establish Montana retention requirements.

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.

Prove the workflow before you need it urgently

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.

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

Top comments (0)