Flxpoint Knowledge Base

What this does

Routing groups

Named containers that define which sources are eligible and what rules apply for a category of orders.

Routing priorities

Ordered rules - Lowest Cost, Source Priority, Single FR, Closest - evaluated top-to-bottom to pick the best source.

Source priority tie-breaking

When multiple sources score equally, a ranked list determines which one wins.

Cannot-route handling

Per-group configuration for what happens when no source qualifies - cancel, hold, or manual review.

Split order review

Optionally pause multi-source FRs in Unprocessed state before they transmit, so you can review split costs.

How routing decisions are made

Order imports

→

Routing group selected

→

Eligible sources identified

→

Priorities evaluated top→bottom

→

Best source selected → FR created

Priorities narrow the field step by step. If Priority 1 leaves multiple eligible sources, Priority 2 narrows further - and so on - until one source wins or no source qualifies. A source that is disabled in the routing group is never considered, regardless of priority rules.

Routing groups - when to use more than one

Setup	Use when	Example
Single default group	All orders should follow the same routing logic - one country, one fulfillment model	"Main Fulfillment" group with all US sources and Lowest Cost priority
Multiple groups with override	Different order types or regions need different source pools or priority rules	"International" group with only globally-shipping sources; "East Coast" group disabling west-coast warehouses

Start simple. A single well-configured default routing group handles the vast majority of accounts. Add a second group only when a clear business rule requires it - not as a precaution.

Important - read before configuring

A default routing group is required

There must always be a default routing group. If no workflow rule assigns an order to a specific group, the default is used. Flxpoint does not allow you to delete the only remaining routing group.

Required priorities hold orders when unmet - Preferred ones don't

Setting a priority to Required means Flxpoint puts the order on hold and sends a notification if that condition can't be satisfied. Preferred means it tries but continues to the next rule if no match. Misconfiguring Required vs Preferred is the most common cause of unexpected order holds.

Editing a routing group affects all future orders immediately

Changes to a routing group's priorities or eligible sources apply to every new order routed through that group from the moment you save. Use the Preview tool on a test order to validate changes before saving to a live group.

Closest only works for US-based source addresses

The Closest priority calculates distance from the source's configured address to the customer's zip code. If no address is set on a source, that source is excluded from Closest evaluation. This priority is US-only and does not apply to international sources or customers.

Routing priorities - full reference

Priority	What it does	Preferred vs Required	Best use case
Single Fulfillment Request	Finds sources that can fulfill the entire order in one shipment, avoiding splits.	Preferred continues if no single source qualifies. Required holds the order.	When split shipments significantly increase costs or create customer experience problems.
Lowest Cost	Calculates total cost (item + dropship fee + estimated shipping) and selects the cheapest option. A margin can be set so sources within X of the lowest cost all remain eligible for the next rule.	No hold behavior - always selects a winner or passes to next rule.	High-volume or low-margin catalogs. Set a margin when you want geographic or vendor preferences to break ties within an acceptable cost range.
Source Priority	Routes to the highest-ranked eligible source from your configured source priority list.	No hold behavior - moves to next rule if top source can't fulfill.	Maintaining preferred vendor relationships or guaranteeing a specific source handles a product category first.
Fewest Number of Fulfillment Requests	Minimize the number of sources selected to fulfill the entire order.	No hold behavior.	One box, one tracking number.
Has Shipping Policy Mapped	Filters to sources that have a shipping method mapped to the order's shipping policy (e.g. only sources that support "Priority" shipping).	Preferred falls back to other sources. Required holds the order if no source has the mapping.	When carrier or service-level compliance is non-negotiable (e.g. regulated products requiring specific carrier codes).
Closest	Selects the source geographically nearest the customer. A margin (miles or %) makes sources within that range all equally eligible, passing to the next rule for final selection.	No hold behavior.	Reducing delivery time when you have warehouses in multiple US regions. Combine with Lowest Cost as the next rule to balance proximity and cost.
Preferred Warehouse	Always tries to route to a designated internal warehouse first. If that warehouse can't fulfill, routing continues using the priorities below this one.	No hold behavior - falls through to remaining priorities automatically.	Businesses with owned inventory that should always be depleted before dropship suppliers are used.

Common issues

Order is on hold - "order cannot be routed"

▾

Check these in order: (1) Is the SKU linked to a Master SKU? Unlinked SKUs are invisible to routing. (2) Does any source in the routing group have that SKU in stock? (3) Is the relevant source enabled in the routing group - check the source list inside Settings → Orders → Routing → [group]. (4) Is a Required priority creating an unsatisfiable condition - e.g. Single Fulfillment Request Required but items only exist across two sources? Change to Preferred or add more sources.

Order is routing to a more expensive source instead of the cheapest one

▾

This usually means a higher-ranked priority is overriding Lowest Cost. Check whether Single Fulfillment Request or Source Priority sits above Lowest Cost in the list - those rules narrow eligibility before cost is evaluated. Also verify that estimated shipping costs and dropship fees are configured on your sources; if they're missing, all sources look equally priced and Source Priority wins by default.

Routing group changes are affecting orders I didn't expect

▾

Routing group edits apply to all orders routed after the save - including orders already in your queue that haven't generated a fulfillment request yet. To test changes safely: create a second routing group with your new config, use the Preview tool on a few test orders to validate, then swap it to default once confirmed.

Closest is not selecting the geographically nearest source

▾

Verify that each source has a Source Address configured (Source → Settings → Address). Sources without an address are excluded from Closest evaluation entirely. Also confirm your margin value - if the margin is wider than the actual distance between sources, all sources qualify and the rule passes to the next one without differentiating by proximity.

FAQs

Can one order be routed to multiple sources (split shipments)?

Yes - if no single source can fulfill all items, Flxpoint will split the order into multiple fulfillment requests unless Single Fulfillment Request is set to Required. You can also configure the Routing Completed Workflow inside the group to pause split FRs in an Unprocessed state for review before they transmit.

How do I assign a specific routing group to certain orders instead of the default?

Use a workflow rule on order import to assign the routing group based on channel, tag, SKU, or other order attributes. Without a workflow override, all orders use the default routing group. Navigate to Settings → Orders → Routing to set up overrides.

Does disabling a source in the routing group affect other routing groups?

No. The enabled/disabled toggle in a routing group is local to that group. Disabling a source in Group A does not affect whether it's eligible in Group B. This also does not deactivate the source itself - it simply excludes it from that group's consideration.

What does "Preferred Warehouse" do differently from "Source Priority"?

Preferred Warehouse is specifically designed for owned inventory - it always tries that one internal warehouse first and then falls through to all remaining priorities if unavailable. Source Priority evaluates a ranked list of any sources (internal or external) in sequence and stops as soon as the highest-ranked eligible one is found.