Review import conflicts

A conflict is a review ModuleDesk cannot attribute to one module on its own, usually because the customer bought a pack.

The preselection is a guess, not an answer

Each row arrives with the first candidate already selected, so the Import button is always clickable. That is convenient and dangerous: pressing it without reading assigns every ambiguous review to a first-listed module, and a review attributed to the wrong module distorts that module's rating.

"No match" is a different thing, and it does have a fix

A conflict is an order that matched SEVERAL products. Importing more orders will not resolve one — somebody has to choose.

"No match" is the separate bucket: no order was found for that reviewer at all. That usually means the orders CSV has not been imported, because without orders there is nothing linking a reviewer to a purchase. Import orders, run the review import again, and those resolve on their own.

Working through them

Sort by the customer, not by the review. One buyer with a pack produces several conflicts that all resolve the same way.

Also available in: Español