Handling backorders and partial shipments in a buyer portal

In welding supply, a backorder is routine — a spool is out until next week, a can shipped from a different warehouse, a full order goes out in two shipments. Handled by phone, that means a second call later to explain what actually shipped. Here is how it stays clear without one.

Why backorders are where phone orders get confusing

An order taken over the phone is a single conversation, at a single point in time. If half the line items ship today and the rest ship next week, that split has to be communicated separately — a follow-up call, a text, an email — and it is easy for the buyer's own records to fall out of sync with what your team knows internally.

What a buyer should see, per line item

The fix is not a phone call explaining the split; it is a status per line item that both sides can already see. A confirmed order should show which lines shipped, which are backordered, and — where known — an expected date, without either party needing to ask. The buyer checks their own order history instead of calling to ask "did the rest of this go out yet."

Partial shipments don't need a new order number

When an order splits across two shipments, the cleanest approach keeps it as one order with per-line status, rather than creating a second order number for the remainder. A buyer looking at their order history should be able to tell, at a glance, that one PO produced two shipments — not go searching for a second record that may or may not be linked to the first in their own system.

• Per-line status: shipped, backordered, or pending — visible on the order itself, not communicated separately.
• One order, not two: a partial shipment updates the existing order rather than spawning a second record to track.
• No status call required: a buyer checking their own order history removes the “what shipped” call entirely.

See how order status is tracked in the SupplyDesk dashboard →