Two of our customers came to last quarter with shipment lane requirements that, on paper, look like opposites.
A major retailer needed strict, non-overlapping postal code coverage across their lanes with clean separation, no ambiguity, and every ZIP routed to exactly one lane per carrier service.
Separately, a high-volume DTC brand running staggered same-day trailer closeouts off a shared destination set needed the opposite: overlapping postal codes across lanes, so multiple trailers serving the same destination set could share a single carrier method out of the same origin, with each trailer running on its own cutoff schedule.
These differing strategies required more flexibility from our product, which was the basis for the Shipment Lane Management enhancements we’re launching this week. This is the first wave of a multi-phase release that gives fulfillment operators the configuration flexibility their actual operations require.
What's new today
Allow Overlapping Postal Codes . Shipment Lane configurations group lanes under a carrier and optional service methods. Until now, postal code uniqueness was enforced at the configuration level: a ZIP could only exist in one lane per carrier service method. That worked well for operations that need clean, non-overlapping coverage, but wasn’t the best fit for customers running multiple trailers serving the same destination set out of the same origin.
The new Allow Overlapping Postal Codes toggle relaxes this enforcement. Operators who need clean separation keep the default behavior. Operators who need to configure multiple trailers serving the same destination set turn it on, unlocking the multi-lane workflows that Wave 2's cascading logic will fully operationalize over the coming weeks. Both patterns are now supported on the same platform.
All Postal Codes routing. Until now, if you wanted a lane to cover all U.S. postal codes, you had to upload all of them. That's around 40,000 ZIPs — a real maintenance burden, particularly for customers who use a "catch-all" lane to handle anything not routed by a more specific lane.
With the new All Postal Codes routing option, you can configure a lane to cover every destination served by the carrier without uploading anything. Lanes covering all postal codes are badged in Shipium’s UI and sorted to the top of their group, so they're easy to identify at a glance. Prioritization automatically defers to more specific lanes when they apply, so the All Postal Codes lane only catches the shipments that don't match a more refined lane.
A redesigned Console workflow. The Shipment Lane landing page, detail view, and add/edit form have been overhauled. The lane configuration cache now refreshes immediately after a lane is created or edited, so updates appear without a manual page refresh. Several silent bugs in the old workflow are now resolved.
Why this matters
Real fulfillment operations don't fit a single template. Some operators need clean, non-overlapping lane separation because their workflow depends on every ZIP routing to exactly one trailer. Others need overlapping postal codes because they're running multiple trailers serving the same destination set, with cutoffs staggered through the day.
Now, you can configure the platform to match your operation, not the other way around.
