Why Shopify Flow Tags Do Not Stop Every Order From Importing Into ShipStation

Quick answer

Why the order appears anyway

Consider a store with normal parcel orders, pickup orders, and orders fulfilled by a separate 3PL. You create a Flow that tags 3PL orders External_Fulfillment. The tag appears in Shopify, but the order still shows up under Awaiting Shipment in ShipStation.

That is not proof that Flow failed. Flow’s Add order tags action adds a tag to an order; it does not rewrite the connected app’s import criteria. ShipStation can import Shopify tags into a custom field, but the mapping must be configured. An automation rule must then evaluate that field or other available order criteria and take the appropriate action.

There is also a timing risk: a Flow triggered by Order created runs after the order event, and an integration may read the order before the new tag is present. Never assume a tag added asynchronously will be available in the first import payload. Shopify’s own Flow documentation also warns that other apps can overwrite tags after Flow adds them.

Practical implementation

1. Define the routing rule before editing either system

Write a simple matrix of orders that should enter ShipStation and orders that should not. Use stable facts where possible: source, fulfillment location, shipping method, or a tag that exists before the integration imports the order. Decide what happens to mixed orders containing items for more than one fulfillment provider; an order-level exclusion can hide legitimate ShipStation work.

2. Make the Shopify tag reliable

In Shopify Flow, choose an appropriate order trigger and add a condition that identifies the target order. Use Add order tags with a specific tag, for example External_Fulfillment. For draft-order workflows, consider applying the tag before conversion: Shopify documents that tags on a draft order carry over when the draft becomes an order. Confirm the tag is present on the Shopify order before relying on it downstream.

Flow tags are case-sensitive in the action. Standardize exact spelling. For important routing decisions, do not use a tag that is also casually edited by staff or unrelated apps.

3. Map Shopify tags into ShipStation

In ShipStation, go to Settings → Selling Channels → Store Setup, choose your Shopify store’s Edit Store Details, then Edit Shopify Settings. Under Custom Field Mappings, map Order Tags to one of ShipStation’s three custom fields. These are the steps ShipStation documents in its March 12, 2026 help article. Confirm the chosen custom field is not already needed for another integration value.

Import a new controlled order and inspect the mapped custom field on the ShipStation order. If the tag is absent, do not create an exclusion rule yet: check timing, the selected field, and whether the tag was present when ShipStation first read the order.

4. Build a non-destructive ShipStation automation first

In ShipStation’s automation rules, create a condition that matches the mapped custom field or another supported order criterion. Initially set an internal note or a temporary tag instead of excluding the order. Verify the rule hits only the intended test orders, including a normal parcel order that must remain visible.

Once the criteria are proven, switch the action to Don’t Import the Order if permanent exclusion is genuinely what you want. ShipStation says this action removes the record from view and reporting and cannot be undone by deleting the rule or re-importing the store. A safer alternative for some workflows is to hold, tag, or route the order within ShipStation rather than remove it.

5. Check fulfillment-order behavior, not only order tags

ShipStation documented Shopify order-import pathway changes in April 2026, including a setting called Map multiple open fulfillment orders to requested fulfillments. If one Shopify order can split across locations or providers, inspect this mapping and test partial fulfillments. The right solution may be fulfillment-level routing rather than a blanket order-level exclusion.

Common misunderstanding

“I tagged the order in Flow, so ShipStation should never see it.” A Shopify tag is data, not an import policy. You need explicit ShipStation mapping and automation, and the timing must work.

“Don’t Import is just a filter I can reverse later.” It is not. ShipStation calls it a permanent action. Use reversible notes or tags while testing and reserve permanent exclusion for clearly defined cases.

How to test this

1. Create a normal shippable test order and a clearly excluded test order.
2. Verify the intended tag appears in Shopify on the excluded order.
3. Inspect the ShipStation custom-field mapping and confirm the tag actually arrives.
4. Run a temporary rule that adds a note; check it matches the excluded order and not the normal order.
5. Repeat with a mixed fulfillment order, draft-order conversion, and any alternate shipping method used in production.
6. Only then decide whether to activate a permanent Don’t Import action. Document the rule and monitor the next real import batch.

Sources and further reading

• Shopify Help Center — Add order tags action.
• Shopify Help Center — Order created trigger.
• ShipStation Help — Mapping Shopify order tags to custom fields (updated March 12, 2026).
• ShipStation Help — Advanced automation and permanent Don’t Import behavior.
• ShipStation Help — Shopify import pathway changes (updated April 10, 2026).