Processing order tracking codes

In the Tracking Code view, you can search for an individual order, check the order and customer information, save the shipping tracking code, and see the result of the customer message. The workflow is part of Order Processing and is intended for fast packing and shipping work.

Saving changes the order status to Shipped, adds a status history line, and attempts to send the customer a tracking notification if the customer hasn't already been notified. The status change and tracking code may be saved even if the message fails to send, so always check the scorecard.

Tracking codes: mark the order as shipped and notify the customer

Tracking codes mark an order as shipped and consolidate search, review, storage, and notification results into one page. Open /orders/handling/tracking . The search accepts up to a 7-digit order ID or a current tracking code longer than that. When an order is found, the page displays the order ID and date, current status, customer name and email, shipping method, current tracking code, total, and currency.

The new tracking code is entered in the Tracking Code field. Review and Save opens the confirmation Save tracking code? , which displays the order ID and the code entered. Save tracking commits the change. The scorecard displays the new tracking code, status, customer message result, any external status sync warnings, and the request ID.

The workflow is not just about editing a text field. The service prevents processing an order that is already in the Sent state, updates the status and code in the same database transaction, and records the changes in history. The customer message and external status synchronization then occur as separate steps.

Why is the tracking code stored on the checkout page?

Saving the tracking code on the checkout page reduces the risk of updating the wrong order, as the order summary is displayed before confirmation. At a minimum, check the order ID, customer name, email, shipping method, and current status. If the information does not match the order you are packing, do not proceed to save.

One step updates the tracking code, sets the order to Sent, and adds a comment to the status history in the format Tracking code: KOODI . Additionally, a separate audit history records the status or tracking code change when the value actually changes. This gives the administrator a record of what was changed, on which page, and with whose ID.

Customer communication reduces delivery status inquiries only if the message is actually sent. The scorecard's Customer notified , Customer already notified , Notification failed to send , or other reason for skipping tells you the actual outcome. Don't conclude the success of a message just from a new Sent status.

Search and check the correct order

Search for the correct order by entering Order ID or Tracking Code . Use Order ID when you know the order number. The current tracking code is suitable for searching when only the tracking number is on the package or shipping document. Up to 7 digits are interpreted as the Order ID; a longer value is interpreted as the tracking code.

When the search returns an order, compare the summary to the physical shipment. Check the customer name and email, shipping method, date, current tracking code, total, and current status. If no order is found that matches the search, the page displays a notification and does not open the save form. Fix the search tag instead of blindly trying to save a new code.

An order that is already in the Shipped status cannot be processed with this function. The request will be rejected before a new tracking code, status history, and notification are generated. If the code of a shipped order needs to be corrected, do so in the order's own tracking code editor and assess the need for customer communication separately.

Enter and confirm tracking code

Enter the tracking code exactly as provided by the carrier, for example JJFI123456789FI . The code must be a maximum of 64 characters. The first character must be a letter or number; letters, numbers, a period, an underscore, a plus sign, a hyphen, a slash, and a space are allowed after that. A value that is empty, too long, or contains other characters will prevent saving.

For a pickup order, you can use the value nouto . This value directs the MVC notification request to the pickup state, but the current handler still sets the order to Shipped. It does not change the stored state to Available for Pickup. If your business requires an Available for Pickup state, use a separate workflow to make the status change.

Select Review and Save and read both the order ID and code from the confirmation. Only then accept with the Save Tracking action. Saving requires administrator write access and a valid session ID. Do not close the output until you have reviewed both the saving and the notification status.

What happens in recording

The save will recheck the tracking code and order, resolve the Sent status ID from the settings, and read the customer's previous notification status. The database transaction will update the order status and tracking code, add a status history row, and write the status and code changes to the audit trail. If this step fails, none of these changes should be treated as successful.

After the database transaction, the service resolves the customer message. If the order's customer_notified flag indicates that the customer has already been notified, no new message is sent. Otherwise, the MVC messaging service is given the order, customer, email, language, and tracking code. A successful submission is noted on both the order and the newly created status history line and is logged for auditing.

Finally, the order is synchronized to external systems. Sync issues are returned as scorecard warnings and do not cancel the tracking code that has already been saved. The request ID helps you to resolve a single failure with support.

Check the customer's notification

A customer tracking notification is only sent when it is not blocked by a previous notification flag on the order. This is a per-order blocking, not a same-code comparison. If the customer has been previously notified about an order event and a flag has been set, the new tracking message can be skipped. Changing the code later will not reset the notification flag.

A successful notification can include a tracking code and the carrier's tracking link, if the order's delivery information includes a link. Without a link, the customer can receive just the code. The pickup value is passed to the messaging service as a separate pickup status. The actual message template and possible tracking link are generated in MVC's messaging service.

If the messaging service returns a sending error, the scorecard displays Notification sending failed and the error information. The order status, code, and history are already saved at this point, and a message error will not cancel them. Resolve the message resending separately; do not save the same order again through this page, as the Sent status prevents further processing.

Read the scorecard and resolve discrepancies

The scorecard confirms the order ID, saved tracking code, and new status. The customer message status is shown with a separate label. Any external sync warnings are separate from the notification error, so check both. Copy the request ID if you need technical clarification.

If the result says that the customer was already notified, the code and status may still be successfully saved. If the notification failed, the delivery mark may still be successful. If the external synchronization warns, the local change may be ready but the receiving system has not yet matched it. These results should not be combined into a single success or failure conclusion.

Saving the tracking code does not change the prices, balance or visibility of the products in the online store. The customer can see the tracking code in the message and in the store's own order history, if the online store implementation in use shows the information. Verify the customer view and message template for each store.

Good to know

It is important to know that the function only processes orders that have not yet been marked as shipped. The maximum length of the input is 64 characters, and the allowed character set is limited. In the search field, a maximum of 7 digits means the order ID; a longer value is searched for as a tracking code.

The save always sets the status to Sent even when the code is nouto . The customer message is only sent if a previous order-specific notification entry allows it. Failure of the message or external synchronization does not undo the status and code change that has already been made.

After each processing, check the order, customer, new status, tracking code, notification result, sync warnings, and request ID. If you are only fixing the tracking code for an order that has already been shipped, use the separate order editing functionality instead of this shipping confirmation workflow.