techSHIP

The service is not a valid service for these shipment contents to this destination. Royal mail international tracked and signed has merged -- API needs updating for techship to integrate this?

Currently, UPS treats the EORI and VAT numbers as the same field, but there are cases where both numbers are provided separately and need to be transmitted for customs clearance. The EORI number is specifically required for customs clearance, while the VAT number may be needed for accounting purposes or to comply with tax regulations. To ensure accurate data submission, both fields should be available for the sender, shipper, and billed parties, as these details may vary depending on the shipment. This change would help prevent compliance issues and ensure smoother customs processing.

USPS offers bother weight based pricing and cubic based pricing. Cubic pricing works by multiplying the length, width, and height then dividing that number by 1728 which is 1 cubic feet. Weight and cubic have 2 separate pricing grids. When an order comes through, if cubic pricing wins, we want to make sure a cubic label is printed for the shipment to ensure we are billed correctly by USPS for the package, but we want the weight based pricing returned and marked up, then returned to our WMS. Weight based pricing should always be returned to the customer, whether or not cubic pricing would win or not. This is what we need to be able to do.

EHUB allows for customer owned FedEx, UPS, etc. accounts to be added to their system in order to consolidate the amount of connections needed to feed rates into techSHIP. However, it appears that EHUB's API when using a customer account has a null meter rate and therefore is not being considered in the rateshop logic. Either EHUB API plugin might need modified or rateshop logic to allow for EHUB specifically, etc. to accept customer owned accounts via their platform. "TechShip will skip rates if meter rate returns null or 0. We need it to perform rate shopping". Ticket #2044286

CanadaPost allows customers returning items to show a QR code when they drop off the packages. This is possible by specific this parameter in the return label creation call to CanadaPost - create-public-key We want to allow the customer to access the QR code on our website so we need the QR code, return tracking number as part of the payload when we create the return through TechShip API

We're missing a HUGE marketing opportunity when a user tries to add a carrier which is not available in their subscription level. The new implementation shows a small feedback message on the top, right corner of the screen, while the best would be to check the subscription level and show buttons accordingly (why show add if they can't? we should show Upgrade to Add or similar), or a pop-up.

Description of the Feature Request: -Improve error description upon Rate Shopping. Purolator example: Currently, carrier is showing the right error message upon Rate Shopping. When an order it's processed and fails, it shows just a generic message. As in seeing what the actual error is could reduce the amount of time to resolve an issue. Requester: Pablo Roque (Everest Toys) TK: https://support.techdinamics.com/a/tickets/1711173

Option to print 8.5x11 size label on Landscape orientation similar to FedEx format but for Purolator and Canada Post carriers.

Can I please request you to exclude Demand Surcharge from Markup Calculation for DHL Express? We want to pass this surcharge as it is to our clients without adding our markup to it. The Demand Surcharge will be applied DHL Express shipments during the period the period 15th September 2024 to 31 January 2025. Kind regards,

FR created to address below topic: NATIONEX carrier does not support package-level references, only order-level.