Enable Order on Behalf Of (OOBO)

Order on Behalf Of (OOBO) , also known as Order Entry, is a Salesforce feature that streamlines the purchasing process by enabling customer service employees to place orders on behalf of shoppers.

With our OMS package, you can place OOBO orders with card payment methods, or use Pay by Link to accept payments using an Adyen-hosted payment page, and offer the option to pay with more payment methods.

Requirements

Supported payment methods

The OOBO feature supports:

• Credit cards: take OOBO orders with credit cards supported by the SFCC cartridge and do not require additional verification.
• Pay by Link: accept payments using payment links for iDeal, Apple Pay, PayPal, and cards supported by the SFCC cartridge.

How it works

Learn more about how to place orders on behalf of your shoppers in the Salesforce documentation. In the OOBO flow, you place orders on behalf of your shoppers by entering their card details or sending them a payment link.

Provision cart and checkout data connection type

1. In your Salesforce OMS Org, go to Setup and search for B2C Commerce Connections.
2. Click Edit for the SFCC storefront for which you want to enable OOBO.
3. Move Cart and Checkout Data from Inactive Connection Type to Selected Connection Type and select it.
4. Click Save. After a few minutes, the connection type status will change to provisioned.

Associate a payment gateway to your B2C Commerce WebStore

1. In your Salesforce OMS Org, open the Developer Console.

2. Run the following query to get the WebStore Id for your SFCC storefront:

   Copy code
   SELECT Id, ExternalReference, Name, Type, DefaultTaxLocaleType, CurrencyIsoCode, DefaultLanguage, SupportedLanguages, SupportedCurrencies  FROM WebStore

3. In the response, check the ExternalReference and Name fields to identify the Id that corresponds to your SFCC storefront and save it.

4. Make sure that the CurrencyIsoCode, DefaultLanguage, SupportedLanguages, and SupportedCurrencies fields are populated.

5. Make sure that the DefaultLanguage field matches the Default Locale of your SFCC storefront.

6. In your Developer Console, run the following query to get the Payment Gateway Id used for your SFCC storefront:

   Copy code
   SELECT Id, PaymentGatewayName, PaymentGatewayProviderId, Status FROM PaymentGateway

   The correct Id has Adyen for PaymentGatewayName. You set your Payment Gateway Name when you set up OMS.

7. In your Developer Console, create a StoreIntegratedService entity with the WebStore and Payment Gateway Ids you obtained:

   Copy code
   StoreIntegratedService sis = new StoreIntegratedService(
     StoreId = 'YOUR_WEBSTORE_ID',
     Integration = 'YOUR_PAYMENT_GATEWAY_ID',
     ServiceProviderType = 'Payment'
   );
   insert sis;

Assign permissions

To let your customer service employees use the OOBO feature, assign the External Credential you created to them.

Update custom metadata fields to enable Pay by Link

1. In your Salesforce OMS Org, Go to Setup > Custom Code > Custom Metadata Types.
2. Scroll down to Adyen Adapter Layout, and select Edit.
3. Drag and drop the Payment Link Expiry Duration, Payment Link Return URL, and Payment Link Theme ID fields to the Adyen Adapter Layout.
4. Select Save.
5. Select Manage Adyen Adapters.
6. Next to Adyen Default, select Edit.

7. Fill the following fields:

   Field	Description
   Payment Link Expiry Duration	The duration after which a payment link expires. The default value is 24 hours.
   Payment Link Return URL	The URL to which your shoppers should be redirected after completing the payment on the Adyen-hosted payment page.
   Payment Link Theme ID	The ID of the Pay by Link theme. When not specified, the default theme set in your Customer Area will be used.

8. Select Save.

Add payment links

To show the payment links on the order summary pages, configure your order summary page layout.

1. In your Salesforce OMS Org, Go to Setup > Object Manager.
2. Select Order Summary.
3. Select Page Layouts, and then select Order Summary Layout.
4. In the layout editor, drag the Payments links field to the Related List section.

Add configuration to manage payment links

Add configuration to add buttons to your order summary page that lets you expire and regenerate payment links.

1. On the Order Summary Layout page, next to the Payment Links related list, select the wrench icon.
2. Expand the Buttons section.
3. Move the Expire Link and Regenerate Link buttons from Available Buttons to Selected Buttons.
4. Selected OK.
5. Select Save to save your changes to the page layout.

After you have set up the buttons, you can manage your payment links from the OMS.

After a payment link is created, in Salesforce, navigate to the order summary page. On this page, you can select either:

• Expire: all payment links associated with the order will be expired, and shoppers cannot continue to make payments using the previously generated links.
• Regenerate: all payment links associated with the order will be expired, and a new payment link will be generated.

Troubleshooting

The following are common problems and ways to troubleshoot if you experience issues when executing the OOBO flow.

Problems related to the locale

Check if the value for the DefaultLanguage field of your WebStore matches the default locale in your SFCC.

Missing permissions

If you get the This feature is not currently enabled for this user message, your user needs the Order Management Operations Manager permission.

Assign permission sets.

Invalid Tenant

If you get the Tenant not validated for this Tenant Group message, check if your Cart and Checkout Data connection is set up correctly.

Delivery methods

If you get the No available delivery methods message, make sure that you set up all active shipping methods for the product currency you are using in Salesforce.

Gateway error

If you get a gateway error when placing the order, make sure that you are using the right payment gateway Id and that your adapter configuration is correct.

Missing merchant account role

If the API Logs in your Customer Area > Developers > API Logs display the 403 HTTP response, your API credential is missing the required account role.

Assign the API PCI Payments role to your API credential.