Skip to main content

Editing an order

Use this page to change the header of a saved order.

Before you start​

  • The order is not Closed or Cancelled.
  • You have the web action shipment_order_save and the API right shipment_order_update. By default ADMIN, MANAGER, SUPERVISOR and OPERATOR have both.
  • Know what is locked. Type, Ship To and Carrier can change only before the order is launched (before the first release). Priority, Requested Ship and Notes can change until the order is Closed or Cancelled. See the table in Order screen.
  • Owner cannot be changed after the first save, even if the field looks open. See below.

Steps​

  1. Open the order from Outbound > Orders.
  2. Change the fields you need on the Header tab or the Ship To tab.
  3. Click Save on the order toolbar.

What Save sends​

Save sends only the fields you changed, with the version of the order that you saw. It does not send the fields you left alone. This matters on a released order: a field that is locked is checked only when it is sent. If Save sent every field, any save on a released order would be refused for a field you never touched.

The fields Save can send are Type, Ship To, Carrier, Priority, Requested Ship, Notes and the hidden external_id. If you changed nothing that is on this list, Save does not call the server. It says Nothing changed. The fields Owner, Order #, Status and Cancel Reason are not on the list. Changing only one of them gives Nothing changed, and the change is not kept.

Source: crates/services/web-ui-server/src/extensions/customization/shipment_order/save_action.rs:204-250.

What the screen says​

ResultMessage
SavedOrder saved
Nothing to sendNothing changed
A required value was emptiedFill in Owner, Type first (only the missing names are listed)
The server refusedSave failed: {error} and the grid refreshes

What changes​

WhatChange
OrderThe changed fields are written. The version goes up by one.
Pick tasksIf Priority changed, every pick task of the order gets the new priority at once.
EventNone for an order edit.

Source: crates/libs/wms-outbound/src/service/order/update.rs:79-137.

What can go wrong​

MessageMeaningFix
'order_type_id' can only be changed before the order is released (it is {status})You changed a locked field on a launched order. The same wording is used for ship_to_id and carrier_id.Cannot be fixed. The order was promised to the customer. Cancel the order, or leave the field.
'order_type_id' can only be changed before the order is released (it was already released, and reads {status} only because every line was cancelled)The order reads New again, but it was launched before.Same.
'priority' cannot be changed on a {status} order (also requested_ship_date, notes, external_id)The order is finished.Cannot be fixed.
ship_to owner {id} is not a customer (owner_type must be 'Cus')The new Ship To is not a customer.Pick a customer.
Save failed: version conflict on shipment_order {id}Somebody saved the order after you opened it. The error carries the current version and status.Press Refresh or open the order again, and repeat your change.

Unlike Release, Allocate and Unallocate, Save does not repair its own copy after a version conflict. You must reopen the order.

Not confirmed by code: that Save really does not repair the version after a conflict. The code shows no repair step, but the refresh of the grid after the error may have the same effect. To verify: open the same order in two browsers, save a note in the first, then save a different note in the second, and press Save once more in the second.