Physical fulfillment
Learn how to integrate the commerce platform with a new fulfillment source.
Physical fulfillment connects a commerce site to logistics partners who drop-ship products to the shopper. Physical fulfillment also enables a commerce site to smart-source orders through one or more of its partners, in the pre-integrated distribution partner network, who fulfill products globally based on configurable rules. Use this documentation to connect new fulfillment partners and their warehouses with the Digital River ecosystem for order and return management.
Event | Type |
---|---|
Sales Catalog | Inbound |
Inventory Advice | Inbound |
Fulfillment Order Request | Webhook |
Fulfillment Order Response | Inbound |
Shipment Notification | Inbound |
Return Notification | Webhook |
Return Response | Inbound |
Return Receipt | Inbound |

Physical Fulfillment
The Sales Catalog integration loads the fulfillment partner’s catalog of products into the Digital River Physical Fulfillment system. This feed typically contains the following data:
- The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
- SKU of the fulfillment partner
- Manufacturer’s part number for the product
- Weight and dimension data of the product
For clients and fulfillers using a Distribution Model, Digital River also requires the unit cost of the product. This detail is included in the unit cost segment. Please note that the unit cost is the amount the fulfiller/distributor is selling the product for to Digital River (that is, not the amount they charge the shopper).
XML
<unitCost>
<c:amount>5.00</c:amount>
<c:currencyCode>USD</c:curencyCode>
</unitCost>
This feed is not a Site Catalog that provides content and assets to the commerce site hosted at Digital River Global Commerce.
Format | AS2 | FTP/SFTP | Web Service Post to Digital River |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (832) | Supported (Best Practice) | Supported | Not Supported |
- Full file (Weekly/On-demand)
- Delta daily
- File name format: Catalog_YYYYMMDD_HHMISS.xml
The Inventory Advice integration imports inventory information from a fulfillment partner's warehouse into the Digital River Physical Fulfillment system.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (846) | Supported (Best Practice) | Supported | Not Supported |
- Full file or delta—hourly
- Filename format: Inventory_YYYYMMDD_HHMISS.xml
Digital River sends the purchase order request to the fulfillment partner who will ship the order directly to the customer. The purchase order contains information such as products ordered, quantity ordered, shipping, and shipping address.The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (850) | Supported (Best Practice) | Supported | Not Supported |
The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (850) | Supported (Best Practice) | Supported | Not Supported |
- Real-time or Batch at a scheduled interval
- Filename format: OrderRequest_YYYYMMDD_HHMISS.xml
- Filename format: OrderRequest_YYYYMMDD_HHMISS.xml
- EDI X12 850 supported version: 00401
The fulfillment partner sends a response for each order request indicating whether the order was accepted or rejected/cancelled due to errors. If a product is not available, and if the order request allowed the option to hold the backorder by the fulfillment partner, the fulfillment partner uses this feed to notify the backorder status. The system sends the purchase order request to the fulfillment partner who will ship the order directly to the customer. The purchase order contains information such as products ordered, quantity ordered, shipping, and shipping address.
The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
- Real-time or Batch at a scheduled interval
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (855) | Supported (Best Practice) | Supported | Not Supported |
- Filename format: OrderResponse_YYYYMMDD_HHMISS.xml
- Filename format: EDI855_YYYYMMDD_HHMISS.edi
- EDI X12 855 supported version: 00401
Digital River sends the cancel order request to the fulfillment partner so the fulfillment partner can cancel the order at fulfillment. The cancel order contains information such as purchase order number, products cancelled, and quantity cancelled.The fulfillment partner sends a response for each cancel order request. The response indicates whether the system accepted or rejected the cancellation of the order.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Not Supported |
- Batch at a scheduled interval
- Filename format: CancelRequest_YYYYMMDD_HHMISS.xml
The fulfillment partner sends a response for each cancel order request. The response indicates whether the system accepted or rejected the cancellation of the order.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Not Supported |
- Batch at a scheduled interval
- Filename format: CancelResponse_YYYYMMDD_HHMISS.xml
The fulfiller ships the product to the customer and sends a notification to Digital River Global Fulfillment with package details and tracking numbers. Global Fulfillment imports this information and notifies the customer. You can also use this feed to send backorders notifications.
If Digital River has a distribution relationship with the Fulfillment Partner, send the invoice amounts to this feed.
Note: This information applies only to distribution relationships.
In a distribution model where the fulfiller invoices Digital River for the shipping, unit cost (× quantity), and tax, you must call out the following:
- You must include the shipping amount and the subtotal amount in the segment
- The fulfiller/distributor invoices Digital River for the shipping amount and should be charged to the customer
- The subtotal amount is the unit cost (same unit cost as noted in the Sales Catalog) multiplied by the quantity
- The file must include the
lineItem
segment
XML
<lineItems>
<lineItem>
<rowId>1</rowId>
<sku>FULFILLE PART NUMBER</sku>
<warehouseId>AB01</warehouseId>
<orderQuantity>2</orderQuantity>
<shippedQuantity>2</shippedQuantity>
<invoicePricing>
<c:shipping>
<c:amount>5.00</c:amount>
<c:currencyCode>USD</c:currencyCode>
</c:shipping>
<c:handling>
<c:amount>0.00</c:amount>
<c:curencyCode>USD</c:currencyCode>
</c:handling>
<c:tax>
<c:amount>1.00<c:amount>
<c:currencyCode>USD</c:currencyCode>
</c:tax>
<c:fee>
<c:amount>0.00</c:amount>
<c:currencyCode>USD</c:currencyCode>
</c:fee>
<c:discount>
<c:amount>0.0</c:amount>
<c:currencyCode>USD</c:currencyCode>
<c:discount>
<c:subTotal>
<c:amount>5.00</c:amount>
<c:currencyCode>USD</c:currencyCode>
</c:subTotal>
<c:total>
<c:amount>11.00</c:amount>
<c:currencyCode>USD</c:currencyCode>
</c:total>
</invoicePricing>
</lineItem>
</lineItems>
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (856) | Supported (Best Practice) | Supported | Not Supported |
- Batch—Daily at scheduled one or more scheduled times
- Filename format: Shipment_YYYYMMDD_HHMISS.xml
- Filename format: EDI856_YYYYMMDD_HHMISS.edi
- EDI X12 856 supported version: 00401
If a customer initiates the return of products in an order, Digital River sends the return pre-advice to the fulfillment partner.
The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (180-1) | Supported (Best Practice) | Supported | Not Supported |
- Batch at scheduled intervals
- Filename format: returnNotification_YYYYMMDD_HHMISS.xml
- Filename format: EDI180-1_YYYYMMDD_HHMISS.edi
- EDI X12 832 supported version: 00401
The fulfillment partner sends a response with warehouse RMA ID and optionally a return warehouse address to Digital River. The response is based on the return notification pre-advice sent to the fulfillment partner.
The following table displays the supported formats and data interchange modes from the fulfillment partner to Digital River.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (180-2) | Supported (Best Practice) | Supported | Not Supported |
- Batch at scheduled intervals
- Filename format: returnResponse_YYYYMMDD_HHMISS.xml
- Filename format: EDI180-2_YYYYMMDD_HHMISS.edi
- EDI X12 180-2 supported version: 00401
When returned packages arrive at the warehouse, the Fulfillment partner notifies Digital River Physical Fulfillment to complete the return with a credit payment. This integration notifies Digital River of any returns without a valid return pre-advice from Digital River. This includes shipments refused by the customer or shipments that the fulfillment partner could not deliver to the customer.
Format | AS2 | FTP/SFTP | Web Service Post to Fulfiller |
---|---|---|---|
XML | Supported | Recommended (Best Practice) | Supported (Custom Implementation) |
EDI X12 (180-3) | Supported (Best Practice) | Supported | Not Supported |
- Batch at scheduled intervals
- Filename format: returnReceipt_YYYYMMDD_HHMISS.xml
- Filename format: EDI180-3_YYYYMMDD_HHMISS.edi
- EDI X12 180-3 supported version: 00401
Last modified 6mo ago