Written by DROPS.ST.
Rehearse a menu migration with a small, representative product sample before moving the full catalogue. Map the fields, compare the resulting records and test how customers see and order those products. Resolve exceptions before choosing a cutover time.
DROPS gives operators a shop where products, prices, images and stock belong together. Its assisted migration service covers moving products, prices and images; agree the exact source data and scope before the move. DROPS shop and migration features.
A rehearsal turns that scope into something you can check.
Agree what is moving
Start with a written list of included records. Distinguish the current menu from archived products, test listings and items you no longer sell.
Decide separately whether the project includes customer records, open orders, account balances or historical reports. A catalogue migration does not establish that these other records will move.
Name one person who can resolve product-data questions and another who approves the switch. In a small business, the same owner may handle both jobs.
Keep a readable copy of the source catalogue and its images. Record when it was captured and which shop it came from. Ask the migration team which source formats it can work with rather than assuming a particular export will import unchanged.
Build a field map before copying products
Use this checklist to explain how each source value should appear in the new shop. It is a planning aid, not a promised import format.
| Source information | Mapping decision | Rehearsal check |
|---|---|---|
| Product identifier or SKU | Preserve the reference or record its replacement | Each intended product has one matching record |
| Product name | Keep enough detail to distinguish similar items | Search and listing show the expected item |
| Short and full description | Assign each text to the appropriate field | Neither is missing or placed in the wrong field |
| Price and unit | Identify what the price purchases | Listing and order use the agreed amount and unit |
| Category | Map old labels to the new structure | Product appears in its intended category |
| Images | Match files to the correct product | Image opens and depicts the intended item |
| Stock or availability | Define the source and capture time | Result matches the agreed snapshot |
| Minimum and maximum quantity | Preserve the intended ordering limits | Test quantities behave as expected |
If wholesale packages or quantity prices are included, map them separately. Record the package name, quantity meaning and price tier. Do not assume a package has independent stock merely because it has a distinct label.
Choose a sample that reveals problems
A sample made entirely of simple products proves little. Include ordinary records alongside the cases most likely to need correction:
- Similar names with different SKUs or pack sizes.
- A product with several images.
- A product with a long description.
- An unavailable item.
- An item with quantity limits.
- A wholesale package or price tier, if included.
Label test copies clearly and keep them outside ordinary customer ordering until approved.
Compare the resulting records against the source one by one. Record missing fields, changed values and deliberate exclusions. A product count is useful, but matching counts can conceal one missing item and one duplicate.
For duplicates, check identifiers and business meaning. Two records with the same name may be different packs. Two differently named records may represent the same item.
Inspect images directly. A filename match does not confirm that the image is readable, belongs to the product or survived at useful quality.
Reconcile stock and the ordering experience
Stock needs a timing rule. If the source snapshot says eight units while staff continue selling, that snapshot will age during the migration.
Decide who records movements after the snapshot and how the final stock value will be established. Keep physical stock, reservations and available-to-order quantities distinct where your business uses them.
Do not assume that an external point-of-sale system will update the new shop automatically. Any connection requires its own agreed scope and demonstration.
Then inspect the test menu on a phone. Check product identity, image, unit, price and availability. Open the details and try the permitted quantity range.
Where connected Telegram ordering is included, repeat the customer-facing checks there. Complete a clearly marked test order only through the agreed test workflow. Compare its item, quantity and price with the product record.
Hypothetical example: five products, two exceptions
An owner rehearses a move using five products from a larger catalogue.
Four records have unique SKUs. The fifth shares a SKU with another listing but has a different pack size. One image also opens correctly while depicting the wrong item.
The owner pauses the full transfer. They assign a distinct reference to the separate pack and replace the mismatched image. The corrected sample is compared again before approval.
These are invented sample records, not observed customer results. The point is the decision: resolve ambiguity while the sample is small, instead of copying it throughout the catalogue.
Set the cutover and rollback decision
Before switching, record the acceptance conditions: required fields reconciled, duplicate decisions resolved, images checked, stock updated and test ordering passed.
Also agree when staff stop editing the old catalogue, who applies final changes and how enquiries or orders received during the transition will be handled.
If acceptance fails before customer activity begins in the new shop, keep the old shop as the operating source and correct the rehearsal. Set a new cutover time only after the failed checks pass.
After real orders arrive, returning to an earlier state becomes a reconciliation problem. Preserve the new orders and stock movements. Decide how each will be handled before reversing the switch. Restoring an old copy without accounting for later activity can discard business records.
Make the move worth the work
DROPS is a strong fit when the goal is a working shop with a coherent catalogue, rather than another collection of product copies. Connected Telegram shopping uses the same catalogue and order system as the website, giving the migration a clear destination: one shop record to maintain. DROPS shop features.
Use the menu software requirements checklist to define that destination before reviewing transfer details.
See DROPS and explore demo shops. Bring a small product sample and your field map to the migration discussion. Agree what moves, what needs correction and what must pass before customers start ordering.