Written by DROPS.ST.
Assign one person to resolve a POS/website discrepancy. Compare the same item, unit and customer context at recorded times. Correct its agreed source and verify the customer menu again.
DROPS organizes products, prices, images and stock in one catalogue, with customer-linked order items. Connected Telegram uses the same shop data, giving the investigation a common shop-side record.
Verify any external POS transfer method, timing and ownership separately; a shared shop catalogue does not establish that connection.
Name the owner before debating the vendor
The incident owner keeps evidence together, assigns the next action and confirms the result, even when others make the correction.
Separate three responsibilities:
- Business decision: what the item, price and available quantity should be.
- Data correction: who may change the authoritative record or transfer.
- Customer check: who verifies the menu and relevant ordering path afterward.
Agree who can make corrections using the store-manager menu permissions guide. Do not distribute broad access simply to make a discrepancy easier to investigate.
Choose a source for each disputed field
Neither the counter system nor a later website timestamp proves correctness. Establish the owner and checked source for each field.
For stock, distinguish a physical count from a quantity intended for online sale. For price, identify the applicable unit, package and business context. Two correct figures can look inconsistent if one describes cases and the other describes units.
The UK Government Data Quality Framework distinguishes accuracy, consistency and timeliness. That distinction is useful here: matching figures can still be wrong, and an accurate earlier figure can be unsuitable for a current menu. Government Data Quality Framework.
Capture an incident record that support can use
| Record | Capture | Purpose |
|---|---|---|
| Item | SKU, name, pack | Match identity |
| Source | Value, unit, location | Establish authority |
| Website | Value and address | Show discrepancy |
| Times | Date, time, zone | Explain sequence |
| Context | Account, filters, channel | Match the view |
| Transfer | File or connection reference | Identify handoff |
| Earlier view | Last known correct observation | Narrow change window |
| Owner | Person, next action, review | Continue resolution |
Distinguish change time from observation time. If the source update time is unavailable, label it unknown.
Capture only the disputed fields and remove customer information. Give support a specific reference, value, view and timestamp.
Reproduce before changing several settings
Reopen the exact product and customer context, checking address and filters. Compare listing and details against the source.
Identify the actual import file or connection evidence and its timing; do not assume a scheduled transfer succeeded.
Vendor-specific causes require the actual connection documentation. Consult Dutchie: menu sync and product display and verify the applicable mechanism before treating it as a DROPS setting.
Apply the same field-level source check to an incorrect category or another documented mapping error. If the external system is an ERP, verify its actual transfer method and scope separately; the shop catalogue does not establish an ERP connection.
Hypothetical example: a stale file, not a slow menu
At 10:00 UTC, an authorised stock check records fourteen units of a test item. At 10:07, the website still displays twenty.
The incident owner finds that a manual import at 10:05 used a file prepared at 09:40, when the value was twenty. The website received an older value after the stock check.
The correction is to reconcile that item against the approved source and fix the file-selection handoff. Repeatedly refreshing the website would not repair the stale input.
Record the correction and later customer view, and check whether other items were affected.
Close the incident with evidence of the correction
Make the smallest authorised correction. Avoid replacing an entire catalogue when one field is wrong, especially while unrelated orders or staff changes may be occurring.
Repeat the original customer check with the same SKU, unit and context. Record the outcome and observation time. If another channel is in scope, verify that view too; a shared catalogue does not mean every existing screen refreshes instantly.
Keep the cause and prevention action together. Examples include identifying the approved import file, clarifying field ownership or improving the support handoff. Use the menu migration checklist for a larger transfer rather than turning each incident into a full migration.
Keep the shop record clear with DROPS
DROPS keeps the web and connected Telegram catalogue with customer-linked orders. Your team can compare the item, customer selection and resulting record within one shop.
Explore DROPS and open the demos. Bring one disputed item, inspect its shop records and agree how external POS information enters the system.