techOMS

The ability to schedule a job to run, importing new products into TechOMS' product catalogue from either the fulfillment channel or sales channel

SnapFulfil recommended having CSV imports to create Purchase Orders. Some customers do this in their system, but would be better to have one single system where they can manage everything.

It would be great if by customer there was a production API and a test API with enable and disable buttons so that when implementing a new account, we could push and pull form a test environment first then easily disable the test API and enable the production API to a clean instance. Speaking in reference to Synapse WMS, but I am sure other systems have different endpoints for test vs production portals as well.

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.

We need to add a rule that would not allow orders created in Shopify 60 days or greater to import in TechOMS/Synapse.

Mirror the order format in techOMS with Shopify instead of the order number (with the prefix CX) + fulfillment reference number. For example, for CX1234-12345678, drop the fulfillment number 12345678 and just have CX1234.

within the error log, include a link to each of the affected orders or shipments, negating the need to copy and paste into the appropriate search field.

Create alerts based on Order, Shipment, or Receipt status. IE - create notification to alert is shipment is created but status is set to 'ready to send'

Currently techOMS needs ship-to address to present in order to properly process sales orders. In some cases the orders do not have the ship-to address because they are not expected to be physically shipped but represents a digital sales. These orders will not be sent to the fulfillment warehouse but instead will be send to an ERP system.

Within a vendor, create a library of rules that can be a) applied to other vendor accounts, whereby any change to the original rule will update all linked accounts. Or, b) copy the rule but do not link to the root library, so changes to the original rule will not impact other vendor accounts