One order, two delivery runs
A wholesale customer orders tea and coffee for the same buyer. Tea leaves on Monday and coffee on Wednesday. Keep one sales order and add a delivery record for each run, with its own reference, destination, contact and assigned products.
| Order line | Quantity in its SKU unit | Delivery |
|---|---|---|
| Tea carton | 8 | Monday / DEL-101 |
| Coffee carton | 5 | Wednesday / DEL-102 |
Assignment selects a whole order line. A delivery record does not divide the eight-carton tea line into two four-carton deliveries. If a line needs partial physical dispatch, record the actual warehouse movement and inspect its outbound snapshots; do not infer shipped quantities from the count of assigned lines.
Choose a destination belonging to the buyer
Open Sale → Sale order management, edit the order, and review the saved merchant address under Basic information. The order address supplies the tax-zone context when building editable product snapshots. The delivery record's address and contact fields describe its destination.
A selected address must belong to this order's merchant and be active. The same check applies to new orders, the merchant portal, historical imports and delivery updates. Main accounts have separate data, and staff can open only orders within their permitted merchant scope.
If an old address is no longer available, the editor warns you to select an active address or clear the selection. It retains the historical reference until you make that choice. If the order or address query fails, reload before saving; an unknown result does not mean the merchant has no addresses. Changing delivery metadata does not reprice the frozen order or rewrite its recorded tax.
Reassign a line with one save
- Open the order's Delivery information tab and add the delivery records you need.
- Enter each run's reference, destination and contact details.
- Open Assign products, select the order lines for that delivery, and save.
- Review the affected delivery records. Moving a line removes it from its previous delivery and assigns it to the new delivery in one transaction.
The server checks that each selected snapshot belongs to this sales order and is a sales-plan or actual outbound snapshot. A failed save leaves all assignments unchanged, with the selection available to correct and try again. Pasting delivery details also restores the original row if saving fails. Clearing a field is an explicit edit; it is different from leaving the field untouched.
A delivery record, physical stock-out, delivered status and customer receipt are separate facts. Use the warehouse stock-out workflow to move physical stock. Use receipts to record money collected. Adding a delivery record alone performs neither action. See the sales manual, warehouse manual and available-stock guide.
Let an Agent inspect the plan first
An owner-created read API Key lets an Agent read order details and delivery records through HTTP or MCP. It cannot save assignments. Owner-created keys cover that owner's account, while staff sessions retain their merchant restrictions.
With a write-enabled key and an authorized task, an Agent can read the operation schema, confirm the order, buyer, active address and snapshot IDs, then submit the target delivery's product list once. A successful response includes the affected assignments. After a timeout, read the records before retrying a write. See the Agent connection guide for the Skill and MCP setup.
Start with a representative order in the free plan: all features free for one month, with 1 hour of consultation and assistance included. Follow it through delivery planning, actual stock-out and receipt recording to evaluate how your team and Agent share the workflow.