Written by DROPS.ST.
A price and a positive stock figure are not enough to explain whether a product should appear in a particular customer menu. Check the product’s identity, active status, category and intended customer context, then compare the listing, detail and ordering results.
DROPS organizes product names, units, SKU references, stock, active status and categories in one catalogue. Quantity limits and wholesale packages give your team specific ordering choices to investigate.
Verify the applicable filtering behavior in the proposed configuration; the branches below are a diagnostic sequence.
Describe the missing item precisely
Start with the expected view. Record the shop address, product reference, displayed name, selected category, search or filter, customer account state and channel. Include the observation date and time.
“Missing from the menu” can mean several things:
- Absent from a category listing.
- Absent from search results.
- Accessible through a product link but difficult to discover.
- Visible, but without an available ordering choice.
- Present on the website but absent from the connected Telegram view.
Work through a visibility decision tree
Follow these branches in order. At each stage, retain the observation before making an authorised correction.
1. Is this the intended product record?
Compare SKU, unit and package first. Similar names or a price on another record do not establish identity.
2. Is the record active for the intended use?
Establish why it is inactive before changing it. Withdrawal or incomplete launch review may be intentional.
3. Is its category assignment appropriate?
Check the intended category and this shop's display rules; absence from one category does not establish global invisibility.
4. Does the customer context match the intended view?
Compare account state, selected menu, filters and channel. Where access restrictions apply, verify them through an authorised test. Do not remove them to prove that a product exists.
5. Is the problem visibility or orderability?
If the item is visible but cannot be added, investigate its units, package choice, stock and quantity limits. That is not the same as a missing listing.
6. Does the observed result remain unexplained?
Prepare a focused support report containing the product reference, expected view, actual result and checks completed. Mark an untested branch as unknown rather than treating it as ruled out.
Treat vendor rules as specific to the vendor
BLAZE documents category, inventory and price requirements for its own menu. These do not establish DROPS filtering rules. BLAZE Canada: getting started
A website connected to a POS also needs a separate transfer investigation. Use the POS and website menu-accuracy guide when a known source value disagrees with the shop, rather than assuming every absence is a delayed update.
Keep comparable observations
Record “not tested” where access or a safe test is unavailable. A staff view is not evidence of what an ordinary customer sees.
Compare the affected SKU with an unaffected item where useful, keeping the customer context consistent.
Hypothetical example: present in detail, missing from a category
A test item has a price and twelve units in its catalogue record. Staff expect it in “Accessories,” but the customer category view does not show it.
The tester checks the same item through its available product link and finds it visible. Its catalogue category is “Supplies,” not “Accessories.” The team then confirms which category the owner intended.
An authorised correction to that assignment is followed by another customer check. The record was not globally invisible, and changing stock would not have addressed the category discrepancy.
Correct the cause without widening access
Change one justified field or setting, then repeat the same view and item check. Keep the original observation so staff can explain what changed.
Use the consistent product-descriptions guide for naming and unit clarity, and the menu permissions guide for correction access.
Do not publish duplicate products as a workaround before understanding the original record. A second item can create a new stock or ordering ambiguity.
Make the menu easier to manage with DROPS
Choose DROPS when you want product details, stock, categories and order context organised in one shop. Connected Telegram shopping uses the same catalogue and order system, so your team can investigate the same product reference across the enabled channels.
Explore DROPS and open the demos. Bring one product and inspect its listing, detail and quantity choices against the intended catalogue decisions.