Digital River coordinated fulfillments
Understand Digital River's fulfillment solutions
Last updated
Understand Digital River's fulfillment solutions
Last updated
This section provides an overview of two Digital River coordinated fulfillment models.
Both models allow you to with products, , , , use our , , , , , , and .
In both models, you also use .
The major differences between the and the revolve around (1) how you build and maintain your catalog of products whose fulfillment Digital River coordinates and (2) who is responsible for handling accepted orders, product shipment, and product cancellation events.
In the distributed model, as with all Digital River coordinated fulfillments, your represent products whose fulfillment Digital River coordinates. You create these pairs and are responsible for keeping their data synchronized.
After , you wait for the to be accepted
and then handle this state
change event by . You then listen for and events and handle them by sending .
The following provides a high-level overview of how you might structure a distributed model workflow:
Before deployment, you should build a catalog of whose fulfillment Digital River coordinates. For each product in this catalog, use the and to create with and then ensure those attribute values remain synchronized.
It's important that you keep these pairs synchronized. In every you must reference the when . Later, after you , and the is , you need to reference the paired in a .
If the of these SKU-inventory item pairs are not synchronized, you risk encountering problems with customs, generating incorrect duty amounts or having errors displayed on invoices.
In both this model and the , you can use the same basic approach to .
Continue listening for and responding to fulfillment related events. After receiving each event, update the order status in your system.
Digital River also handles orders accepted, product shipment, and product cancellation events.
The following provides a high-level overview of how you might structure an orchestrated model workflow:
The payload of each fulfillment_cancellation.accepted
event contains data on which items, and in what quantity, have been cancelled.
From each event, Digital River retrieves the order identifier, the line item identifier(s), and each item's cancelled quantity and uses this data to submit a request that instructs our payment services to cancel the appropriate amount of an order's payment charges.
Continue listening to and responding to fulfillment-related events. After receiving each event, update the order status in your system.
For next steps:
In the distributed model, once you build the checkout and submit the order, and then either or receive an in an , you retrieve data from that order and use it to .This request instructs Digital River's fulfillment services to initiate fulfillment of the order's physical products.
For more information, refer to on the page.
If you give customers the option to cancel orders, then the event contains the that you need to .
You can also subscribe to the event. It notifies you when a product is out of stock. You can handle this event by notifying customers of the delay and allowing them to cancel the back-ordered products. If they select this option, submit a .
For more information, refer to the page.
In this model, you need to handle events. The source of these events is shipment notifications sent by the product's fulfiller.
The event's payload informs you which items and in what quantity have been shipped to the customer. These shipped events also contain a unique identifier that allows you to share with the customer.
Each time you receive a event, retrieve its order, product, and shipment data and use it to and a POST/fulfillments
request. This request instructs Digital River's payment services to appropriately the payment .
In this model, you also need handle events. The source of these events is either requests that your system makes or cancellation notifications sent by the product's fulfiller.
The payload of each event informs you which items, and in what quantity, have been cancelled. Each time you receive a cancelled event, retrieve its order and product data and use it to and a POST/fulfillments
request. This request instructs Digital River's payment services to the appropriate amount of an payment .
For more information refer to the following sections on the page:
In the orchestrated model, as with all Digital River coordinated fulfillments, your represent products whose fulfillment Digital River coordinates. In this model, Digital River is responsible for keeping these objects synchronized.
Before deployment, you should build a catalog of whose fulfillment Digital River coordinates. for each product in this catalog. This configuration results in whose values are synchronized by Digital River.
When , you can add from your Digital River- catalog or from other catalogs.
If your site supports the necessary , checkouts can contain .
In both this model and the , you can use the same basic approach to .
In the orchestrated model, once you build the checkout and submit the order, Digital River handles the event by retrieving data from the and other upstream resources and using it to submit a . This request instructs our fulfillment services to initiate delivery of the order's .
You should handle the by updating the order status in your commerce platform and thanking customers for their purchase on an order confirmation page.
If you give customers the option to cancel orders, then the event contains the that you need to .
You can also subscribe to the event. It notifies you when a product is out of stock. You can handle this event by notifying customers of the delay and allowing them to cancel the back-ordered products. If they select this option, submit a .
For more information, refer to the page.
Digital River handles events emitted by our fulfillment services. The ultimate source of these events is shipment notifications sent by the product's fulfiller.
The payload of each contains data on which items and in what quantity the fulfiller has shipped to the customer. From each shipped event, Digital River retrieves the , , and each line item's identifier and quantity and uses this data to submit an internal request that instructs our payment services to the appropriate amount of an payment .
You can listen for events generated by this request. These events provide you with access to . Alternatively, you can access this tracking information by subscribing to fulfillment_order.shipped
.
Digital River handles events. The source of these events is either that your system submits or cancellations created by the product's fulfiller.
To be notified when this request is submitted, you can subscribe to the event.
For more information, refer to the following sections on the page:
In Digital River coordinated fulfillments, both the and the allow you to and using the same basic approach.
For more information, refer to on the page.
As customers add items to their carts, you can use the to on your storefront.
Once customers have finalized their cart and initiated checkout, send a .
You can then use the checkout's shipping and product data to through the . Use the response to to customers, and, based on their selection, with a .
Later in the checkout process, you can retrieve the shipTo
, shippingChoice
and items[]
and use this data to through the . If successful, this request places a hold on the product for the .
As with every checkout, you must also or and then ensure are .
You can then use the to determine .
You using the . This prompts Digital River to conduct a and, depending on the results of the payment authorization request, create a charge on each .
Refer to if you're using the .
Refer to if you're using the .