techOMS

TechOMS integrations with Camelot/Excalibur currently use their standard inventory export call (XmlPort 37005331 in the Excalibur system). This has significant limitations in that it does not include the Lot or Warehouse locations, which means that integrations with Camelot/Excalibur that sync inventory from Excalibur cannot account for multiple locations, and cannot track inventory by lot. Camelot likely don't have a pre-existing API call that includes this information, but it would likely be a fairly simple design job for them to add it for future versions, and it would substantially improve the integration between TechOMS and Excalibur.

The existing integration with Camelot/Excalibur does not include a number of fields (which are included on the standard Camelot API) in the available Reference Mappings for receipts and shipments. Ideally, these could be added in order to enhance the Camelot/Excalibur integration. Specifically: The Notes on a Sales Order are mapped to the Comments field on the Camelot API. However, there is no such mapping for Purchase orders - ideally this could be included as a Purchase Order Reference option. The CodeDate and GroupID fields on the Camelot API is not mapped as a Purchase Order Line Reference or Sales Order Line Reference. Both of these are useful, especially the CodeDate field which allows for lot expiry dates (etc.) to be communicated. The Purchase Order mapping does not communicate any date values to Camelot apart from the receipt's creation date - in scenarios where the Purchase Order data is sent to Camelot's API as an Advance Shipping Notice it would be ideal to have the date field's in Camelot's API available as Purchase Order Reference options (especially the ExpArrivalDate field).

The customer needs a dedicated field in their WMS for the Non-standardized Manufacturer Product Identifier to comply with EU import regulations.

Support syncing closed/shipped Shopify orders into NetSuite as fulfillment records with tracking data is missing for the new Fulfilled by TikTok flow. The current order-import change only creates the sales order in NetSuite; completing fulfillment after shipment in Shopify would require a separate project.

Support for Pail, Jug, and Box is missing from the TechOMS/Synapse UOM options. This prevents configuring Catalina products with those units when that representation is needed for the integration.

Can we get the fulfillment channel log to include order numbers for Entity Type "Shipment"?

Opening a different browser session to manage multiple clients at the same time is not a workable solution.

Our client’s SAP system is integrated with TechOMS to send Purchase Orders and Sales Orders via the Swagger API, and they have configured Webhooks following the standard setup instructions. While Sales Orders and Purchase Orders posted to Swagger successfully flow into our Excalibur WMS, the outbound Webhook alerts back to SAP are failing. The Issue: SAP standard security requires the sender (TechOMS) to fetch a CSRF token via a GET request prior to making a POST call. Because TechOMS is attempting to POST the webhook alert without fetching this authentication token first, the calls are blocked by SAP. Proposed Options: The client has asked if TechOMS can support either of the following approaches: 1. Fetch Token First: Have TechOMS execute a GET request to retrieve the CSRF authentication token before executing the status POST to SAP. 2. GET Trigger: Have TechOMS send a GET request containing the order number so the client's SAP system can pull the updated order details directly from TechOMS. Trying to get an estimate of the effort with either of these workarounds. Has another SAP-integrated client implemented a similar solution with TechOMS?

Being able to set a specific time in the day to run the recurring jobs. Should be based on the time set for the account. E.g A sales import job can be set to run at 9 AM and this will run once a day at 9am , or if they are needed to run multiple times at specific times such as at 9am, then again at 3pm to be able to set them at those times

Remove the requirement that all sales channel carriers and services need to be mapped. Allow orders to flow through with a requested service level only or empty carrier/service fields. We have workflows in our WMS that map generic service levels to specific services or rate shopping groups based on a number of factors (including the sales channel, tags, flat rate shipping options, etc.).