Shipping Management
June 26, 2026
Summary
How shipping policies, source shipping methods and channel shipping mapping fit together - the three layers that connect what a customer picks at checkout to the carrier service your supplier actually ships with.
What this does
Shipping policies
Create named buckets (Standard, Priority, Freight) that bind source shipping methods to channel options.
Source shipping methods
Define carrier codes and service levels your suppliers use to physically ship orders out.
Channel shipping mapping
Map what customers select at checkout (e.g. "4–7 business days") to an internal shipping policy.
Package sizing
Enable Best Fit Package to let Flxpoint auto-select the optimal box based on line item dimensions.
Rate shopping
Filter eligible carriers and methods for automated rate comparison (requires ShipEngine connection).
The three layers of shipping configuration
| Layer | What it is | Set up when |
|---|---|---|
| Shipping policy | A named container that groups source shipping methods and channel shipping mappings together (e.g. "Standard," "Priority," "Freight") | Before adding source shipping methods or channel shipping mappings - policies must exist first |
| Source shipping method | The carrier + service level your supplier uses (e.g. UPS Ground, UPSH for handguns). Assigned to a policy. | After creating a policy; once per carrier/service combo per source |
| Channel shipping mapping | Translates what a customer selects at checkout into a policy (e.g. "4–7 business days" → Standard) | After creating a policy; required for every shipping option exposed on a channel |
Important: read before configuring
If a customer's checkout shipping selection (Channel Shipping Text) doesn't match any channel shipping mapping, Flxpoint holds the order automatically. Every shipping option on your channel must be mapped to a policy - including edge-case values like
N/A and n/a, which are treated as separate entries.When you assign a shipping policy to an unmapped channel shipping mapping, orders already on hold for that value are not released automatically - each held order must be released manually. If you have multiple variants (e.g.
N/A and NA), each must be assigned separately.The rate shopping filter on a source shipping method is only visible after you have connected ShipEngine and enabled Rate Shopping for that source. The field does not appear until both conditions are met.
When Best Fit Package is enabled, Flxpoint calculates package size from line item dimensions. For orders that exceed your largest defined box, it defaults to the largest box available - verify that your box dimensions are complete before enabling this for high-volume sources.
If rate shopping returns no rates, check the address fields. Flxpoint passes country, state, city and postal code to ShipEngine exactly as stored, without trimming or correcting them, so a wrong country code or a trailing space in the state can produce no rates.
An order goes on hold when its shipping method cannot be traced to a supplier method. The chain: the shipping text on the incoming order maps to a Flxpoint shipping policy (Channel > Shipping Mappings, column To Shipping Policy), and each source needs a shipping method linked to that same policy (Source > Shipping Methods, column Flxpoint Shipping Policy). Fix the missing link, then on the order click Release Hold and Generate Fulfillment Requests. If the source has no method for the policy, the fulfillment request has no source shipping method and sends that need one fail with a 'Source shipping method is missing' type error.
Source shipping method: field reference
| Field | Required | Description |
|---|---|---|
| Name | Required | Label for this shipping method (e.g. "UPS Ground," "UPSH: Handguns"). Used for internal identification only. |
| Flxpoint Shipping Policy | Required | The shipping policy this method is assigned to (e.g. Standard, Priority, Freight). Every source shipping method must belong to a policy. |
| Shipping Code | Required | The exact code your source/supplier expects to identify how to ship the order (e.g. UPSR, UPSF). Must match what your source's system accepts. |
| Best Fit Package | Required | Toggle on to let Flxpoint auto-select the optimal package size using order line item dimensions. Requires dimensions to be set on source inventory. |
| Default Carrier Code | Optional | The text code your source uses to identify the carrier (e.g. UPS, FEDEX). Found in advanced settings. |
| Custom Carrier Name | Optional | A free-text field to describe the carrier. Useful when working with custom or unlisted carriers. Found in advanced settings. |
| Custom Method Name | Optional | A free-text field to describe the specific service level or method (e.g. "2-Day Air"). Found in advanced settings. |
Common issues
Orders are stuck on hold with "unmapped channel shipping method"
The channel's checkout shipping text doesn't match any saved mapping. Go to
Settings → Orders → Shipping Management, find the flagged value under Channel Shipping Mappings, and assign it to the correct shipping policy. This does not release the held orders automatically - after assigning the policy, manually release each order still on hold for that value. If you see multiple variations (e.g. both N/A and NA), assign each one separately.
Rate shopping settings don't appear on a source shipping method
Rate shopping settings only appear after ShipEngine is connected to the account and Rate Shopping is enabled for that specific source. Check both conditions before looking for this field - it will not show until both are active.
Source has different shipping requirements per product type (e.g. firearms vs accessories)
Create a separate source shipping method for each product type with its own Shipping Code. For example:
UPSH for handguns, UPSF for long guns, UPSR for accessories under $500. All of these can sit under the same shipping policy (e.g. "Standard") - you do not need a new policy per product type.
Best Fit Package is selecting an incorrect or oversized box
Best Fit Package requires accurate dimensions on each source inventory item. If dimensions are missing or incorrect, Flxpoint defaults to the largest defined box. Verify that length, width, and height are populated on the relevant source inventory records, then re-test with a sample order.
FAQs
Do I need a separate shipping policy for every source?
No. Policies are shared across sources. A single "Standard" policy can hold shipping methods from multiple sources - each source's methods are just assigned to whichever policy fits their service level. You only need additional policies when you need to separate service tiers (e.g. Standard vs Priority vs Freight).
Can one channel shipping text map to more than one policy?
No. Each channel shipping text can only map to one policy. However, a single policy can have multiple channel shipping texts pointing to it. For example, both "Standard Shipping" and "4–7 business days" can map to the same "Standard" policy.
What happens if I delete a shipping policy that has active orders?
Deleting a policy removes it from all future routing decisions immediately. Active orders already in progress are not affected mid-fulfillment, but any new orders arriving with a channel shipping mapping that pointed to the deleted policy will be flagged as unmapped and held. Reassign the channel shipping mappings to a new policy before deleting.
Why is my source shipping method's carrier code not being recognized?
The Default Carrier Code and Shipping Code must exactly match the values your source's system expects - including capitalization and any hyphens. Obtain the accepted codes directly from your source's API documentation or support team, then update the method in
Settings → Orders → Shipping Management.