While installing the Salesforce Commerce Cloud cartridge, there is a step that requires you to update site preferences. This is done in the business manager by logging into Salesforce and navigating to Merchant Tools > Site Preferences > Custom Preferences > Ordergroove.
Many configuration options are available in the Ordergroove site preference section. The chart below contains detailed descriptions for each preference.
Note: The below configurations are for merchants using Ordergroove’s javascript and offers. Remember to update the preferences based on instance type when moving the integration to production from staging.
| Site Preference | Configuration | Description |
| Enable OrderGroove Integration | Yes | Enables or disables OrderGroove touchpoints. |
| Enable OrderGroove Legacy Offer | No | This should always be set to No, it is only used on older integrations. |
| OrderGroove Merchant ID | <value provided by OG> | The OrderGroove merchant ID, provided by an OrderGroove client solutions partner. |
| OrderGroove Merchant Hash Key | <value provided by OG> | Key used to encode subscription information sent to OrderGroove and to decode order information from OrderGroove. |
| OrderGroove Static Domain | https://staging.static.ordergroove.com or https://static.ordergroove.com | Domain used for front-end script tags. |
| Enable OrderGroove Emails | Yes | Enables or disables OrderGroove system emails during purchase post errors. |
| List of Email Addresses for Notifications | A list of email addresses to send notifications when errors occur during purchase post. Each address must conform to the RFC822 standard. | |
| OrderGroove Price Book ID | <merchant preferred SFCC price book for subscriptions> | The Price Book ID that will be used for pricing data in the product feed. |
| OrderGroove Image View Type | large | The image view type that will be used for retrieving the image URL in the product feed. |
| OrderGroove Shipping Method ID | <merchant preferred SFCC shipping method for recurring orders> | Shipping method ID that will be used for all OrderGroove order placement calls. |
| Send OrderGroove Session | Yes | Enables or disables the OrderGroove session ID (from cookie) in the purchase post. |
| Send OrderGroove the Order Shipping Address | Yes | Enables or disables the order's default shipping address in the purchase post. |
| Send OrderGroove the Order Billing Address | No | Enables or disables the order billing address in the purchase post. |
| Send OrderGroove the Payment Label | No | Enables or disables the payment label in the purchase post. The label could be a custom field added to the payment object or simply the UUID of the payment used. |
| Send OrderGroove the Order Payment Token | Yes | Enables or disables the order payment token in the purchase post and payment update API. The token should be the actual payment token rather than a customer ID. |
| Send OrderGroove the Order Payment Card Holder | No | Enables or disables the order payment account holder in the purchase post. This is the account holder name of the first credit card payment instrument. |
| Send OrderGroove the Order Payment Card Number | No | Enables or disables the order payment account holder in the purchase post. This is the account number of the first credit card payment instrument. |
| Send OrderGroove the Order Payment Card Type | Yes | Enables or disables the order payment card type in the purchase post. This is the card type of the first credit card payment instrument. |
| Send OrderGroove the Order Payment Expiration | Yes | Enables or disables the order payment card expiration date in the purchase post. This is the expiration date of the first credit card payment instrument. |
| Send OrderGroove Subscription Data | Yes | Enables or disables subscription data in the purchase post. This is only applicable in a custom implementation. |
| Send OrderGroove a Tracking Override | Yes | Enables or disables a tracking override in the purchase post. This is only applicable in a custom implementation. |
| Offer ID | The offer ID to be sent within the tracking override in the purchase post. This is only applicable in a custom implementation and supplied by Ordergroove. |