Where the sales-to-dispatch handoff breaks

Consider a supplier whose customer accepts a quote on Tuesday afternoon. The salesperson marks the deal as won and asks the warehouse to send it tomorrow. The order contains the correct products and agreed price. It looks complete.

The delivery address is the customer’s head office. The equipment is needed at a construction site. Nobody has confirmed whether that site has a forklift, whether the customer wants everything together, or who agreed to absorb the extra freight charge. The warehouse starts calling around while the customer assumes the shipment is already organised.

This is an illustrative example, but it captures the distinction that matters: an accepted sale and an order ready for dispatch are different operational facts. An effective sales to dispatch handoff makes those facts visible before someone starts moving goods.

At Bosar, we approach this as a chain of decisions with owners. Better software can support that chain. It cannot resolve a delivery promise that nobody has actually confirmed.

A won deal leaves several questions unanswered

Sales needs to know whether the customer has agreed to buy. Operations needs to know what it has authority to fulfil, when, where and under which conditions. A single status cannot answer both questions reliably.

A useful order journey separates acceptance, release, picking, packing and dispatch. Each stage should represent something that has happened, with evidence behind it. A salesperson changing the opportunity status should not silently certify stock availability or a passed credit check.

Promised dates and available dates

A customer might request Friday, a rep might say Friday should be possible, and a supplier might confirm that incoming stock is expected on Friday. Those are three different commitments.

Record the requested date, the date the business has confirmed, and any dependency behind that confirmation. If stock is still incoming, the order should show who is checking its arrival and when the promise must be reviewed. An AI summary must preserve the uncertainty rather than turning an expected date into a guarantee.

Delivery details and commercial details

The billing address identifies where the invoice goes. The delivery address identifies where goods need to arrive. The site contact may be a third person entirely.

Delivery access, unloading arrangements, opening hours and a purchase-order reference can determine whether a shipment is usable when it arrives. Capture them in fields the dispatch team can find. A note buried in the salesperson’s email should not be the only place the delivery instruction exists.

Define what makes an order releasable

A release check should answer the questions that genuinely prevent fulfilment. Adding twenty mandatory fields to every sale can create another workaround. Define a short common record, then add requirements for relevant order types.

For example, a customer collection needs a collection contact and readiness confirmation. A pallet going to a site may need unloading information and a delivery window. A made-to-order item may need an approved drawing revision before it can enter production at all.

Give each check an owner

The following is a proposed starting point, to adapt to the way your business operates:

Release requirement	What needs to be confirmed	Accountable role
Commercial agreement	Accepted products, quantities, price and current revision	Sales
Supply	Stock allocation or confirmed production/procurement plan	Operations
Delivery	Correct destination, contact, access and required service	Sales or order administration
Payment conditions	Applicable credit or payment requirements satisfied	Accounts
Freight decision	Service, payer and approved customer charge	Dispatch with commercial owner
Final release	Required checks complete or a recorded exception approved	Named release owner

Some companies combine these responsibilities in one person. That is fine. The point is to make the decision explicit, including who acts when a field is missing. A red warning with no owner is simply a more visible delay.

Build three clear fulfilment paths

The happy path is useful for a demonstration. Partial orders and urgent requests reveal whether the handoff works in daily operations.

The basic sequence can stay simple:

Accepted order → release review → full shipment, agreed split or hold → confirmed dispatch → customer update and invoice review.

The important detail is the evidence that moves an order between those stages. A draft shipment should not be treated as goods sent. A held order should have a reason, an owner and a next review time.

Complete shipment

For a complete shipment, dispatch receives the approved order version, allocated quantities, delivery instructions and freight arrangement. Picking and packing then confirm what is physically going out.

If the warehouse discovers a shortage or damaged item, that finding must change the order’s readiness. It should not be confined to a warehouse message while the customer receives an automatic confirmation that everything has shipped.

Split shipment or backorder

Imagine an order for twelve units with eight available now. A split requires more than reducing a quantity on a packing slip. Confirm whether the customer accepts the split, whether the remaining four have a dependable date, and how the additional freight is handled.

Keep the remaining obligation visible after the first dispatch. The first shipment completes part of the order, not the relationship. This is also where invoice quantities must follow the agreed billing policy rather than copying the original total without review.

Urgent exception

Urgency should shorten the decision path, not erase it. An urgent order can move to a named manager who sees what is missing, decides what may proceed and records the reason.

Some conditions should remain hard stops, such as an unconfirmed product identity or an unresolved requirement that affects safe handling. Others may allow an authorised commercial exception. Define those distinctions before a truck is waiting at the door.

Freight has three separate numbers

An estimated transport cost, the service that gets booked and the freight amount charged to the customer are related, but they are not interchangeable.

