The Ops Community ⚙️

Victoria Hodgson
Victoria Hodgson

Posted on

How to test cannabis inventory reservations across channels

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.

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.

Map which inventory each channel can sell

When assessing cannabis multi-channel selling capabilities, 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.

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.

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.

A shared catalog does not necessarily mean a shared pool of available inventory. Establish that relationship before interpreting any result.

Define when a reservation should begin and end

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.

The official BLAZE committed inventory documentation 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.

Separate physical stock from available stock

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.

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.

Test competing orders for the last available item

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.

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.

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.

The expected result must follow the configured reservation policy. A permitted override and an unexplained acceptance of conflicting orders require different responses.

Check the order result, not just menu visibility

Observe three separate outcomes: whether the item appears, whether it can enter a cart, and whether the order is accepted.

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.

Test cancellation, quantity changes, and expiration

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.

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.

Test expiration only if the platform supports it and the setting is enabled. Use the configured period rather than inventing a deadline.

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.

Test stale menus and delayed synchronization

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.

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.

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.

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.

Check location boundaries before testing transfers

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.

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.

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.

Centralized visibility helps staff locate inventory. The test must separately establish when that inventory becomes eligible for an order.

Record failures so the team can reproduce them

Use a consistent record for every scenario. Screenshots are helpful, but they need enough context to explain the sequence.

Record What to capture
Inventory source Store, storage location, and product identifier
Starting position Physical, reserved, and available quantities
Order activity Channel, order identifier, status, and action time
Expected result Behavior confirmed by settings or documentation
Actual result Accepted order, rejection, override, or unresolved state
Follow-up Responsible person, correction, and retest outcome

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.

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.

Top comments (0)