“Where is my order?” Answer from the record.
The customer PO should reach the team processing the order. Keep the delivery order, processing status, dispatch date, transporter and LR reference together, so the next customer update comes from a shared record.
- Customer PO details carried into the delivery order
- Processing status with a clear next action
- Dispatch date, transporter and LR reference
- Payment visibility alongside delivery coordination
Delivery coordination and commercial closure run in parallel.
Representative view · Dispatch · sample data
A delivery update should not need three calls and a forwarded message.
Point at a card, or tap it, to see what changes with Sales OS.
Customer PO details pull into the delivery order when the offer is converted.
Keep the order processing status visible in Dispatch Coordination.
Keep the dispatch date on the coordination record.
Record the transporter and LR or reference number beside the delivery order.
See the payment position alongside coordination. Commercial closure and dispatch progress remain separate.
From the customer PO to a useful delivery update.
Follow the sample workflow. Choose a step or press Play.
DO-318 · Aster Projects
Creating the delivery order confirms the order. Customer PO APL-1042 is carried into the record.
Build the answer the customer needs. Then record the dispatch update.
Add a date, transporter and reference to a sample delivery order. The preview turns those details into a clear internal update for the next customer conversation.
Prepare the delivery update
Dispatch date · Transporter · LR / reference
Processing
Add the dispatch details to build a useful internal update for the next customer conversation.
The dispatch update does not change the amount received or commercially close the order.
One record for the handover. Four views of what happens next.
Choose a view to explore the working context.
Start with the customer PO already there.
Use the delivery order created from the offer. The assigned team processes it with the customer’s order context.
The next team gets the context. The owner keeps visibility.
Choose a page to explore the work around the sale.
What your team gets.
The handover is working when the next person can act.
Sales should not need to repeat the customer PO. The processing team should not need to search for the transport reference. Keep the coordination context beside the delivery order.
Get clear on the workflow.
01What does Dispatch do in Sales OS?
It coordinates delivery-order processing, dispatch dates, transporter details, LR or reference numbers, notes and order processing status.
02Does it generate an invoice, e-invoice or e-way bill?
No. Sales OS Dispatch Coordination does not include invoicing. Continue those activities in your existing business systems.
03Does it check available stock or move inventory?
No. This workflow has no available-stock linkage or inventory movement.
04Can the payment position be updated here?
Yes. Payment confirmation can be updated in Dispatch Coordination or Confirmed Order, and both update the same commercial status.
05Does a dispatch update close the order?
No. Dispatch progress runs alongside the commercial flow. Full payment or manual commercial closure closes the order.
Make the next delivery answer easy to find. Control wapas lijiye.
Walk through a customer PO, a delivery order and the details your team needs for its next update.
