Configuring an Integration Mapping
The integration mapping editor is a full-page interface that guides you through connecting Luminous data fields to the fields your destination system (TrackStar, Shopify, ShipStation, etc.) expects.
Opening the editor
- Go to Manage → Mappings in the left-hand menu.
- Click Create Mapping to start a new one, or click the ⋮ menu on an existing row and choose Edit.
Creating a new mapping
When you land on the New mapping page, fill in:
| Field | What to enter |
|---|---|
| Name | A short label you'll recognise in the channel list (e.g. Shopify order push) |
| What are you sending? | Choose the data type: Push orders / Push products / Push inbound shipment |
| Where to? | The destination integration account (TrackStar, ShipStation, Shopify store, …) |
| Example ID (optional) | An order / product / PO shipment ID — used to show real values beside every field. You can add or change this later. |
Click Create mapping to continue to the editor.
Using the guided builder (default)
The editor opens in guided mode by default. The left rail lists every section of the destination schema with a progress bar and a count of required fields still empty.
- Click a section in the rail to focus on it.
- For each destination field, click Choose source to pick a Luminous field, or type a fixed value.
- The Example column shows the real value from the source record you loaded, so you can confirm the right data is being sent before saving.
- Required fields are flagged; the guidance line tells you exactly what is left to do in the current section.
- When a field's source or type is too complex for the guided view, an Advanced link takes you to the grid focused on that row.
Switching to the Advanced grid
Click Advanced in the mode toggle at the top of the editor. Your choice is remembered per browser — power users only need to set it once.
Both views edit the same underlying mapping; switching back and forth is safe at any time.
Adding or changing a conversion
A conversion transforms the source value before it reaches the destination (uppercase, value lookup table, find/replace, date formatting, etc.).
- Once a source field is chosen for a row, a Convert chip appears beside it.
- Click the chip to pick a conversion type. The editor probes your example record through the real transformation engine and shows what each option would actually produce.
- For conversions that have settings (such as a value mapping table), clicking the chip on a row that already has a conversion opens the settings form directly.
- To remove a conversion, open the chip panel and click Remove.
Previewing output
If an example record is loaded, the editor runs a preview automatically and shows resolved values beside each row. Click Preview in the toolbar to open the full before/after view, or Refresh after editing rows to update it.
Saving
Click Save in the header. Rows missing a destination field will be flagged before the save is sent. The editor also warns before you leave with unsaved changes.
Applying the mapping to a channel
After saving, go to Manage → Channels, open the relevant fulfillment channel, click Edit, and set Order destination → Advanced Mapping to this mapping. All outbound pushes from that channel will then use it.
Common questions
Can one mapping be used by multiple channels? Yes — once saved, a mapping can be assigned to any number of channels.
What if a required field stays empty? The save will be blocked and the missing fields highlighted. The destination system would also reject the push if a required field arrived empty.
My conversion is a value lookup table — how do I edit individual entries? Click the conversion chip on the row. Because that conversion has settings, the settings form opens directly so you can add, change, or remove lookup pairs without losing your place.
Can I restore a previous version of a mapping? Yes — click History in the editor toolbar to open the version panel. Choose a version and click Load into editor; it becomes an unsaved draft you can review before saving.