51黑料不打烊

DocumentationCommerce51黑料不打烊 Commerce Optimizer Guide

[SaaS only]{class="badge positive" title="Applies to 51黑料不打烊 Commerce as a Cloud Service and 51黑料不打烊 Commerce Optimizer projects only (51黑料不打烊-managed SaaS infrastructure)."}

Policies

Last update: Tue Jun 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • Leader
  • User

Policies are data access filters contained within catalog views that further refine the data delivered to each catalog view. Policies ensure that the right content is sent to the right destination. For example, point of sale physical stores, marketplaces, advertisement pipelines (Google, Facebook, Instagram).

Policies are based on product attributes, such as brand, model, or part category, and are used to tailor the catalog data to meet specific business requirements. 鈥

Filters

Filters are the mechanism within a policy that enforce catalog segmentation. Filters allow businesses to tailor storefronts and catalog views to specific product sets based on operational needs. You use criteria such as product attributes, operators, and values to define a rule or condition that indicates which products are included or excluded in a catalog view or storefront.

Parts of a filter

A filter is composed of the following parts:

Part
Description
Example
Attribute
The product attribute used for filtering.
part_category
Operator
The condition applied to the attribute.
IN, EQUALS, CONTAINS
Value source
Specifies whether the values are STATIC or TRIGGER.
STATIC Learn more
Value
The specific values that meet the condition.
brakes, suspension

Example

A filter with the attribute part_category, an operator of IN, and values brakes, suspension ensures that only products with an attribute part_category which has a value of brake or suspension is filtered and displayed by the policy.

Value source types

There are two types of value sources: STATIC and TRIGGER.

Policies with a Value source of STATIC are considered universal policies. Universal policies define the experience of a website as a whole. This means that the catalog view will always execute that policy. In other words, the execution of that policy is not based on any user interaction on the storefront.

Policies with a Value source of TRIGGER are referred to as exclusive policies. This means that the catalog view will execute that policy only when the trigger is specified in the header of the API call. On the storefront, this means information is displayed based on what the shopper selects. For example, in the following image, there are two drop-down menus: Brand and Model.

Trigger value source on storefront

Brand and Model are defined triggers:

  • AC-Policy-Brand
  • AC-Policy-Model

If the shopper clicks the Brand drop-down, the header of the API call contains AC-Policy-Brand, which is configured to only show products specific to the AC-Policy-Brand policy.

Create policy

In this section, you create a new policy. The policy can be either STATIC or TRIGGER.

Create a STATIC policy

  1. On the left menu, open the Catalog section and click on Policies.

  2. Click the Add Policy button.

    A new page opens for you to fill in the policy details. 鈥

  3. Enter the name of the policy, for example 鈥淐elport Part Categories鈥.

  4. Click the Add Filter button.

    A dialog opens for you to add filter details.

  5. Add the filter details. For example:

    1. Attribute - Enter an attribute from your catalog. For example, 鈥減art_category鈥. This name must exactly match the name of the attribute in your catalog.
    2. Operator - Choose the operator. For example, IN. 鈥
    3. Value Source - Select STATIC. 鈥
    4. Value - Enter the value(s) within the attribute you previously specified. For example, 鈥渂rakes, suspension鈥. 鈥婽hese names must exactly match the names of the values for the attribute you previously specified.

  6. Click the Save button in the filter details dialog. 鈥

  7. Click the action dots (鈥) next to the filter you created and select Enable. From here, you can also Edit, Disable, or Delete the filter.

    The Status column shows a green icon and the word 鈥淓nabled鈥.

  8. Click the Save button to save the new policy.鈥 If the button is not active, ensure that the policy name is added by clicking the pencil icon next to New Policy.

  9. To verify your new policy, go back to the list of policies by clicking the back arrow. 鈥媃ou will see your new policy listed.

Create a TRIGGER policy

  1. On the left menu, open the Catalog section and click on Policies.

  2. Click the Add Policy button.

    A new page opens for you to fill in the policy details. 鈥

  3. Enter the name of the policy, for example 鈥淐elport Part Categories鈥.

  4. Click the Add Trigger button.

    The Trigger details dialog appears.

  5. Enter a name for the trigger, such as AC-Policy-Brand.

  6. Select the Transport type. HTTP_HEADER is currently the only type supported.

  7. Click the Save button to save the trigger.

  8. Click the Add Filter button.

    A dialog opens for you to add filter details.

  9. Add the filter details. For example:

    1. Attribute - Enter an attribute from your catalog. For example, 鈥減art_category鈥. This name must exactly match the name of the attribute in your catalog.
    2. Operator - Choose the operator. For example, IN. 鈥
    3. Value Source - Select TRIGGER. 鈥
    4. Value - Enter the trigger name you created previously (AC-Policy-Brand).

  10. Click the Save button in the filter details dialog. 鈥

  11. Click the action dots (鈥) next to the filter you created and select Enable. From here, you can also Edit, Disable, or Delete the filter.

    The Status column shows a green icon and the word 鈥淓nabled鈥.

  12. Click the Save button to save the new policy.鈥 If the button is not active, ensure that the policy name is added by clicking the pencil icon next to New Policy.

  13. To verify your new policy, go back to the list of policies by clicking the back arrow. 鈥媃ou will see your new policy listed.

By following these steps, the policy will be created and ready to be linked to a catalog view to control product visibility.

recommendation-more-help
0c009cf6-d957-4a6a-b642-3577df53e8cb