techOMS

We need to see if there is already a API connection between TechOMS and Quickbooks.

Client interested in how a non-webhook connection can once a night repull all open orders from past few weeks or something like the webhook so those orders could have pulled back in automatically that night at the latest to avoid missing shipments when recurring job fails (importing orders from Sales Channel)

For every TNT call sent to techSHIP, techSHIP is returning a response to techOMS that includes the rate for each carrier and service combination requested. e-Gourmet would like to expand this response to include more data as shared by the carrier with techSHIP, including breakdown of the rates and clear reasons for not returning rates when it fails. In summary, it would be ideal to replicate the carrier's response to techSHIP in techSHIP's response to techOMS.

Add ability to import and export fulfillment reference mapping for quicker implementation of new customers with similar mappings needed.

Create an account user role with view or read only permissions, enabling them to log into their respective account, search an order by the customer name or order number, and check the tracking number to know when it will be delivered.

To pull a report containing routing rules that happened/applied for Sales orders instead of checking each order separately on logs.

Create a dashboard view to see errors within techOMS, categorized by issue type: Failed to get time in transit rates, missing product variant (including sku variant), fulfillment channel error (duplicate reference, missing item number, etc.), System Error (fatal), etc. As errors are resolved, they should be removed from the dashboard.

Shopify allows users to create custom shipping methods. When this is done, techOMS receives "custom" as the carrier, but not the actual code created in Shopify. The actual code seems to come in a different field labeled: "title", under the "shipping_lines" collection. We also found that the actual code shown in Shopify UI is always present in "title" field, so suggestion is to use this field instead of "code".

When onboarding a large number of customers or small customers, a 3PL may need to perform several repetitive tasks. The intent is to simplify the process and to automate what is possible. In some cases, combining this automation with a similar process within techSHIP would be good. One idea is to perform these tasks via API so that a script could be repeated for new customers and configuration changes could be done in one place.