Skip to content
On this page
Fix Updated Aug 14, 2026

Why parts were skipped

In short

The importer brings in everything the current store can use and lists what it could not. Usually a condition is not available in the chosen set, an operator is not supported, or a referenced product does not exist here.

Applies to

  • Imports that succeeded but came in incomplete

Doesn't apply to

  • Files rejected outright — those fail with a single error instead

A partial import is not a failure. The file was valid, and everything usable was brought across — the banner is telling you what was not, so you can add it back deliberately.

What the messages mean

MessageCauseFix
Unknown condition — skippedThe condition does not exist in this versionRebuild that condition by hand
Doesn’t support that operatorThe operator is not offered on that conditionPick the nearest supported operator
Isn’t in the X condition setValid condition, wrong set for this ruleSwitch the set first, then re-import
Condition was incompleteMissing values in the fileRe-add it in the editor
Method entry was incompleteA method arrived without a usable nameSelect the methods again
Renaming pair was incompleteOne half of a pair was missingRe-enter the pair
Display-order entry was incompleteAn ordered row was malformedRe-drag the order
Match type wasn’t recognizedUnreadable valueDefaulted to All conditions — check this
Condition set wasn’t recognizedUnreadable valueDefaulted to General Rules — check this
Rule had no nameMissing nameA default was used; rename it

Check the defaults before activating

The two that matter most are match type and condition set. Both fall back to a sensible default rather than failing, and a rule silently set to “All conditions” when it was meant to be “Any” behaves differently in a way nothing on screen flags.

Unknown payment methods

Separate from skips, you may see a notice that some payment methods are not in the known provider list. That is not an error — it usually means a gateway specific to the origin store. The names come across as typed, so check they exactly match a method at this store’s checkout before activating.

The most common cause

Importing a Product-Based rule into an editor set to General. Every product condition is then “not in the set” and gets skipped, leaving a rule that looks nearly right and applies far too broadly.

Set the condition set to match the source rule before importing.

Frequently asked

Should I import anyway when parts are skipped?

Usually yes, then add the missing pieces by hand — the alternative is rebuilding from scratch. Just check the rule before activating it, because a hide rule missing a condition is broader than intended.

The methods were skipped. Why?

Method entries that arrive incomplete are dropped. You need at least one method selected before the rule can be saved, so pick them again in the editor.

Can I stop this happening?

Mostly. Export and import between stores with the same products, collections and tags, and keep both on the same condition set.

See also: Import a rule · Condition sets · Condition reference — all 23 conditions

Still stuck? Email support — we usually reply within a few hours.