Order Routing to Different Warehouses

Order Routing to Different Warehouses

Software Plan: Growth & Enterprise
Account Type: Seller Account
Inventory Type: Serialized & Non-Serialized

Overview

Order Routing determines which warehouse location will process an incoming marketplace order.
If you operate from multiple warehouse locations, routing ensures orders are assigned automatically based on your selected configuration.
If you operate from a single location, routing configuration is not required.
Settings → Other Settings → Order Routing Settings







When you click on Order Routing Settings, the page shows two tabs:
  • Routing
  • History
All configuration is done under the Routing tab.

How Order Routing Works

When an order is received:
  1. Routing must be enabled.
  2. The system considers only those locations mapped to the marketplace.
  3. The selected Routing Type logic is applied.
  4. Inventory availability is considered.
  5. Splitting logic applies (if enabled from backend).
  6. Warehouse Capacity is checked (if configured).
  7. Warehouse Capacity is evaluated after routing eligibility and before final assignment.
  8. The order (or SKU line) is assigned to a location.
  9. If a location does not meet routing conditions (marketplace, inventory, or capacity), it is skipped.
  10. If no eligible location is found, the order is assigned to the Default Location.

Quick Setup Flow

  1. Select a Routing Type
  2. Map Marketplaces to each location
  3. Configure routing logic (priority or pincode, based on type)
  4. Select a Default Location
  5. (Optional) Define Warehouse Capacity
  6. Enable Routing 

Enable Routing

Enable the Enable Routing toggle to activate routing logic.
If disabled:
  • Orders follow default system allocation.

Enable Splitting

Enable Splitting toggle if splitting is enabled from backend.

If Splitting is enabled:
  • Multi-SKU orders may be fulfilled from multiple locations.
  • Different SKUs in the same order can be routed to different warehouses.
If Splitting is disabled:
  • The entire order must be fulfilled from a single location.
Note:
  • Splitting is not supported for MCF (Multi-Channel Fulfillment) locations.

Routing Type

Only one Routing Type can be selected at a time.

If you attempt to change the routing type, the system shows a confirmation message stating that existing configuration will be deleted and routing for pending orders will be retried with the new configuration.

You must confirm before proceeding.

Example (Basic Routing)

If you have:

  • Warehouse A (Priority 1, Capacity Available)
  • Warehouse B (Priority 2)

The system will first check Warehouse A.
If it meets routing conditions, the order is assigned there. 

If not, Warehouse B is considered.

Example (Capacity Impact)

If you have:

  • Warehouse A (Priority 1, Inventory Available, Capacity Full)
  • Warehouse B (Priority 2, Inventory Available)

Then:

  • Warehouse A is skipped as capacity is reached
  • The system evaluates Warehouse B
  • The order is assigned to Warehouse B

Which Routing Type Should You Use

  • Proximity-Based Routing → Use when you want orders assigned to the nearest warehouse.
  • Location-Based Routing → Use when you want fixed priority between warehouses.
  • Pincode (Forced) → Use when specific pincodes must always be served from a specific warehouse.
  • Pincode (Optional) → Use when you want pincode-based routing with fallback flexibility.

1. Proximity Based Routing

Orders are routed to the location nearest to the buyer’s address.
Inventory availability is considered.
Only locations mapped to the marketplace are eligible.
Columns visible in this view:
  • Location
  • Marketplaces
  • Warehouse Capacity
  • Default Location
Use this when you want routing based on buyer distance.


2. Location Based Routing

Orders are routed based on priority defined for each location.
You must assign a unique priority number.
The system checks locations in priority order.
Inventory availability is considered.
Columns visible in this view:
  • Location
  • Marketplaces
  • Warehouse Capacity
  • Priority
  • Default Location
Use this when you want defined operational hierarchy between warehouses.


3. Map Location with Pincode (Forced)

Orders are routed strictly based on pincode mapping.
You must upload a CSV file containing pincodes for each marketplace.
If buyer’s pincode matches the uploaded list:
  • The order is routed to that location.
Inventory availability is not considered in this case.
Columns visible in this view:
  • Location
  • Marketplaces
  • Warehouse Capacity
  • Pincode (Upload / Download)
  • Default Location
Use this when certain pincodes must always be served from a specific warehouse.
Orders will still be routed to the mapped location even if inventory is not available.


4. Map Location with Pincode (Optional)

