Where are customer MSLS requirements maintained?

Customer MSLS requirements are maintained in the customer master in HublerX — linked to the ERP customer record. Requirements can be set by customer, by customer tier, or by product category. When a customer's MSLS requirement changes, it is updated once and applied automatically to all future orders.

Does HublerX account for transit time when calculating MSLS compliance?

Yes. HublerX calculates MSLS compliance based on the remaining shelf life at the point of customer delivery — not at the point of dispatch. Transit time by lane and carrier is configured in HublerX and factored into the compliance calculation automatically.

What happens when no compliant batch is available for an order?

HublerX flags the breach before the picking list is generated, notifies the commercial team and production planner simultaneously, and surfaces the next available production run that will produce a compliant batch — with the earliest possible dispatch date. The commercial team can then manage the customer expectation proactively.

Can this workflow handle split shipments — where part of an order ships from one batch and part from another?

Yes. Where a single order quantity cannot be fulfilled from one compliant batch, HublerX calculates the optimal split across multiple batches — each meeting the MSLS requirement — and generates a picking list that specifies the exact batch and quantity for each line.

Shelf Life Aware Inventory Allocation

HublerX allocates finished goods inventory to customer orders based on each customer's minimum shelf life at shipment requirement — automatically, before the picking list is generated, preventing MSLS breaches before the truck is loaded.