Written by DROPS.ST.
For an authorised cannabis-vape operator, a stock buffer starts with the meaning of the recorded quantity. Define which units are eligible, already committed or deliberately held outside the sellable amount before testing competing checkout requests.
DROPS provides tracked product quantities shared by the website and connected Telegram shop. Its ordering path sums quantities for the same product across package rows, then applies a guarded stock deduction. That gives the team a specific stock basis and rejection behaviour to evaluate.
This is not an autonomous physical-stock buffer or external POS synchronisation: low-stock display thresholds are different from the quantity the ordering path can sell.
Choose one explicit stock basis
Identify the product, stock unit and source of the starting figure. Distinguish a physical count from a recorded quantity already reduced by existing shop orders.
Define which commitments or held units are already reflected in that figure. Do not subtract them twice. A supplier possibility or unreviewed future receipt should not quietly become current sellable stock.
Keep the buffer as an approved planning choice with its reason and owner. Do not present an arbitrary number as a recommended safety margin for every operator.
The count-and-adjustment guide assigns authority for the underlying stock record. This guide tests the reviewed sellable basis against checkout behaviour.
Use a physical-to-sellable review sheet
This original aid separates quantities before the supported stock figure is changed or tested.
| Quantity or decision | Basis to record | Check before launch |
|---|---|---|
| Starting figure | Physical count or existing recorded amount | Exact product and stock unit identified? |
| Existing shop commitments | Relevant orders and current states | Already deducted from the chosen figure? |
| External commitments | Approved quantity and source | Included without double counting? |
| Reviewed buffer | Explicit quantity, reason and owner | Held outside the intended sellable amount? |
| Planned stock value | Reconciled sellable basis | Appropriate authorised update process? |
| Tracking mode | Tracked or unlimited behaviour | Guarded-stock test actually applicable? |
| Competing requests | Same product and defined quantities | Rejection and resulting records explainable? |
Keep the original calculation and source references. An unexplained stock edit cannot tell the next person whether units were sold, held or counted differently.
Hypothetical example: avoid subtracting a hold twice
A fictional product has ten units on its approved physical basis. Two units are already associated with shop orders, and the current recorded quantity is eight because that deduction is reflected.
An external commitment of one unit and a reviewed buffer of two units are not yet reflected. Under those assumptions, the planned sellable amount is 8 − 1 − 2 = 5 units.
Using the physical basis gives the same result: 10 − 2 − 1 − 2 = 5. Starting from eight and subtracting the shop-held two again would count that hold twice.
These figures illustrate a reviewed basis, not a recommended buffer, actual stock record or automatic DROPS buffer calculation.
Test the deduction, not the low-stock badge
In the current tracked-stock path, the server checks the combined requested quantity for a product. The deduction requires enough stock for that quantity; a failed deduction returns an unavailable-quantity result and rolls back the attempted order transaction.
A low-stock badge or threshold does not perform that calculation. Do not describe a presentation threshold as units automatically withheld from checkout.
For an approved fictional test with five sellable units, two competing requests for four units each exceed the available total. Inspect the actual supported result and confirm that accepted, rejected and remaining quantities reconcile under the defined test conditions.
Source inspection supplies the contract to test, not a completed concurrency test or universal overselling guarantee. Untracked products and another external stock system need separate treatment.
Keep packages on the same stock unit
DROPS' standard package matrix sums row quantities at product level. A package name does not establish a physical case-conversion multiplier or independent variant stock.
Use the wholesale quantity guide to define units and package meaning. If the intended selections use incompatible physical units, establish a supported conversion arrangement before relying on the deduction.
Do not compensate for an unexplained stock result by editing quantities until the screen looks right. Preserve the test evidence and assign the discrepancy to the authorised reviewer.
Review changed commitments and restored stock
A later cancellation or authorised adjustment can change the record. Check whether the current basis still includes the intended buffer and external commitments; a numerical increase does not by itself explain their treatment.
Use the shared-commitment guide for external partner promises and the menu incident record for conflicting source values.
Record the chosen launch basis and remaining questions. A successful ordinary selection is not evidence that the competing-request case passed.
Ground stock-buffer testing in DROPS
Choose DROPS when the approved stock basis should feed common website and Telegram selections, with product-level quantities and guarded deductions behind the order. That specific relationship makes the proposed buffer reviewable.
Open the DROPS demos with the fictional five-unit case. Inspect tracking, units and supported rejection behaviour, then agree any safe controlled test separately. Choose a process in which the physical basis, sellable quantity and outstanding commitments remain explainable.