Orders are routed to the location where order pincode is mapped.
Inventory availability and pincode priority are also considered.
You can upload pincodes for each marketplace.
Columns visible in this view:
  • Location
  • Marketplaces
  • Warehouse Capacity
  • Priority
  • Pincode (Upload / Download)
  • Default Location
Use this when you want pincode-based routing along with priority flexibility.


Marketplace Mapping

Under the Marketplaces column:
  • Select applicable marketplaces for each location.
  • Only orders from selected marketplaces will be routed to that location.
If no marketplace is selected:
  • That location will not be considered for routing for that marketplace.
Primary location is always available for routing.


Default Location

Only one location can be selected as Default using the radio button.
If routing conditions are not satisfied:
  • The order is assigned to the Default Location.

Warehouse Capacity

Warehouse Capacity defines the maximum number of suborders that can be assigned to a location within a day.
It is used when a warehouse should not receive more orders than it can handle.
This is useful when a warehouse has limited processing capacity and should not receive more orders than it can handle.

When Capacity Can Be Configured

Warehouse Capacity can be configured only when:
  • Routing is enabled.
  • Minimum Shipment setting is OFF.
  • The location is eligible for routing.
For Primary Location:
  • Capacity can be defined directly.
For Child Locations:
  • Capacity can be configured only after at least one marketplace is selected. If no marketplace is selected, the field remains unavailable.

What is Counted

Capacity is calculated per suborder.
Suborder means:
  • One SKU line within an order.
Quantity does not increase suborder count.
Example:
  • 1 Order with 1 SKU (Qty 5) → counts as 1
  • 1 Order with 3 different SKUs → counts as 3

When Capacity is Reached

If the defined capacity for a location is reached, that location will not be considered for further routing, and other eligible locations will be evaluated.

History Tab

All routing configuration changes are recorded under the History tab for reference.


Important Points

  • Only one Routing Type can be active at a time.
  • Changing Routing Type removes existing configuration.
  • Only one Default Location can be selected.
  • Marketplace selection controls routing eligibility.
  • Splitting must be enabled from backend.
  • Warehouse Capacity applies per suborder.

FAQs

Q1. Why is a warehouse not receiving orders even though it has inventory?

  • Check if the marketplace is mapped to that location.
  • Ensure routing is enabled.
  • Check routing type conditions (priority, pincode, etc.).
  • Verify that warehouse capacity (if configured) is not reached.

Q2. What happens if no warehouse meets routing conditions?

  • The order is assigned to the Default Location.

Q3. What happens if two warehouses are eligible for routing?

  • The system applies the selected routing type (proximity, priority, or pincode) to decide.

Q4. Why is Warehouse Capacity not visible?

  • Minimum Shipment may be enabled.
  • For child locations, no marketplace may be selected.

Q5. Can one order be processed by multiple warehouses?

  • Yes, if splitting is enabled (via backend).
  • Different SKUs in the order can be routed to different locations.

Q6. Does Warehouse Capacity consider quantity or number of SKUs?

  • Capacity is calculated based on suborders (SKU lines), not quantity. 

Related Articles

    • Related Articles

    • Prefetch Settings In Easyecom

      Software Plan: Startup, Growth & Enterprise Account Type: Seller Account, Aggregator Account, 3PL Account Inventory Type: Non-Serialized & Serialized Overview Prefetch Settings allows fetching in advance the invoices and shipping labels for ...

    • B2B Order Processing (New)

      Software Plan : Growth & Enterprise Account Type : Seller Account Inventory Type : Serialized & Non-Serialized Feature description Easyecom announces a significant upgrade to its B2B order processing platform, prioritizing enhanced efficiency, ...

    • Creating STN order in Easyecom

      Software Plan: Growth & Enterprise Account Type: Seller Account Inventory Type: Serialized & Non Serialized Feature description A stock transfer note is created to authorise the movement of inventory from one location to another different location. ...

    • Order tagging settings (Order import based on pincodes)

      Order tagging settings: This settings helps you to customise order importing from marketplace to EasyEcom by filtering pincodes. You can enter a list of pincodes and only for those pincodes, orders will be imported to EasyEcom. NOTE: This setting is ...

    • B2C Order Processing – Individual Orders

      Software Plan : All Account Type : Seller Account & Aggregator 3PL Inventory Type : Serialised and Non-Serialized Description This article documents the end-to-end processing of individual B2C orders in Easyecom, starting from order availability in ...