What it writes
This act saves the reviewed pairs of an old and a new variant, each tied to a sales channel, for their named sales channels. The CSV uses old_sku,new_sku,channel and holds up to 1,000 pairs. Historical sales and selling dates stay unchanged. Assign selling periods separately.
Who may press it
You need write access and access to Analogs. A viewer can preview the file but cannot apply it. Your product and channel restrictions still apply. Scheduled workflows cannot perform this act.
What you review
In Products → Analogs, choose Import analog CSV, drop the file in or browse for it, and press Preview pairs. A Download template link gives you the columns. The review names missing or ambiguous codes and channels, duplicate rows, excluded products and conflicting mappings. Correct every blocked row before you press Approve and apply. A source-archived donor remains eligible unless explicitly excluded in Tightly.
Ask can prepare the same review. It must show the proposed change and wait for your confirmation on a later turn before applying the exact reviewed file. If the products or mappings change after review, approval is refused and you must preview again.
What you see after approval
The result reports saved mappings separately from forecast refresh. A failed refresh leaves the mappings saved. Export the report to retain resolved IDs and row results. If the result is unclear, preview the same file again to check which mappings are already saved before retrying.
How to take it back
Open Products → Analogs → In use, review the pair and use Break this link. Ask does not offer a bulk undo. Removing an analog does not delete historical sales; review the new product's forecast after changing its source.