Why You May Not See an “Order Destination” in Channel Settings
Previously, some channels allowed you to directly set an Order Destination (such as a specific ShipStation store) within the channel settings.
Today, fulfillment routing is handled differently depending on the type of channel you are using. Not all channels have a fixed destination by design.
The Two Supported Channel Models in Luminous
Luminous supports two primary ways to configure how orders route to fulfillment destinations.
Option 1: End-to-End Channels (Simplest & Most Explicit)
Use this when:
Orders always come from one source and ship to one destination
You are working with EDI workflows that have fixed routing
Orders should not be split across multiple warehouses
Destination clarity is critical (e.g., during go-live)
How it works:
The channel itself has a defined fulfillment destination
Routing is explicit and predictable
Behavior matches traditional “source → destination” flows
Best for:
EDI customers with known trading partner requirements
Retailers with strict routing rules
Teams that want clear, easy-to-reason-about fulfillment behavior
Option 2: Sales Channels + Smart Fulfillment (More Flexible)
Use this when:
Orders may ship from multiple warehouses
Fulfillment needs to be determined dynamically
Routing depends on inventory availability or priority rules
How it works:
Sales Channels do not have a fixed destination
Fulfillment is resolved using:
Shipping Admin → Smart Fulfillment Settings
The Fulfillment Priority List
Destination systems (like ShipStation) are chosen at fulfillment time
Important notes:
All sales channels behave the same at a base level
Channel-specific requirements (e.g., ShipStation store, EDI values) are passed using custom fields
These custom fields are mapped consistently to the destination system
Best for:
Brands with multiple warehouses
Dynamic routing requirements
More complex fulfillment operations
Common Questions
Do I need both a Sales Channel and an End-to-End Channel?
No.
You should choose one model based on your workflow:
Use End-to-End Channels for fixed routing
Use Sales Channels for dynamic routing
Can Sales Channels still be used for webhook-created orders and outbound EDI?
Yes.
Sales Channels still support:
Sales Orders created via webhook
Outbound EDI documents
However, they do not provide destination clarity on their own. Routing is handled through Smart Fulfillment instead.
Where do I configure fulfillment routing for Sales Channels?
Go to:
Shipping Admin → Smart Fulfillment Settings
This is where the Fulfillment Priority List determines:
Which warehouse fulfills the order
Which connected fulfillment system is used
Recommendation
If your workflow requires:
Fixed EDI routing
A known fulfillment destination
Clear behavior during go-live
👉 End-to-End Channels are strongly recommended.
Sales Channels remain fully supported, but they are best suited for workflows where routing flexibility is more important than having a single, explicit destination.
Summary
Use Case | Recommended Setup |
Fixed EDI routing | End-to-End Channel |
Single destination fulfillment | End-to-End Channel |
Multiple warehouses | Sales Channel + Smart Fulfillment |
Dynamic routing | Sales Channel |
Clear go-live behavior | End-to-End Channel |
If you’re unsure which setup fits your business, reach out to your Luminous implementation team for guidance before go-live.