↑↓ selectEnter openEsc close

    1. Elbuz

    How to merge two product cards into one

    15 min readUpdated

    Elbuz merges two cards of the same product into one: orders, documents, stock movements and price list matches move to the card that stays, and the other is deleted.

    When you need this:

    • Dozens of confirmed pairs — “Apply” merges them all at once.
    • One card already has sales — Elbuz keeps it: orders outweigh any content.
    • You want to keep the other card — click “Keep the other one” in the comparison.
    • Your site runs on Elbuz Tunnel — the deleted card leaves the site during the merge or with the next export.

    Where to start: merge one pair with “Merge” and see what moves over.

    What merging can do

    How to merge one pair or all confirmed pairs

    A merge cannot be undone. The second card of the pair is physically deleted — Elbuz has no trash for products, so there is nowhere to restore it from.

    Everything that did not move over under the “only what the winner lacks” rule is lost with it: promotions and discounts, related products, videos, files, options, category links, questions and answers, and — if the winner already had a gallery — all photos of the second card along with their files.

    Whether and when the product disappears from a connected site depends on your export settings (see below).

    You can merge one pair with “Merge” in a row: a comparison of the two cards opens, showing which stays, which goes and what moves over. Or merge a batch with “Apply” above the table: it merges every “Confirmed” pair, 20 pairs per step. The button appears only once there is a confirmed pair.

    What “Apply” does with each confirmed pair. Note the two side branches: a pair whose card no longer exists goes to “Merged” without a merge, and a pair that failed to merge goes to “Rejected”
    NoYesYesNoYesNo“Apply” and confirmation in thedialogUp to 20 pairswith the “Confirmed” status aretakenAre both cards of the pairstill in the catalog?The pair goes to “Merged” without amergeDid the merge succeed?The second card is deleted.This pair and other pairs with thiscard go to “Merged”The pair goes to “Rejected”Are there “Confirmed” pairs leftand did the batch takeat least one pair off the queue?“Pairs merged: N”and separately “Failed to merge: N”
    • Action or result
    • Decision: the path depends on the answer

    Which card stays

    The card with the higher content score stays. Elbuz calculates this number itself:

    • gallery photos — 4 points each, up to 40;
    • attributes — 1 point each, up to 30;
    • description — 1 point per 500 characters, up to 20;
    • main photo filled in — 5;
    • has order lines — 100;
    • has document lines — 100;
    • linked to external stores — 50;
    • matched price list lines — 10.
    Дані таблицею
    ПоказникHas order linesHas document linesLinked to external storesGallery photosAttributesDescriptionMatched price list linesMain photo filled in
    Maximum points10010050403020105
    Maximum points for each part of the content score. Orders alone outweigh all content combined — photos, attributes, description and main photo give at most 95.

    Orders and documents outweigh any content: the algorithm won't delete a card with sales, even if its description is poorer. On a tie, the card with the lower stays — the one created earlier, which has usually already spread to exports and links.

    The comparison dialog shows both numbers side by side in the “content” row. Elbuz suggests the winner. If you disagree, click “Keep the other one”: the dialog reopens with the choice reversed, the content score and the “Moves to the card that stays” list are recalculated, and after “Merge cards” the card you chose stays.

    The
    1Stays
    2Will be deleted
    3Content row
    4What moves to the card that stays
    5Keep the other one
    1. Stays — the card that remains in the catalog after the merge.
    2. Will be deleted — the card that is removed; its data moves to the first one.
    3. Content — two numbers showing how filled in each card is.
    4. Moves to the card that stays — the list of what is carried over; orders, documents, stock movements and price list links move in full.
    5. Keep the other one — swaps the roles of the two cards.

    “Apply” doesn't ask which card to keep: in each batch pair, the card with the higher content score stays. You can pick the other card only one pair at a time. So if you need to keep the second card, first take the pair out of “Confirmed” with “Clear decision”, then merge it with “Merge” and “Keep the other one”.

    What moves to the card that stays

    Content moves over under the “only what is missing” rule. Each item has its own condition, and it matters:

    • main photo — only if the winner's is empty;
    • photo gallery — only if the winner has no gallery photos at all. If it has even one, the second card's photos don't move over and are deleted with it;
    • attributes — only those the winner lacks;
    • description and short description — only for languages where the winner's description is empty. If the winner's card has no description in some language at all, the second card's description moves over for that language;
    • barcodes, SKU and model — only into the winner's empty fields.

    The dialog lists in words what will move over: “Moves to the card that stays: photos: 4, attributes: 12, empty fields: ean”. If there is nothing to move, it says so: “nothing to move — the card that stays already has all of it”.

    Links, however, move over in full: orders, documents, stock movements, matches with supplier price lists, price history, price monitoring, store and export assortments, reviews, customer carts. Elbuz builds the list of these links from the database structure rather than keeping it in code.

    There are two exceptions. First: if both cards have a record with the same key, the winner's record stays. This is most visible in price history — when both cards have a price for the same day, the second card's data point doesn't move over.

    Second — sets. If the second card was a component of another set, the winner replaces it in that set, and that's fine. But if the second card was a set itself, its composition doesn't move to the winner and is deleted with the card: you'll have to build the set again.

    What a merge doesn't move over

    The second card's price, quantity, status, category and manufacturer don't move over at all: the winner keeps its own. Promotions and discounts, related products, videos, files, product options, category and layout links don't move over either. If the second card had option products (variants linked to it), they are deleted along with it.

    When the merge reaches your site and exports

    A merge doesn't start an export by itself. What your site or marketplace sees depends on how it receives data.

    A site connected through Elbuz Tunnel. Elbuz records the deletion of the second card in the deletion log. From there, two branches:

    • if the tunnel export template has “Products” checked in the “Select data to delete on the site” section and “Delete data immediately on the site” turned on, the template is active, and the tunnel connection settings are filled in, the card is deleted from the site database during the merge itself, without an export;
    • if “Delete data immediately on the site” is off, the card stays on the site until the next tunnel export of a template with “Products” checked in that same section. At that step the export log shows “Deleting items from the site database that were deleted earlier”;
    • if “Products” is not checked for deletion in any template, the deletion log won't pass this card to the site, and it won't disappear from the site database this way.
    How a card deletion reaches a tunnel-connected site. The “Yes” branch of the first question deletes during the merge itself, the rest with the template's next export; if “Products” is not checked for deletion anywhere, the card stays on the site
    YesYesYesNoNoNoYesNoMerge: the second card is deletedEntry in the deletion logIs there an active tunnel templatewith “Products”and “Delete data immediately on thesite” checked?Are the tunnelconnection settings filled in?Did the tunnel respondwithout an error?The card is deleted from the sitedatabaseduring the mergeThe error text goes to the operationlogIs there a tunnel templatewith “Products” checked fordeletion?Deleted with this template's nextexport,at the step “Deleting items from thesitedatabase that were deleted earlier”The card stays on the site
    • Action or result
    • Decision: the path depends on the answer

    If the tunnel returned an error on deletion, the merge in Elbuz is already done, and the error text goes to the operation log. This section's settings are described in the article on exporting through the tunnel.

    File exports and feeds. The second card is no longer in the catalog, so it won't be in the next file. Until the next export, the link serves the previous file, which still contains the card. Whatever moved to the winning card (photos, description, attributes, barcodes) also reaches the file only with the next export.

    Templates with “Only export new data” checked take only products without the “Exported” flag. A merge clears this flag on the winning card and on its photos and attributes, so the moved content reaches such a template with the next export.

    What to do if you merged the wrong pair

    How to find merged pairs. Every merged pair stays in the “Merged” tile for good: neither a new run nor the “Clear” button removes it.

    The row shows the ID and names of both cards as they were at the time of the search; the deleted card is marked “card removed during the merge” and has no open button. The tile doesn't split merges by run — it holds all of them, however many there were.

    The operation log shows who deleted the card and when: each merge adds a “Products deleted” row with the number of deleted cards, under the name of the person who merged (option products of the second card are counted too). Log rows are kept for 14 days.

    What a database backup gives you. There is no selective restore: restoring from a backup replaces the whole database with its state at the time of the backup. The deleted card comes back, but everything done in Elbuz after the backup is lost, including new orders and other merges.

    Gallery photo files that didn't move to the winner were deleted from storage during the merge (unless another product uses the file), and a backup doesn't restore them: the card comes back with links to missing photos. An Elbuz restore also doesn't bring back a card deleted from the site via the tunnel — the site has its own database.

    What you'll have to do manually without a restore. Elbuz can't split a merged pair. The second card's orders, documents, stock movements, price list matches and price history stay on the winner. To have the card separately, create it again: price, quantity, category, manufacturer, description and photos from your records outside Elbuz, and redo the price list matches.

    How to catch a third card of the same product

    When a product was entered three times, there are two pairs: first with second and second with third. After the first pair is merged, the second card is gone, and the “second with third” pair closes as “Merged” by itself, though the third card is still separate and duplicates the first. So the “Merged” tile may contain pairs that were never merged.

    What to do: after “Apply”, click “Find duplicates” again. The new pair appears in the list. In “With AI check” mode, a new run doesn't erase the existing verdicts of other pairs: only new pairs are checked.

    If a pair fails to merge, Elbuz marks it “Not a duplicate” and reports: “Failed to merge: N — those pairs were marked as “not a duplicate”.” Look for them in the “Rejected” tile.

    Scenarios

    Site on Elbuz Tunnel: the merged card must disappear from the site along with the merge

    What to do. In the tunnel export template, in the “Select data to delete on the site” section, check “Products” and turn on “Delete data immediately on the site”. The template must be active, and the tunnel connection settings must be filled in.

    The result. During the merge, the second card is also deleted from the site database, without a separate export.

    What won't happen. Without “Delete data immediately on the site”, the card stays on the site until this template's next export (when the merge reaches your site). If the tunnel returned an error, the merge in Elbuz is already done, and the error goes to the operation log. Restoring an Elbuz backup won't return the card to the site — it has its own database.

    You need to keep the very card Elbuz suggests deleting

    What to do. If the pair is already “Confirmed”, hover over the row and click “Clear decision” so “Apply” doesn't merge it first by content score. Then click “Merge” in the row and “Keep the other one” in the dialog, check the “Stays” and “Will be deleted” columns, and only then click “Merge cards”.

    The result. The card you chose stays. Orders, documents, stock movements and price list matches move to it, and of the content — only what it lacks.

    What won't happen. “Apply” doesn't offer this choice: in a batch, the card with the higher content score always stays. Of the deleted card's fields, only the main photo, SKU, model, and UPC move to the chosen card — and only those that are empty there. Its price, manufacturer and category links don't move over.

    What to do when a merge fails

    Troubleshooting common problems
    What you seeWhyWhat to do
    “This pair has already been merged.” The pair was merged in another tab or by another employee Refresh the list by clicking any tile
    “Failed to merge: N — those pairs were marked as “not a duplicate”.” The data transfer failed, and the pair was taken out of the queue so the loop doesn't repeat endlessly Find them in the “Rejected” tile and try merging them one by one with “Merge” (merging)
    “card removed during the merge” The pair shows a card that no longer exists Nothing: this is a record of a completed merge

    FAQ

    Can I undo a merge?

    No. The second card of the pair is physically deleted, and there is no trash for products. So review the pairs first, check the “Confirmed” tile, and only then click “Apply” (if you merged the wrong pair).

    What happens to the orders of the card being deleted?

    Orders, documents, stock movements, price list matches and price history move to the card that stays before the second card is deleted. Also, having orders and documents adds 100 content points each to a card — which is exactly why the algorithm keeps it.

    Why is there a pair in “Merged” that I didn't merge?

    The product was entered three times: after the first pair was merged, the second card was gone, and the “second with third” pair closed by itself. Click “Find duplicates” again — the third card will be found (triples).

    Do the price and stock of the deleted card move over?

    No. The card that stays keeps its own price, quantity, status, category and manufacturer; they don't move over from the second card (what a merge doesn't move over).

    A set disappeared after the merge. Why?

    If the deleted card was a set itself, its composition doesn't move to the card that stays and is deleted with it. You'll have to build the set again (what moves over).

    Where to find it and who has access

    Where to merge
    the “Catalog duplicates” window: “Merge” in a row or “Apply” above the table
    Access right
    the “Catalog duplicates” window; there is no separate right for merging
    Prepare
    pairs with the “Confirmed” status — how to review them

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free