Routing Consolidation

Owned by Megan Stanage
Aug 30, 2024
2 min read

Routing Consolidation Overview

Routing Consolidation is designed to take in a request of demand lines with many attributes and determine, based on those attributes, whether any particular line should be consolidated with another.

These attributes are fields such as Customer, End Address, Customer PO, Mode of Delivery, etc.

Utilizing attributes instead of base data fields allows you to define the consolidating characteristics instead of limiting them to our definitions.


Workflow

 Routing Consolidation Request JSON

The Request JSON contains information about the demand lines submitted for consolidation.

Most importantly, it should contain the attributes for the lines you are attempting to consolidate.


 Match Consolidation Key

The first loop in Routing Consolidation logic is to check for the consolidation key.

This ties the entire JSON submission, not individual lines, to a specific consolidation policy.

  • If a key matches the consolidation policy, the evaluation begins.

  • If there is no match, no consolidation occurs.

Configurations

Endpoints

  • Swagger


 Within Effective Dates & Time Fence

The next two logic loops are both date-based:

  • First, checking if the ship date falls within the start and end date of the consolidation policy.

  • Second, checking if the ship date falls within the time fence for the policy relative to today’s date.

The former is a static, long-term time fence. The latter is a moving period of time centered on the current date.

If either of these checks fail, the line is not consolidated and evaluation begins on the next one.

Configurations

Endpoints

  • Swagger


 ShipTo Address Match

Routing Consolidation logic first tries to match against the ShipTo on the demand line.

  • If this is the first line being evaluated, it starts its own consolidation group.

  • If the next demand line with a matching address is evaluated, it is considered for this consolidation group.

Configurations

Endpoints

  • Swagger


 Attribute Match/Group Source Orders

After the ShipTo address is evaluated, the line attempts to consolidate against the attributes set on the consolidation policy.

  • If the line matches the attributes for the policy, it is added to a consolidation group with matching attributes. The order line must match all attributes to be added to the group.

  • If the line does not match, it is the first line in a new consolidation group.

Configurations

Endpoints

  • Swagger


 Routing Consolidation Response JSON

After all lines are evaluated for consolidation, they are provided back in the Response JSON.

Each consolidation group has a unique ID for use by the host system, if necessary.

Lines that were not added to a consolidation group are not included in the response.

Configurations

Endpoints

  • Swagger



FAQs

Q: Does Routing Consolidation logic consider demand that has already been picked and/or staged?

  • A: It considers any demand lines that have been submitted to the endpoint within the same request. It is up to the host system to decide which lines qualify for consolidation.

Q: How are the consolidated lines grouped?

  • A: Each consolidation group has a unique identifier via GUID (Globally Unique Identifier).


Feedback

Submit feedback.