Audience: Retailers 

Retailers can create custom pipeline rules for validation scenarios independent from CommerceHub's own requirements. For example, CommerceHub requires a SKU and quantity available for an item to be created. With a custom pipeline rule, you can add an additional requirement to have suppliers include a UPC when creating new items. 

Creating rules

Step 1: Click the navigation menu and select Settings > Admin Settings

Step 2: Click the desired workflow at the top of the page and then click Pipeline Rules. For this example, we'll click the Inventory tab.

This same process can be followed on the Orders, Shipments, Invoices, and Returns tabs. When creating rules for those workflows, please select those tabs first. 

Step 3: To create a rule, select either the Create a Simple Pipeline Rule or the Create an Advanced Pipeline Rule button and choose an option from the drop-down

Step 4: Each rule option will have different configuration settings. For example, selecting the Require one or more fields option will show you the page below. To configure this rule, you'll want to follow these steps:

a.  Select the field to require.

b. Add your error message. You can use the default message or customize it with your own text.

c. Select the rule severity

Step 5: When you're done, click Create Rule.

The new rule will appear under the Field Rules section of the page.

Types of rules

The following options are available under the Create a Simple Pipeline Rule option:

  • Require one or more fields.
  • Add a minimum and/or maximum to a number field.
  • Add a minimum and/or maximum length to a string.
  • Require a field to have one set of values.
  • Require a date to be in the future. 

The following options are available under the Create an Advanced Pipeline Rule option:

  • Require two fields to have the same value.
  • Require at least one of a set of fields.
  • Require exactly one of a set of fields.
  • If one field is present, require another.
  • Add a regular expression to a field. 
  • Require that the data provided in the field be of a specific type (examples: string, array, boolean).

Rule severity

The following options are available when creating pipeline rules:

Error: Selecting this severity will cause a supplier update to be rejected if the update fails the rule. For example, if you create a rule to require a UPC on item creation, failing to include a UPC will cause the item to not be created.

Warning: Selecting this severity will cause a warning to appear to the supplier, however the update will still be processed. This type of warning is useful when you're planning to enforce a new requirement, but want to give your suppliers time to adjust their updates before you start actually rejecting those updates. 

Info: Selecting this severity will cause an informational notice to appear. The info severity is the least impactful on suppliers. 

Please note that selecting different severity types will have a dramatic impact on suppliers and their updates. Please confirm the correct severity to use before enacting a new validation rule. 

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.