mcp-wms-wiki/wiki/concepts/crossdocking.md

title, type, sources, related, last_compiled

title	type	sources	related	last_compiled
Crossdocking	concept	areas/crossdocking/crossdocking_manual/index.md areas/crossdocking/crossdocking_manual/crossdocking_warehouse.md areas/crossdocking/crossdocking_manual/crossdocking_opportunity.md (404 — sourced from index.md description) areas/putaway/putaway_admin/index.md (Group by SO/Route strategy type) sources/archives/06_Gestion_cross_docking.md	concepts/reception.md concepts/putaway.md concepts/shipping.md concepts/container.md concepts/stock.md	2026-04-17

Crossdocking

Overview

Crossdocking is a warehouse flow optimization technique where received stock bypasses or minimizes time in bulk storage by being moved directly or nearly directly to the shipping area. Instead of the standard flow (receive → putaway → pick → ship), crossdocking shortens or eliminates the storage step.

EasyWMS supports two distinct crossdocking types in manual warehouses:

Type	Description	Stock assignment timing
Opportunity crossdocking	Stock goes directly to a shipping dock/stage/staging area after reception	Assigned immediately upon receipt
Crossdocking to warehouse	Stock goes to dedicated crossdocking locations near shipping area	Assigned when the shipping order is later released

Both types apply to containers, stacked containers, carts, and loose stock received at equipment. Automatic warehouses follow the same logic for location search but the TMS executes the physical movement.

Opportunity Crossdocking

Concept

When an operator is about to putaway received stock/containers, EasyWMS checks if any unreleased or in-preparation shipping order needs that stock. If yes, instead of going to bulk storage, the stock is directed straight to the dock, stage, or buffer associated with the shipping order.

The process triggers at two moments:

1. After receipt into equipment — operator is ready to putaway what was received
2. When preparing to putaway from a reception stage — stock received in a staging area is evaluated for direct transfer

Conditions and Eligibility

For opportunity crossdocking to apply to a shipping order line:

• The line orders only per container OR only per item (not mixed requirements)
• The line is not marked as critical or required to ship
• If the shipping order is sequenced (by line or by route with stops): crossdocking only applies if the container is for the line or stop currently being shipped or a prior one

For stock reserved in a reserve:

• If the stock has an active exclusive reserve → it is assigned to the order with that reserve (not freely routed)

For cutting stock items in non-consolidating conversions:

• Crossdocking is supported, but the decision process applies stock restrictions specific to cutting items (must handle total-quantity stretches)

Process Flow

1. Operator receives stock/container at equipment
2. Operator initiates putaway
3. EasyWMS evaluates: is there a shipping order that needs this stock?
4. If yes → task destination is set to the dock/stage/buffer of the shipping order → crossdocking task generated
5. If no → standard putaway process continues (channel filling strategies, then location strategies)
6. Operator follows RFT instructions to the assigned destination (same UX as standard putaway)

Output

• A putaway task with destination = dock/stage/buffer of the matched shipping order
• Stock is assigned to the shipping order at the time of crossdocking
• No storage location is used

Crossdocking to Warehouse

Concept (Warehouse)

