Why the mapping doesn't work

Luminous order tags are text labels (e.g. rush, gift, B2B). ShipStation's tagIds field is an array of numeric IDs that reference tags you've created inside your ShipStation account — the two formats are fundamentally incompatible.

When Luminous attempted to send tag names as tagIds, ShipStation rejected the payload with a data-conversion error, causing the entire fulfillment order push to fail.

As of the August 2026 fix: Luminous now detects this mapping automatically and skips it so it can no longer block a push. The channel configuration screen also shows an inline warning on any row where a tags / {{tags}} source is mapped to a tagIds destination on a ShipStation channel.

What you can do instead

Option A — Map tags to a text field (recommended for most teams)

ShipStation's advancedOptions.customField1 (or customField2 / customField3) accepts free-form text and is visible to warehouse staff.

Luminous sourceShipStation target
{{tags}}advancedOptions.customField1

This sends the tag list as a comma-separated string (e.g. rush, gift) into a ShipStation custom field where pickers can read it.

Option B — Use ShipStation's own tagging

If you need orders to be tagged in ShipStation (not just annotated), you must assign those tags inside ShipStation's automation rules based on order criteria. ShipStation tag IDs are account-specific numeric values that cannot be looked up from Luminous tag names.

Option C — Remove the mapping

If the tagIds mapping was added by mistake or is no longer needed, open Manage → Channels → [your ShipStation channel] and click Edit, scroll to Outgoing Custom Field Mapping, and delete the row.

How to update the mapping

  1. Go to Manage → Channels, open your ShipStation channel and click Edit.
  2. In the Order Destination section (Mapping Type: Basic Mapping), scroll to Outgoing Custom Field Mapping.
  3. Locate any row where the Source is tags or {{tags}} and the Target is tagIds. You will see a yellow warning message on that row.
  4. Change the Target to advancedOptions.customField1 (or another text field), or click the delete icon to remove the row.
  5. Save the channel.
  6. Re-push a test fulfillment order to confirm the push succeeds and the tag data appears where expected.