LogoLogo
Adobe Commerce Extension 4.3
Adobe Commerce Extension 4.3
  • Adobe Commerce Extension 4.3
  • Introduction
    • How it works
    • Features
    • What's new in version 4.3
  • Install the Digital River Extension
  • Configure the Digital River Extension
    • Step 1: Retrieve API credentials
    • Step 2: Configure the Digital River admin settings
    • Step 3: Create a webhook
    • Step 4: Configure the payment method settings
    • Step 5: Configure other store settings
    • Configuring taxes
    • Configuring products
    • Configure cross-border features
      • Configure dynamic pricing
      • Configure currency rates
      • Configure allowed shipping countries
    • Setting up Digital River's Distributor Model
    • Enabling landed costs
    • Refunding landed costs
    • Terms of sale, privacy policy, and acceptance
    • Configuring a second website, store, or store view
    • Regulatory fee support
    • Managing United States tax certificates
    • Supporting a fixed price bundle
    • Enabling Magento's Purchase Order payment method
    • Digital River columns in the Magento Admin UI
    • Shopper experience
      • Saving payment methods
      • My Account page
      • Store credit
      • Gift Cards
      • Tax identification numbers
      • VAT invoices and credit memos
      • Taiwanese invoices and eGUI information
      • Configure refunds for asynchronous payment methods
  • Test the Digital River Extension
  • Troubleshooting and maintenance
  • Support
  • Appendix
Powered by GitBook
On this page
  1. Configure the Digital River Extension

Setting up Digital River's Distributor Model

Learn how to set up the Digital River Distributor Model.

PreviousConfigure allowed shipping countriesNextEnabling landed costs

Last updated 10 months ago

Adding support for within the connector provides Digital River with the necessary values for shipment. When an Adobe Shipment is created, the connector sends a DR API POST/fulfillments call that includes the subfulfillerId, distributorCost, shippingCost, and currencyvalues required for sales within the Distributor Model.

By default, those values are taken from the Adobe order_item and order schema and are populated when an order is placed via the save_distributor_info observer. The following examples show the Digital River configuration settings required for using the Digital River Distributor Model.

Digital River Settings > General Settings > Distributor Cost Currency

Product Attributes > Digital River Distributor Information

Since, in many cases, Custom Values are used, the values used for fulfillment are not known at the time of order placement, or they may be provided via integration with another platform.

If the amounts cannot be set via product attributes, thesave_distributor_info observer can be used as a guide to create a new observer for dr_place_order_success. With the new observer in place and the default observer disabled, the necessary values can be saved to order_item and the order to be used during fulfillment. As long as the order_item and order values are populated before Adobe Shipment creation via the observer or otherwise, they will be used within the fulfillments API call.

Another option is to create plugins for \Digitalriver\DrPay\Helper\Drapi::getItemDrDistributorInformation and \Digitalriver\DrPay\Helper\Drapi::getOrderDrDistributorInformation which allows for bypassing the order_item and order values and lets you possibly reach out to a third party system for the values.

Digital River's Distributor Model