HOW-TO · B2B portal

How to release B2B partial shipments safely

Wholesale buyers often prefer receiving available stock now instead of waiting for a perfect order, but every partial shipment creates a second promise: what shipped, what remains, what gets invoiced and when the rest will follow. This guide shows how to release B2B partial shipments from ChannelDock’s B2B Portal into a controlled partial shipments workflow.

Promise
what ships now
Hold
remaining lines safely
Invoice
only what left the dock
Partial release decisionPortal + WMS
Line 1 · SKU-1462120 / 120 releasedships today
Line 2 · SKU-882064 / 64 releasedinvoice now
Line 3 · SKU-47110 / 90 heldETA confirmed before promise
Buyer sees the split before release. Warehouse receives only the approved shippable work.

Why this matters: Microsoft Business Central documents customer-level shipping advice for partial vs complete shipments, Shopify describes B2B portals as the place for order status and invoices, and B2B OMS competitors keep highlighting partial shipments because spreadsheets break when one order becomes three warehouse and invoice events.

1 ordermultiple fulfillment events
Ship firstinvoice shipped quantities
Per buyerpartial-shipment consent
Open lineremains promised, not forgotten

Before you start: separate order acceptance from shipment release

A B2B order can be commercially accepted while still not ready to ship in full. The mistake is treating the portal order, warehouse pick task and customer invoice as one indivisible object. Partial shipment control starts by splitting those decisions apart.

Buyer policy

Decide which wholesale accounts accept partial shipments, which require complete delivery and which need approval per order. Microsoft’s Business Central calls this shipping advice; the same idea belongs in your portal rules.

Line-level availability

Track available-to-promise stock by SKU, warehouse, case pack and reserved quantity. A full order total is not enough; the release decision happens line by line.

Finance rule

Define whether you invoice per shipment, consolidate later, or hold invoicing until completion. For Net 30 buyers, this must also respect B2B credit limits.

Practical rule: a partial shipment is safe only when the buyer-facing promise, warehouse task and invoice logic all describe the same split. If one team says “part shipped” while another says “order complete,” support tickets and payment disputes follow.

Step-by-step workflow to release a B2B partial shipment

Use this process when a wholesale order is approved, some lines are available and the buyer would rather receive useful stock now than wait for the remaining SKUs.

Check whether the buyer accepts partial delivery

Start with the account rule in the B2B portal. Key accounts, retailers and franchise groups may have routing guides that reject incomplete deliveries, while independent dealers may prefer early stock. If the rule is not stored per buyer, ask before release and record the decision on the order.

Common mistake: assuming every B2B customer wants speed. Some buyers value one complete receiving event more than early stock.

Recalculate available-to-promise at line level

Compare ordered quantity, reserved quantity, on-hand stock, already-picked stock and inbound replenishment. Do not release based on a stale portal snapshot. The release should use the same inventory truth that powers your inventory overview.

Common mistake: shipping the visible stock while forgetting another marketplace, POS order or sales rep quote already reserved it.

Choose which lines move now

Prioritize complete case packs, urgent replenishment lines, high-margin items and SKUs that avoid buyer stockouts. Keep low-value or incomplete carton lines on hold if shipping them alone would create freight cost, receiving work or invoice noise that outweighs the benefit.

Show the buyer the split before warehouse release

In the portal, show “ships now,” “ships later,” expected dates, carrier or pallet method, and whether the remaining quantity stays open. For large accounts, require buyer confirmation before creating the pick wave. This is where a B2B Portal prevents another email loop.

Create a warehouse task only for released quantities

The WMS should receive the approved quantities, not the full order with a note that says “do not pick line 3.” Released lines become a normal pick, pack and carrier workflow; held lines stay out of the active queue until stock and approval are ready.

Common mistake: letting the warehouse see the full order and relying on manual interpretation at the packing station.

Invoice and notify from the shipment event

For most B2B teams, the cleanest rule is to invoice what shipped and keep the remainder open. Include the shipped lines, quantities, tracking, packing slip and open balance in the notification. If the customer prefers one consolidated invoice, still record each shipment event so finance can reconcile later.

Keep the remainder visible until closed

The backordered or held quantity needs an owner, ETA, buyer-facing status and next action. It should not disappear because the first parcel left the dock. Review open remainders daily, especially before order cutoffs and inbound receiving waves.

The safe partial-shipment release path

The strongest B2B portals do not simply expose order status. They turn a partial shipment into a controlled operational handoff: buyer consent, line allocation, warehouse release, shipment documentation and remainder follow-up.

A partial shipment is not half an order. It is a new promise with its own stock, status, documents and invoice rule.

Buyer rule
Line ATP
Release qty
Ship + invoice

Common B2B partial-shipment pitfalls

  • Letting sales approve a partial shipment in email while the warehouse still sees the full order.
  • Posting the whole invoice even though only some quantities left the dock.
  • Marking the customer order complete after the first shipment and losing the remaining demand.
  • Not showing partial-shipment consent per buyer, branch or contract.
  • Ignoring freight economics: two small shipments can destroy margin even when the buyer says yes.

Manual split handling vs. ChannelDock partial shipments

Manual partial shipment handling looks flexible until volume grows. Then every split creates extra emails between sales, support, warehouse and finance.

Without ChannelDock

  • Buyer approval lives in an inbox, not on the order.
  • Warehouse teams receive full quantities and rely on notes to avoid mistakes.
  • Invoices, packing slips and open remainders drift out of sync after the first shipment.

With ChannelDock

  • B2B buyers order through a controlled portal with account rules and visible status.
  • Only released quantities enter order handling, picking and shipping workflows.
  • Remaining lines stay visible for replenishment, approval and buyer updates.

Explore partial shipments →

B2B partial shipment FAQ

A B2B partial shipment is a shipment that fulfills only part of a wholesale order. The remaining quantity stays open as a backorder, held line or future release instead of being cancelled or forgotten.

Yes, unless the buyer’s account terms already allow partial delivery. Some customers want early stock; others need one complete delivery for receiving, freight or invoice reasons. Store that preference per buyer.

The safest default is to invoice shipped quantities and keep the unshipped remainder open. If a customer requires consolidated invoicing, still record each shipment event so finance can reconcile what left the warehouse.

A partial shipment usually means some ordered quantities ship now and the rest remains open. A split shipment can also mean one fully available order is shipped in multiple parcels, warehouses or carriers. In practice, B2B teams need rules for both.

Show the buyer what shipped, what remains, the expected date, the tracking link, the invoice status and the next action inside the portal. Most tickets happen because the buyer cannot see whether the missing line is delayed, cancelled or already planned.

Avoid it when the buyer rejects incomplete deliveries, the freight cost is higher than the margin, the remaining ETA is unclear, or the split would break a retailer routing guide, case-pack rule or credit-limit policy.

Related workflows to improve next

After partial shipments are under control, tighten the surrounding B2B workflows that decide whether the order should be released, held or updated.

Approval workflows

Route exceptions before wholesale orders enter fulfillment.

Read the how-to

Credit limits

Keep shipment release aligned with payment exposure.

Read the how-to

Order tracking

Show buyers what shipped and what remains open.

Read the how-to

B2B Portal

Give wholesale customers controlled self-service ordering.

View feature

Release partial B2B shipments without losing control

Use ChannelDock to connect portal promises, warehouse release, partial shipment status and buyer updates in one operational flow.