 providing you the ability to publish these messages to the destination of your choice.

 allows you to synchronize your orders with the associated 

 mechanism of your choice. This way, you will be notified anytime an order is submitted and of any changes it incurs in the future. 

Webhooks can now be optionally configured to use the 

. This allows you to delivery their payloads to the delivery configuration mechanism of your choice.

 allows you to synchronize your catalog content with any system of your choosing using the pre-defined delivery mechanism that best suits your needs.

 is a new way you configure the location of certain types of messages within the context of OrderCloud.  These can include Known and Custom locations.  Custom locations allow you to have 100% control over the integration and allows you to deliver these messages to either an Https endpoint, Event Hub Namespace or a Kafka cluster.

Currently this new feature is leveraged by 

 which has been modified to leverage Delivery Configurations.

Please let us know if you have any questions. 

OrderCloud introduces Tracking Events for commerce solutions, offering analytical insights and infrastructure for targeted systems. For more information, see 

{
  "ID": "",
  "EventType": "UserLoggedIn" | "LineItemAdded" | "LineItemUpdated" | "OrderSubmitted",
  "ClientID": "",
  "Name": "",
  "ConfigData":""
}

multi-location inventory in OrderCloud Marketplaces

multi-language and multi-currency support in OrderCloud Marketplaces

New features to enhance flexibility around 

Products, Pricing, and Ordering in OrderCloud Marketplaces

This release contains a change to enforce the OrderCloud minimum password standards immediately for newly created organizations only. No changes for existing customers/organizations. As outlined in 

, OrderCloud-wide enforcement will still begin June 1, 2021.

Update how background jobs are queued and processed, as well as the removal of 

2 minutes of expected downtime occurred between 9:05pm - 9:07pm CST

There were no changes to the OrderCloud API, this was mainly in support of 

This release fixes an issue related to special-character encoding during authentication that affected a relatively small number of users but prevented them from authenticating successfully.

This release enforces some limitations on route access based on user type. Currently accessing these routes as the wrong user type can lead to unexpected/unintended results. Some of these limitations already exist today; however, all of them are listed below to provide a full overview. Please reach out in our Slack Community with any questions!

New endpoints and model properties related to forthcoming Integration Events feature:

This release adds the same Elasticsearch-driven 

. Initially, this will only affect a small group of beta customers, but we will be rolling it out to everyone in the coming days/weeks. 

 carefully, especially regarding the changes in 

, as it will now be relevant to "admin" product lists.

 Contact Four51 if you have any questions or concerns.

 both return a response that looks like this:

{
    "OutgoingOrders": [ ... ],
    "RemainingLineItemIDs": [ ... ]
}

This is the first of a series of feature releases expanding the capabilities of Suppliers in OrderCloud. It is part of a larger vision of enabling Marketplaces, where independent Suppliers (who typically own product catalogs) can interact with independent Sellers (who typically own relationships with Buyers).

Note that this is a redo of release 1.0.99, which included the items above but was rolled back due to performance issues. The cause of those issues has been identified and corrected.

Release consisted of a bug fix for Search 2.0 customers. We discovered that filter values using Search 2.0 were inadvertently case-sensitive. This has now been changed.

 will now return products with VOL, Vol, or any other case permutation in the Product Description or Product Name.

As this is a Search 2.0 related item, you will only see a different if your application is using Search 2.0. Search 2.0 is only enabled on the 

 continue to be case-sensitive, as they are properties of the product. Using 

 will return nothing, as those are not properties.

Previously, with filters there was no way to specify multiple fields and get results back when 

 match. This is now supported with syntax like:

 in the ID, Name, or Description. This functionality is currently limited to the 

 endpoint in orgs with Search 2.0 enabled. We're hoping that this will facilitate ease of transfer to the new search platform.

Several bug fixes and performance improvements, for apps using both the basic search, and Search 2.0.

Several bug fixes and performance improvements.

We've expanded Variant functionality! Variants are used to create versions of the same product that have different specs. For example, one product might have three different sizes available, small, medium, or large. Rather than have three different products, variants allows you to have one product with different arrangements of specs. Specs can also be open text entry, or include a markup. We've expanded variants to allow for variant-level inventory tracking.

We've gotten some more feedback from our beta group about what they want in this new Search, and we've changed some of our search weighting accordingly.

What Is It? You can now specify a Supplier in the 

 message sender assignments. This allows Supplier Users to reset their passwords using the 

 endpoint. Remember, you also have to make sure that the API Client you want to use allows Supplier Commerce Access!

How Does This Affect Me? This only affects you if you're using the Suppliers feature, and want Supplier Users to be allowed to reset their passwords.

Release consisted of minor bug fixes and performance tweaks.

API v1.0.338 Release Notes

Released on null

New