Written by DROPS.ST.
Choose one approved product record as the source for your shop. Give someone responsibility for its factual fields, keep a reference to the supporting information and check how the record appears wherever customers use it.
DROPS supports this approach with a shared catalogue for the website and connected Telegram shop. Product work belongs in the shop record, rather than in separately maintained channel descriptions. DROPS website and Telegram features.
The shared record provides the foundation. Your team still needs to decide which information is correct, who approves it and when a change is ready.
Define the record customers are ordering from
A product description should help identify the item and explain what the listed price buys. Start with factual information before polishing the wording.
For each product, establish its identifier, name, category, selling unit and pack details. Use the supplier’s current product specification or other appropriate source for those facts. Record where the information came from.
Keep commercial presentation separate from the source material. A supplier document may contain information irrelevant to the menu, outdated text or claims you have not approved.
Do not let a short description introduce facts absent from the approved full record. Avoid filling gaps with guessed composition, effects, safety or health claims.
Separate stable facts from changing values
Use a compact field checklist when preparing or reviewing a record.
| Field | Record decision | Check before approval |
|---|---|---|
| SKU or product reference | Which item does this identify? | Reference distinguishes similar products |
| Name | What must appear to identify the item? | Pack or size differences remain clear |
| Unit and pack details | What does one ordered unit contain? | Quantity meaning is explicit |
| Short description | What must be understood in the listing? | Text agrees with the full description |
| Full description | Which approved details need explanation? | Facts have a recorded source |
| Image | Which file represents this item? | Product and pack match the record |
| Price and availability | Who maintains current commercial values? | Values match the intended selling unit |
Treat price and stock as maintained values rather than sentences scattered through descriptive copy. Repeating a price inside several paragraphs gives staff additional places to update.
If wholesale packages are used, identify each package clearly. Check what its quantity means before writing “one unit” or “one pack.”
Name an owner and a review path
Assign someone to maintain the approved facts. That person needs a way to receive corrections from staff and resolve conflicting supplier information.
For each material revision, record what changed, why it changed and who approved it. A simple version reference such as “description revision 4” can help a team compare copies. This is a recommended working method, not a claim that every shop platform provides version history.
Keep the version record outside customer-facing text. Customers need the current description, not your editing notes.
Decide which changes require review. Correcting an obvious typing error differs from changing a pack quantity or replacing a product specification.
Also match editing access to the authority it actually grants. In the current DROPS setup, catalogue-edit access also covers customer-account edits and wallet adjustments. Do not treat it as a narrow description-editing role. Use a named editor and a review process that fits that broader access.
The store manager permissions checklist helps evaluate that decision.
Check the mobile presentation as a customer would
An approved record can still become confusing when displayed.
On a phone, inspect the menu listing before opening the full details. Can you distinguish similar items? Does the selling unit remain visible? Is the short description useful without repeating the title?
Then inspect the product detail view. Check paragraph breaks, image clarity and whether essential pack information is easy to find. Look for missing characters, broken formatting or content hidden behind controls.
Add the product to a test cart where an agreed test workflow permits it. Compare the item name, quantity meaning and price with the record you approved.
When Telegram ordering is connected, repeat the relevant checks there. Sharing catalogue data is a reason to maintain one record; it does not remove the need to inspect each presentation.
Account for copies outside the shop
A printed menu, image card or in-store screen may contain a separate copy of the description. Put those surfaces on an update list.
For each, record who prepares it, which product record it uses and how a correction reaches it. A shop update should not be assumed to change an exported image or an independently managed display.
If a supplier offers a display integration, ask for a demonstration of the actual connection and its update behavior. DROPS catalogue support alone does not establish real-time signage synchronization.
Check older copies when changing pack details or product identity. Leaving a previous image card in circulation can create ambiguity even after the shop record is corrected.
Hypothetical example: a pack label changes
A shop has a website listing, connected Telegram menu and a manually prepared screen slide for one product.
The approved specification changes the pack label. The named editor updates the shop record and the team inspects both shopping views. The screen slide is a separate file, so its owner replaces that copy and records the new description revision.
This hypothetical workflow illustrates an ownership decision. It is not a claim that DROPS automatically updates independent displays or that this process produced a measured result.
Make one record the centre of daily work
DROPS is a strong fit for owners who want product maintenance connected to the shop customers actually order from. Names, descriptions, prices, units, images, categories and stock have a place in the catalogue. Website and connected Telegram ordering share that catalogue.
That gives the team a practical starting point: prepare the correct record once, inspect its presentation and handle independent copies deliberately. You can spend the review on the product information rather than comparing separately maintained shop menus.
Use the menu software requirements guide when deciding which fields and displays your business needs.
See DROPS and explore demo shops. Open similar products on a phone, inspect their units and descriptions, and compare the details with what you would need your own customers to understand.