If opportunity crossdocking is not possible (no shipping order needing immediate routing, or the stock quantity exceeds a single order's need), EasyWMS evaluates crossdocking to warehouse: the stock is placed in dedicated crossdocking locations near the shipping area. When the shipping order is eventually released, these crossdocking locations are consulted first during stock assignment — ensuring minimum travel distance for shipping.

The stock is not yet assigned to any shipping order during the crossdocking-to-warehouse placement. The link to the order happens at release time.

Conditions and Eligibility (Warehouse)

For crossdocking to warehouse to execute:

1. Item must allow crossdocking: item attribute "Allow crossdocking" must be enabled
2. Crossdocking locations must exist: locations must be configured with storage logic "Allows Crossdocking" AND must be reachable from the equipment by route, height, and work zone
3. Crossdocking putaway strategies must exist: at least one enabled putaway strategy flagged as "Is crossdocking"
4. Valid shipping orders must be candidates: a shipping order/line is a candidate for crossdocking if:
   • Order and lines are not closed, canceled, or in creation state
   • If the line orders a specific container: all items in that container have "Allow crossdocking" enabled
   • The line has pending quantity to assign (shipped + prepared + assigned < ordered quantity)
   • The strategy filters are satisfied: order status, priority, minimum days until release date or planned loading date (if configured)
5. Insufficient stock in existing crossdocking locations: if there is already sufficient stock in crossdocking locations to cover the pending need, no additional crossdocking is performed

Process Flow (Warehouse)

1. Operator is about to putaway received container/stock
2. EasyWMS first tries opportunity crossdocking (direct to dock) — if not possible:
3. EasyWMS evaluates crossdocking to warehouse: a. Identifies candidate shipping orders meeting criteria b. Checks if existing crossdocking locations already have sufficient stock c. If insufficient stock and candidates exist → runs crossdocking putaway strategy d. Strategy finds a valid crossdocking location
4. If a crossdocking location is found:
   • Task is generated with process type = Crossdocking, task type = Putaway
   • Task destination = crossdocking location
5. If no crossdocking location is found → search the rest of the warehouse using standard putaway strategies
6. If only part of the stock qualifies for crossdocking → remainder is located via standard putaway
7. Operator follows RFT instructions (same UX as standard putaway)

In automated warehouses: same logic applies; TMS executes the physical movement.

Crossdocking Locations

A crossdocking location is configured with storage logic property "Allows Crossdocking" = true. These locations are typically positioned near shipping docks and staging areas to minimize the travel distance from storage to loading.

When a shipping order is released, the stock assignment engine consults crossdocking locations preferentially before other storage locations. This prioritization ensures that pre-positioned crossdocking stock is consumed first.

Crossdocking Putaway Strategies

Crossdocking to warehouse requires at least one putaway strategy enabled with the "Is crossdocking" flag. These strategies define:

• Source station criteria (where the crossdocking flow originates)
• Destination rules (which crossdocking locations are valid)
• Filters on shipping order properties (status, priority, days until release/load date)
• Sorting preferences for selecting the optimal crossdocking location

The strategy can filter by:

• Shipping order priority
• Shipping order status
• Days until shipping order release
• Days until shipping order planned loading date

Stock Coverage Check

EasyWMS only routes stock to crossdocking locations if the pending demand is not yet covered. The check compares:

• Pending quantity for shipping order lines (ordered − shipped − prepared − assigned)
• Existing stock at crossdocking locations for the same item

If crossdocking locations already hold enough stock for all pending orders → no crossdocking task is generated → standard putaway proceeds.

Crossdocking Decision Tree

Putaway triggered (after reception)
           │
           ▼
  Opportunity crossdocking eligible?
  (SO needs stock, not critical, not sequenced out of order)
           │
    ┌──────┴──────┐
   YES            NO
    │              │
    ▼              ▼
Move to dock    Crossdocking to warehouse possible?
/stage/buffer   (item allows XD, XD locations exist, XD strategy enabled,
Task: XD        SO candidates exist, insufficient stock in XD locations)
                     │
              ┌──────┴──────┐
             YES            NO
              │              │
              ▼              ▼
         Move to XD      Standard putaway
         location        (channel filling → location strategies)
         Task: XD
         Putaway

Comparison: Opportunity vs. To-Warehouse

Dimension	Opportunity Crossdocking	Crossdocking to Warehouse
Stock assignment	Immediate (at reception)	At shipping order release
Destination	Dock / Stage / Buffer	Crossdocking location (near dock)
Shipping order state required	In-preparation or partially released	Any non-closed/canceled state
Requires XD strategy	No	Yes ("Is crossdocking" flag)
Requires XD locations	No	Yes ("Allows Crossdocking" logic)
Requires item "Allow XD"	No	Yes
Operator flow change	None (same UX as putaway)	None (same UX as putaway)

Configuration Requirements

For Opportunity Crossdocking

No special location or strategy configuration required. The system automatically evaluates all received stock against pending shipping orders during the putaway initiation phase.

For Crossdocking to Warehouse

1. Items: set "Allow crossdocking" = true on each eligible item
2. Locations: configure storage logic "Allows Crossdocking" = true on designated crossdocking locations (near docks/stages)
3. Putaway strategies: create and enable at least one strategy with "Is crossdocking" = true, including destination rules targeting the crossdocking locations
4. Stock assignment: ensure the stock assignment strategy consults crossdocking locations first when the shipping order is released (these locations are consulted preferentially automatically)

Mecalux France — EasyS / SmartUI Setup Notes

Additional setup steps consolidated from Mecalux France practice (in addition to the items above) :

EasyS :

1. Create a dedicated rack for the crossdocking locations.
2. Check Is Crossdocking location = true on the rack.
3. Attach the locations to a Warehouse zone of type Cross docking.
4. Configure the workingZones to include the crossdocking and/or unload processes.

SmartUI :

1. On eligible items, enable Cross-docking in the advanced data tab.
2. Create the crossdocking putaway strategy in sequence position 1 so it runs before the other putaway strategies.

Criteria tab : enable crossdocking. ⚠️ Without any additional criterion, all items will be treated as crossdocking at reception — always add conditions on the state of the pending outbound orders (e.g. status "En attente") to avoid this.

Rules tab : set Zone to the crossdocking zone created in EasyS.

Mecalux France — Known Behavior Notes

• Reception must be done on the RFT : the reception buffer does not trigger crossdocking evaluation. If reception is performed on the buffer, crossdocking is bypassed silently.
• Buffer over dock for direct XD : when the outbound order has an assigned buffer, direct (opportunity) crossdocking routes stock to the buffer rather than the dock — useful for a subsequent packing step.
• Crossdocking overrides reserve : if a crossdocking location exists, the WMS redirects to it even if reserve stock is already available.
• No label is printed in standard direct (opportunity) crossdocking, even for a full pallet — plan for a custom label flow if the customer requires one.

Common Errors

Opportunity crossdocking not triggering despite matching order: The shipping order line is marked as critical or required-to-ship, or the line type mixes container and item requirements (both are required). Remove the critical/required flags or create separate lines.

Crossdocking to warehouse not executing: Item does not have "Allow crossdocking" enabled, or no crossdocking putaway strategy exists/is enabled, or crossdocking locations exist but are not reachable from the reception equipment by route. Check all three configuration elements.

Stock placed in crossdocking location but not prioritized at release: Stock assignment strategy doesn't prioritize crossdocking locations over normal storage. Check the stock assignment strategy configuration to ensure crossdocking location preferences are applied.

Crossdocking location fills up, remainder goes to standard storage: This is normal behavior — the crossdocking process places only what fits. The remainder follows standard putaway. No error; just an expected split.

Shipping order candidate filtered out unexpectedly: The crossdocking strategy has filters on order status, priority, or days until release/load that exclude the order. Review the "Is crossdocking" strategy's filter settings.

Cutting stock crossdocking creates wrong stretch quantities: Cutting stock requires total-quantity handling; partial stretches cannot be crossdocked. Ensure the full stretch length matches the shipping order's demand exactly, or split orders to match available stretches.

Interface Paths

Interface	Path
Web — crossdocking putaway strategies	"Configuration" → "Putaway strategies" (filter by "Is crossdocking")
Web — item "Allow crossdocking"	"Inventory" → "Items" → item → settings
Web — location storage logic	"Warehouse" → "Locations" → location → "Change storage location logic"
RFT — putaway flow (opportunity XD)	Normal putaway flow; system routes to dock/stage automatically
RFT — putaway flow (XD to warehouse)	Normal putaway flow; system routes to XD location automatically

Related

• Reception — crossdocking is triggered during the putaway phase following reception
• Putaway — crossdocking uses the putaway strategy engine; "Is crossdocking" strategies are a subtype of putaway strategies
• Shipping — crossdocking locations feed stock assignment at order release; opportunity crossdocking routes directly to shipping docks
• Container (LPN) — containers are the primary unit being crossdocked; stacked containers and multi-reference containers have specific rules
• Stock — stock status and logistic attributes affect crossdocking eligibility
• Inbound Order — ASN containers can carry exclusive reserves for specific outbound orders, enabling crossdocking on receipt
• Outbound Order — SOR lines with crossdocking-eligible items become crossdocking candidates; order priority drives XD selection