Inxeption · 2023

Multi-shipment checkout for industrial e-commerce

Letting industrial buyers split one order across destinations and delivery dates, and pay the true shipping cost at checkout instead of a surprise bill later.

Role
Senior UI/UX Designer, lead on checkout
Company
Inxeption
Timeline
About 4 months of research and design
late 2023
Platform
Web and desktop
Inxeption checkout: Ship it for me, with an order split into three shipment groups and an order summary

The problem

In industrial e-commerce, buyers usually pay for products up front and for shipping separately, which leads to unexpected fees and frustration. Big orders rarely go to one place on one day.

The goals for the new checkout:

  • Offer a shipping choice per sales channel: self-pickup, or the seller ships.
  • Let buyers split an order into groups delivered on different days or to different locations.
  • Charge the true shipping cost by breaking products into shipments and querying Inxeption's shipping-quote APIs.

At the time, no company had implemented this approach for industrial products.

Research

I started with visual research into how Amazon and other commerce platforms handle multiple ship-from origins and ship-to destinations.

Amazon checkout with items shipped to different addresses
Amazon: choosing where to ship each item.
ShipperHQ article on multi-origin shipping
ShipperHQ: how multi-origin shipping works.

Structuring the flows

I split the existing checkout into two buyer flows. Buyer-Simple covers pickup, or shipping to one location on one date. Buyer-Complex covers shipping to several locations or on several dates.

On the seller side, a new shipment-settings section on the channel details page let commerce partners decide which options buyers could choose.

Design board organized into Setup, Buyer-simple, Buyer-complex and CP flows
The design board: setup, both buyer flows, and the commerce-partner (CP) settings.

Requirements

  • Buyers can add as many shipment groups as they need, as long as the cart has enough items to allocate.
  • The order summary updates as addresses change, because shipping fees and taxes depend on the address.
  • Buyers can remove groups, but at least one always remains.
  • Open question we resolved: collect delivery details during checkout, or after the order is placed?
Annotated wireframe of the multiple-locations shipping step, with team feedback in the margins
Working wireframe with the team's notes, including the debate over naming: group, delivery group or shipment group.

The final design

We collected delivery details during checkout, so the buyer sees the real total before paying. I worked with the PM to keep required fields to a minimum, so nobody faces extra forms after confirming an order.

Open the checkout prototype ↗
Full final checkout page: items, details, shipping groups and payment
The full checkout: one order, three shipment groups, true shipping cost in the total.

Also at Inxeption: AI search vs. browse

For the desktop directory, I designed a way to switch between an AI search mode and a standard browse mode, so buyers could ask for what they need or scan the catalog the way they always had.

The directory moving between AI search and browse.

Also at Inxeption: seller memberships

The seller sign-up flow walks prospective sellers through membership tiers, a page for each benefit, and a closer look at the Managed Store app.

Open the membership prototype ↗

Reflection

What I'd push next. I'd test the complex flow with real buyers placing real split orders. The shipment-group model held up in design reviews, but the true test is a buyer allocating hundreds of items across sites and dates, and I'd want to see where that breaks.

What I learned. Nobody in industrial e-commerce had solved this, so we borrowed from consumer platforms that had. Amazon and the shipping platforms gave us a shared starting point, and splitting the work into simple and complex flows kept the common case fast while still serving the hard one.