Product identity

Stable Product Identifiers: Keep Assortment Changes Clear

Decide when a product change keeps its reference and when it needs a new one. Use a register for temporary gaps, replacements and discontinued items.

DROPS.ST

Web + Telegram. One catalogue.

Run the same catalogue on your website and connected Telegram shop.

Explore DROPS See the shop demo

Written by DROPS.ST.

Keep a product's working reference when its identity stays the same. When a change creates a genuinely different item, give it a distinct reference and record the relationship. Treat a temporary availability gap, a replacement and a permanent discontinuation as different decisions.

DROPS gives those decisions a useful home: products, units, prices and stock belong to one catalogue used by the website and connected Telegram shop. Clear product identity helps your team maintain that catalogue without turning each assortment change into another ambiguous listing.

Distinguish a reference from a display name

A product reference answers “which item is this?” A display name helps someone recognize the item on the menu. They serve different purposes.

A title correction may leave identity unchanged. A familiar title does not prove that a new pack, specification or unit is the same item.

Choose a working reference your team can use consistently. If you use SKUs, document what they identify. Keep supplier references alongside your own where needed rather than assuming they are interchangeable.

Use a small reference register

Keep an owner-managed register explaining why a familiar item retained or changed its reference.

Entry Record Decision
Reference Item and selling unit Intended record
Earlier label Name or supplier reference Same identity?
Availability Current business decision Gap or discontinuation?
Reason/date Factual change explanation Keep or replace reference?
Related reference Separate pack or replacement Relationship, not equivalence
Owner Identity reviewer Resolve uncertainty

Do not fill a replacement field merely because another item is available. A related product remains a separate product unless the identity decision says otherwise.

Decide what kind of change you have

Presentation correction: the item and unit are unchanged, but its name, description or image needs correction. Preserve the working reference and update the approved information.

Temporary gap: the item is expected to remain part of the assortment, but it is not currently available. Record the availability decision. Avoid inventing a return date where none is confirmed.

Different pack or item: the quantity meaning, specification or product identity changes. Assess it as a distinct record and define its reference before adding it to the catalogue.

Permanent discontinuation: record the withdrawal and any separate replacement. Choose supported availability or visibility controls deliberately; deletion is not an assumed solution.

Uncertain identity: the available information cannot establish whether the new item matches the existing record. Hold the decision with a named owner rather than reusing a reference for convenience.

When supplier records conflict, preserve both versions, request clarification and document the approved relationship. Matching names alone cannot settle a product-identity dispute.

Protect the meaning of earlier records

Before repurposing an existing product record, consider orders and staff references that already point to it. An old reference should not quietly become the name of an unrelated new item.

Ask the provider how product changes affect existing order displays and item details. Do not assume historical descriptions are frozen or that a renamed record preserves every previous view.

Keep your register's old-to-current relationship readable. If an item ends, record that fact; if another item replaces it operationally, retain the distinction between them.

Check the actual item when supplier references change, and check units/packs even when labels remain unchanged.

Hypothetical example: a familiar name, a different unit

A shop has fictional item TRAINING-PACK-A. A new supply offer uses the same short name, but one ordered unit contains a different pack quantity.

The catalogue owner compares the specifications and decides the new pack is a distinct item. They assign TRAINING-PACK-B, record its unit and relate it to the older item in the register.

The older reference remains associated with its original identity. Staff can explain the difference without saying that two packs with the same name are interchangeable.

Make a changed assortment readable on a phone

After applying an approved catalogue change, inspect the listing and details on a phone. Similar products should be distinguishable before someone chooses a quantity.

Check the displayed name, unit, image and availability together. A distinct reference in a staff spreadsheet is insufficient if the customer-facing listings still look identical.

Where Telegram shopping is connected, inspect that view too. Shared data gives the two channels a common catalogue; each presentation still needs checking.

Use the consistent product descriptions guide for maintaining the approved facts. If the catalogue is moving to another platform, the migration checklist covers source-to-destination mapping, a different decision from ongoing assortment identity.

Choose a shop you can keep understandable

DROPS is a strong fit for owners who want assortment decisions reflected in one shop catalogue, rather than repeated across independent website and Telegram menus. Product fields, stock and customer-linked orders give the team concrete records to work with.

Bring two similar products and a discontinued item. Check how they display and how changes affect existing records.

Explore DROPS and view the demos. Follow a product into its details and unit. Choose a setup in which your team can explain each identity decision.

Move from research to a working shop

See how DROPS fits your shop.

Explore the platform and try the demo. Bring your catalogue, ordering and team requirements to a setup conversation.

Explore DROPS See the shop demo Discuss your setup