Purpose

In fast-paced fulfillment environments, large LTL or multi-pallet shipments can take minutes, or even hours, to pack, label, and stage. During that time, unexpected ERP updates like order changes or line-item edits can overwrite a shipment already in progress. For warehouse teams, this means lost work, wasted time, and major frustration. The Reject Shipment Imports Based on Tag rule removes this risk by letting users apply a simple tag that blocks inbound updates while they’re working. It’s an easy way to protect active shipments, reduce errors, and keep fulfillment moving without unexpected disruptions.

This article explains how to set up, test, and use the Reject Shipment Imports Based on Tag rule to ensure it works effectively in your shipping environment.

Define a Tag Such As Change Lock to Block Updates to Orders During Fulfillment

The first step is to define a tag that makes sense to your fulfillment team. For our example, we'll use a tag called Change Lock and make it yellow so it's attention-getting to our team.

Steps

1. To define a new Shipment tag: from the main menu, click Lists, and then click Shipment Tags.
   
   
   

2. Install the Reject Shipments Imports Based on Tag Shipment Rule:

   1. From the main menu, click Setup, and then click Shipment Rules.

   2. Click the + plus icon and, in the Rule Search, type "reject" to find the rule.
      
      
      

   3. Click Install.

   4. To configure this Shipment Rule to use your new tag, Enter the name of the tag you defined earlier in the Check for existence of tag box.
      For our example, we'll select the Change Lock tag from the drop-down.
      
      
      

   5. Click Install.
      The system will display a success message and display the Shipment Rules main dashboard. Verify that your new rule is installed and active.
      
      
      

Test a Standard Shipment Update

A good way to test the new update control feature is to enter a simple order, attempt to change it without the tag in place, then try a change after the tag is added to the order. Any order source can be used for this test, such as your integrated ERP.

For simplicity, we'll use the API Samples page in Pacejet to test the process.

Steps

1. From the main menu, click Tools, and then mouse-over API, and then click Samples.

2. Click the Shipments API in the left-hand pane and click the Put tab on the display.

3. Select a sample like 07 Items and Quantity Fully Packed in Packages.txt to test the process.

4. Edit the sample to add a specific ExternalTransactionID and TransactionID before running the Put to send the order into Pacejet, so that the system will update one order rather than send in new orders each time.

5. Click Run It to send this order in.
   
   
   

6. From the main menu, click Transactions, and then click Workbench.

7. Find the order we just submitted with the PUT method on the Shipments API.

8. Click View to open the shipment.
   
   
   

9. To help verify change control, open the package detail section and review the packages and quantities currently in this shipment.
   
   
   

10. Send in a change and observe the change in Pacejet.

11. Go to the same Shipments.Put page we had up earlier, scroll down to find a product, and change the value for the quantity of items being sent for shipping. In this case, we'll update the quantity of "8" to "20" in our sample shipments.
    
    
    

12. Click the Run It button to send this change to Pacejet.

13. Refresh the order you have open on the Rate & Ship page and revisit the detail packing section.
    Take note that the quantity you changed has been updated in Pacejet.

Test the Same Change With Changes Locked Out

The previous steps helped us see how changes get applied into Pacejet. This is a normal process that happens as often as order changes in your business occur. For our scenario here, users plan to begin packing, labeling, and staging a large order.

Steps

1. Open the Shipment that is from the order and scroll down to the Tags section.

2. Click on the plus icon + in the Tag section and select the Change Lock tag we defined earlier.
   
   
   

3. Click Done to proceed.

4. Click Save.

5. After the tag has been added, updates will be blocked.
   As long as the tag is in place, users can safely pack, label, and process a shipment. If an update is required, the tag can be removed to allow updates to be applied.
   
   
   
   

6. To verify that changes are now blocked with the tag in place, return to the Shipments API page we used earlier and submit another change.
   For example, change the quantity of "20" we submitted earlier back to "8".
   
   
   
   
   

7. Click Run It to submit the change.

8. Refresh the order and visit the Packing Details section as before.
   Note how the quantities have not changed. So long as the tag is in place, updates will not be allowed for this shipment.
   
   
   

Another way to confirm the processing step is to review the trace for this order. As shown below, the trace will log that an update was attempted and blocked by the shipment rule per user instructions. This provides a long-term view of processing steps.

Frequently Asked Questions

Here are a few frequently asked questions with answers for common areas of concern.

• Can I rate and ship with the lock in place? Yes, the purpose of the lock is to enable fulfillment activities without concern of updates overwriting the packing, rating, shipping activities performed by the warehouse team.

• How long does the lock stay in place? The order is locked for as long as the tag is in place. If updates are required, users should remove the tag and save the update.

• Is the customer service team notified of rejected changes? No, change attempts are logged in the trace. But teams should communicate if changes are required.

• What if packing takes several hours or over several shifts? This is not an issue as the order will remain locked while fulfillment is completed.

Back to top