A salesperson may estimate freight before the packed dimensions are known. Dispatch may later choose a different service because the customer’s site cannot receive the original vehicle. Accounts then needs to know whether the additional cost was accepted, absorbed or still under discussion.

FedEx’s estimating guidance lists shipment characteristics such as origin, destination, weight, dimensions and service as cost inputs. Its estimates can also differ from final charges. Those are useful examples of why accurate inputs matter, although every freight carrier and service has its own conditions. FedEx shipping-cost guidance.

Make the commercial decision visible

A practical record keeps the estimate, booked service and customer charge in separate fields. It also records who approved a difference.

Suppose the agreed customer charge is $180 and the selected service is $240. That illustrative $60 difference is a decision to resolve. It might be an authorised concession, a quoting mistake or a customer-approved upgrade. An automation that silently copies either figure loses the reason.

Where carrier integrations are available, a system can prepare a comparison using the same shipment details. A person still needs to judge service suitability and approve the commercial treatment. The cheapest displayed rate is not automatically the right delivery decision.

Use the shipment features you already own

It is easy to describe these problems as missing software. First check configuration and actual usage.

For example, Unleashed’s native Order Management supports multiple shipments and invoices against an order, including part shipments. Its documentation distinguishes behaviour when that setting is enabled or disabled. These are existing product capabilities, not reasons to commission a new AI dispatch engine. Unleashed sales module overview.

The more useful question is whether your team uses those records consistently and whether all the information needed to act reaches them.

Put AI around the missing information

A sensible AI-assisted workflow could compare an incoming acceptance email with the order, flag a different delivery address, and prepare a short list of unresolved instructions. It could assemble the relevant conversation for the release owner or draft a customer update after dispatch has been confirmed.

It should show where each proposed detail came from. If a customer mentions a new site without giving its full address, the output should say the address needs confirmation. It should not choose a plausible location from an old order.

The order intake workflow covers that earlier capture step. The dispatch and delivery workflow carries the confirmed information through release, shipment and exceptions.

Close the loop after goods leave

Creating a tracking number may indicate that a label or booking exists. Decide which event your operation accepts as dispatch evidence, such as a confirmed collection or an authorised warehouse completion event. Customer wording should match the evidence available.

A useful update states what was sent, what remains outstanding and what the customer can reasonably expect next. If an arrival date is only an estimate, label it accordingly. Customer messages prepared by AI should remain person-approved.

Give accounts the shipment and its charges

Shipment data must reach invoicing alongside the commercial decisions. One documented example: Unleashed invoices created from a shipment exclude charge lines by default. That particular workflow needs an explicit check if freight or other charges must be added. It is not a universal rule across every ERP. Unleashed invoice creation.

The invoicing workflow should therefore reconcile the relevant order, shipment, approved charges and invoice. A successful handoff ends with an understandable transaction, including any remaining backorder, rather than a parcel leaving the warehouse and the paperwork catching up later.

Measure the delays you can actually change

Start with a short sample of completed orders and trace where each one waited. Separate missing-information delays from genuine stock shortages, carrier disruption and customer-requested holds. Otherwise the handoff project will be credited or blamed for issues outside its scope.

Useful measures include the share of orders held for incomplete delivery details, time spent clarifying each held order, changes made after packing begins, and freight adjustments caused by incorrect inputs.

Track the reason as well as the number. If the same destination problem repeats, fix capture at the point of sale. If release decisions wait on one manager, address the decision authority. If information was agreed verbally and never recorded, the underlying problem is verbal order capture.

Frequently Asked Questions

Do we need a new ERP to improve the handoff?

Often the first step is to configure existing order, shipment and status features, then agree how the team uses them. A separate integration becomes relevant when important information cannot reach those records through supported features. Review actual examples before selecting software.

How should partial shipments be handled?

Keep each shipment linked to the original order, with dispatched and outstanding quantities visible. Confirm customer acceptance of the split, the plan for the balance and the freight treatment. Invoice review should follow the company’s agreed billing policy for that order.

Who should own the release decision?

Choose a role that can see the required checks and has authority to resolve or escalate exceptions. Sales, operations and accounts can own individual inputs. One named release owner prevents each department assuming that somebody else gave final approval.

Can urgent orders bypass the normal queue?

They can use a faster, explicitly approved path. Record the reason, approver and unresolved items. Preserve the checks your business treats as non-negotiable. Urgency changes prioritisation; it does not make an unknown product, quantity or delivery destination reliable.

When should customers receive a dispatch update?

After the event your business recognises as confirmed dispatch. Before that, communicate a booking, preparation status or expected collection accurately. For partial orders, identify what has left and what is still pending. An update should reduce uncertainty rather than conceal it behind an optimistic status.