techSHIP

Hello, I need to add new fields below in conditon list in client / account / restrictions / Advanced mode / condition Field list to be added is : Ship from name Ship from company Ship from address 1 Ship from address 2 Ship from address 3 Ship from city Ship from postal Ship from country Ship from state Ship from phone Ship from email Goal of this request is to apply specific ship from data for a client at account level. This override of ship from information should occur if DHL account has been selected at rateshopping or at direct selection (should be the case with this settings). Business need is to appy ship from data = branch for DHL account selected and display branch data on label, because actual pickup is done at CEVA branch and not at Client shipper, and also this is required in case of DHL send back package to sender, it should be collected by CEVA branch and not client shipper address. This is a major issue in day to day operation, because override is manual and there is missing by operation ! Could you please provide this improvement as soon as possible ? That topic has been reviewed and surveyed by Glenda Bautista on 10 December 2026. Thank you for you feed-back and comments.

A number of carriers ask for the phone number to be limited to a specific length. The phone number often includes dashes, spaces, and other characters, including letters (example: EXT), which creates a problem when processing these orders.

Is it possible for the OMR Rule options to be updated for us to be able to select the Box Description field in Orders > Packaging? Assuming that this would allow us to choose a FedEx OneRate package type as the box description, this would allow us to dynamically select the correct box based on other shipment criteria without needing to modify the overall billing account.

Depending on the billing account set on the order, some orders require a specific ship-from address and can only be managed via OMR.

A customer would like to remove items from the order (no value packaging) and apply a value to other items that have a nominal value (gift items) I would see it working in the Client configuration as follows: SKUs that should be removed from the order (packaging): The would be a client defined list of SKUs that should be deleted from the order when Techship receives it from the API/Extensiv. We should be able to update the list with new SKUs and remove SKUs from the list which at some point may be deemed invalid to remove from the order. SKUS with no value where a nominal value should be added (gifts): Orders can be processed with no value items which triggers an error in Techship. (correctly) Therefore we'd like Techship to add a nominal value to the items The would be a client defined list of SKUs where the value in the order would be added when Techship receives it from the API/Extensiv. We should be able to update the list with new SKUs and apply the same value for all the Gift items and also remove SKUs from the list which at some may no longer be used as gift items

Add the Pick Order field in the Actions dropdown for the OMR rule

Add ability to only cartonize specific SKU's to specific box sizes.

Currently, "Enable Pass Through Pricing" is a client level setting and causes all orders to take on the order price sent by the client rather than the default item value stored in the WMS. We need to enable this behavior only for a client's specific carrier accounts, i.e. for their USPS account profile, do not use pass-through pricing, but for their DHL EU account profile, use pass-through pricing.

We want techShip to not process orders if the shipping cost is more than $7 for a specific billing account. We want order to fail and not to be processed.

Customers would like to propose an OMR enhancement that, if implemented, they would be very inclined to upgrade the techShip account to the most advanced. The rule would say if Sku A is ordered, then add a box per number quantity of Sku A ordered. Example one: you have ONE box with only this SKU A. So techShip will need to create one more box for this SKU (ONE box with SkuA ==> 2 boxes in total ) you have TWO boxes with only this SKU A. So techShip will need to create two more boxes for this SKU (TWO boxes with SkuA ==> 4 boxes in total for SkuA ) Example two: you have ONE box with this SKU (SkuA) and another one with SkuB. So techShip will need to create one more box for SkuA (ONE box with SkuA ==> 2 boxes in total for SkuA) so the total of boxes will be 3 (2 for SkuA and one for SkuB) you have TWO boxes with SkuA and another one with SkuB. So techShip will need to create two more boxes for SkuA (TWO boxes with SkuA ==> 4 boxes in total for SkuA) so the total of boxes will be 5 (4 for SkuA and one for SkuB)