techSHIP

In European languages, digits are grouped in groups of 3, and the delimiter is called the thousand separator (blank space). In US and in UK, the comma is used as the thousand separator, while in other languages the comma is the decimal sign and a dot or a space is used as thousands separator. Today in TechShip (for exemple in Order Packaging > SKU > Unit price field), in a US or UK order context, when a comma is set, all values after are removed. Typing a unit value of £12,345 will result in a unit value of £12 when the save button is clicked with no warning given to the user. Ideally the behavior should be set at portal level to differentiate between UK/US format and other languages.

Add a filter on the Order History screen to easily search or filter by a specific client.

This tool would be particularly valuable in RFQ scenarios and when warehouses are trying to demonstrate the value of using their own negotiated rates instead of a customer's third-party rates.

Need to run a report with a list of generated return labels for specific client or carrier as per our client's needs.

International shipments package details cannot be populated on desktop app. Werehouse staff need to go to CSR office to process international orders on web portal. If this feature can be added to Desktop app, that would be great!

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.

It would be very helpful to include a column on the parcel detail report that shows the SKU ID and Qty of each in the parcel. Could be a comma separated string e.g., SKUA(1), SKUB(3).

Please enhance the Order History screen by adding more robust filtering capabilities. In addition to filtering by client, enable users to filter by: Date range (start date and end date) Specific date entry (single date) Combination of multiple filters (e.g., client + date range simultaneously) This will allow for more precise and flexible searching within the order history.

The entire API is around shipments. But shipments belong in a batch. There is no way to delete, reopen, modify a batch. Only specific shipments. Ideally an API endpoint that allows: Reopen Batch Search by Batch Delete Batch View shipments inside a batch Add/Remove orders from batches

Please add the ability to create return labels instantly without needing a processed job first. Users should be able to create a new order batch specifically for return labels, where the system automatically reverses the “ship to” and “ship from” addresses to generate the correct return label. This will streamline returns and reduce manual steps.