LogoLogo
System Status
  • Commerce API
    • Test and use cases
    • Roles and permissions
    • Sending API calls
  • Shopper APIs
    • Shopper basics
      • Common use cases
        • Creating a customer
        • Applying store credit
        • Private store workflow
        • Guest checkout
    • OAuth
      • Authentication
      • OAuth 2.0 APIs
      • Token
      • Access tokens
      • Session-aware access tokens
      • Authorizing a shopper
    • Shoppers
      • Managing shoppers
        • User management
        • Single sign-on (SSO)
        • Data validation
        • Bulk user management
        • Bulk user account export
      • Managing a shopper's account
      • Managing a shopper's address
      • Managing payment options
    • Product discovery
      • Categories
      • Products
      • Product variations
      • Pricing
      • Inventory status
      • Financing
      • Offers
        • Understanding offers
        • How to use point of promotions (POPs)
          • Retrieving all point of promotion offers for a specific product
          • Retrieving all offers for a specific point of promotion
        • How to use offers
      • Private stores
        • Managing private stores
        • Submitting an order for a private store
        • Useful APIs
      • Fulfillment
        • Electronic Fulfillment Service (OFI)
        • Digital rights
        • Digital rights revocation
        • Physical fulfillment
          • EDI X12 832 definition data elements
          • EDI X12 846 definition data elements
          • EDI X12 850 definition data elements
          • EDI X12 855 definition data elements
          • EDI X12 856 definition data elements
          • EDI X12 180-1 definition data elements
          • EDI X12 180-2 definition of data elements
          • EDI X12 180-3 definition of data elements
    • Cart
      • Applying a shopper to a cart
      • Getting the current cart
      • Creating or updating a cart
        • Adding a product to a cart
          • Gifting
        • Capturing the customer's IP address
        • Providing address information
        • Managing the shipping or billing address
        • Providing subscription information
        • Managing payment methods
        • Capturing the Terms of Sale (TOS) acceptance
      • Managing offers in a cart
        • Applying an offer
        • Applying a coupon or promo code
        • Getting all applied offers
        • Removing an applied offer
        • Removing eligible offers
        • Reconciling conflicting offers
        • Dynamic offers/personalization
          • Skipping Global Commerce merchandising offer arbitration
          • Triggering a promotional URL offer
          • Overriding a promotional URL offer discount
      • Pricing
        • Landed cost
          • Mixed cart support
          • Tax-included pretty price
      • Redirecting to a Digital River-hosted cart
      • Configuring taxes
        • Managing tax identifiers
      • Managing shipping options
        • Getting shipping options
        • Providing a shipping discount
      • Managing line items
      • Applying a price override
      • Managing payment sessions
      • Managing web checkout
      • Submitting a cart
        • Initiating a charge
        • Authorization declines
      • Resuming cart submission
      • HGOP2
    • Orders
      • Getting orders
      • Selling entities
      • Retrieving addresses from an order
      • Retrieving line items from an order
      • Order lookup
      • Returns
        • Initiate an authenticated session
        • Setting up returns in Global Commerce
        • Managing returns
    • Subscriptions
      • Retrieve the subscription
        • Getting all orders for a subscription
        • Getting a subscription's pending actions
        • Getting all subscriptions for a shopper
        • Getting a subscription by identifier
      • Update subscription at the next renewal
        • Changing the subscription renewal type
        • Changing the subscription renewal quantity
        • Adding or updating a perpetual unit price
        • Changing the subscription's payment option
        • Changing the subscription's payment source
      • Immediately change the subscription
        • Updating the subscription's shipping address
        • Updating a subscription's billing and shipping email address
        • Cancelling a subscription
      • Immediately apply a midterm subscription change
        • Reducing the subscription renewal quantity
  • Admin APIs
    • Admin basics
      • Available Admin API calls
    • Order management
      • Getting the order's details
      • Downloading the invoice
    • Offer management
    • Refund management
      • Authorization
      • Refund reason codes
      • Creating a satisfaction refund
      • Getting the available refunds for a specific order
      • Getting refunds for a specific order
      • Getting refunds available for a shopper's order
      • Getting the JSON schema for an order refund
      • Managing a refund for a delayed payment method
      • Refund error scenarios
    • Subscription management
      • Retrieve the subscription
        • Getting all orders for a subscription
        • Getting a subscription's pending actions
        • Getting all subscriptions for a shopper
        • Getting a subscription by identifier
      • Update the subscription at the next renewal
        • Changing the subscription renewal type
        • Changing the subscription renewal product
        • Changing the subscription renewal price
        • Changing the subscription renewal quantity
        • Adding or updating a perpetual unit price
        • Changing the subscription's payment option
        • Changing the subscription's payment source
      • Immediately change the subscription
        • Activating a subscription
        • Changing the subscription's external reference identifier
        • Updating a subscription's billing and shipping email address
        • Cancelling a subscription
        • Updating the subscription's expiration date
      • Immediately apply a midterm subscription change
        • Applying a midterm change with price override
        • Reducing the subscription renewal quantity
      • Subscription notifications
        • Updating the subscriber's email address
        • Card Account Updater
        • Sending a payment information change notification
        • Sending an expired credit card notification
        • Sending an invalid payment account notification
        • Sending a payment failure notification
        • Sending a subscription renewal reminder notification
        • Setting up subscription renewal reminders
        • Setting up trial subscription renewal reminders
        • Setting up marketing reminders
      • Using the Expired Card Optimizer
    • Customer management
      • Retrieving customer details
      • Requesting PII removal for a customer
    • Site management
      • Configuring authorized shipping and billing countries
      • Getting a site's authorized billing countries
      • Getting a site's authorized shipping countries
    • Product management
      • Getting started
      • Manage products (asynchronous API)
        • Creating or updating a product
        • Adding or updating a product variation
        • Deploying a product
        • Applying live changes
        • Retiring a product
        • Deleting a product variation
        • Deleting a base or individual product's locale
      • Retrieve products (synchronous API)
        • Getting a product by locale
        • Getting a product variation
        • Getting a product variation by locale
      • Get the task status for a product (synchronous API)
        • Getting the latest information on a product task
        • Retrieving the tasks for a specific product
        • Retrieving the tasks for products
      • Bulk operation
        • Asynchronous bulk operations
          • Creating products in bulk
          • Updating products in bulk
          • Deploying products in bulk
          • Deleting product variations in bulk
        • Bulk product upload (BPU)
        • Bulk Product Export (BPE)
          • Line-item level satisfaction refund
          • Order-level satisfaction refund
          • Auto-created line-item level return product
          • Line-item level return product
    • File management
      • Downloading a file
  • Payments
    • Payments solutions
      • Drop-in payments
        • How Drop-in payments work
        • Drop-in payments integration guide
      • DigitalRiver.js with Elements
        • Elements integration guide
        • Configuring payment methods
          • Configuring Afterpay
          • Configuring Alipay+ (cross-border)
          • Configuring Alipay (domestic)
          • Configuring Amazon Pay
          • Configuring Apple Pay
          • Configuring Bancontact
          • Configuring BLIK
          • Configuring Boleto
          • Configuring CCAvenue
          • Configuring Clearpay
          • Configuring Credit Cards
          • Configuring FPX Online Banking
          • Configuring Google Pay
          • Configuring iDEAL
          • Configuring Klarna
          • Configuring Konbini
          • Configuring Online Banking (IBP)
          • Configuring Online Banking (Korea Bank Transfer)
          • Configuring PayCo
          • Configuring PayPal
          • Configuring SEPA Direct Debit
          • Configuring Trustly
          • Configuring Wire Transfer
          • Common payment sources
          • Common payment objects
    • Supported payment methods
      • Afterpay
      • Alipay (domestic)
      • Alipay+ (cross-border)
      • Amazon Pay
      • Apple Pay
      • Bancontact
      • BLIK
      • Boleto
      • CCAvenue
      • Clearpay
      • Credit Cards
      • FPX Online Banking
      • Google Pay
      • iDEAL
      • Klarna
      • Konbini
      • Korea Bank Transfer (Online Banking)
      • Online Banking (IBP)
      • PayCo
      • PayPal
      • PayPal Billing Agreement
      • PayPal Credit
      • PayPal Pay in 3
      • PayPal Pay in 4
      • PayPal RatenZahlung (Installment Payment)
      • SEPA Direct Debit
      • Trustly
      • Wire Transfer
    • Source basics
      • Managing sources
      • Handling credit card sources
      • Retrieving sources
    • Building payment workflows
      • Flows by payment type
      • Handling redirect payment methods
    • PSD2 and SCA
    • Payment testing scenarios
      • Testing standard payment methods
      • Testing redirect payment methods
      • Testing receiver payment methods
      • Testing the CCAvenue payment method
  • Events
    • Events overview
    • Responding to events
    • Event types
      • Delayed payment event types
        • Delayed payment expired event
          • Boleto
          • Konbini
          • Wire Transfer
        • Delayed payment reminder event
          • Boleto
          • Konbini
          • Wire Transfer
      • Subscription event types
        • Subscription created event
        • Subscription updated event
        • Subscription action processed event
        • Subscription cancelled event
        • Subscription credit card expired event
        • Subscription payment information changed event
        • Subscription renewal reminder event
        • Subscription renewed event
        • Subscription trial converted event
        • Subscription trial renewal reminder event
        • Subscription payment failed event
      • Post-order event types
        • Invoice created event
        • Refund credit memo event
      • Inventory event types
        • Inventory out of stock event
        • Inventory source and management
        • Inventory self-managed updated event
        • Inventory fulfiller-managed updated event
      • Post-order Notification Integration Guide
    • Webhooks
      • Commerce API safelist
      • Searching for a webhook
      • Creating a webhook
      • Using webhooks
      • Editing a webhook
      • Turning webhooks on or off
      • Revealing a webhook's secret
      • Rotating a webhook's secret
      • Viewing the webhook details
      • Deleting a webhook
  • Developer Resources
    • Postman collection
    • Commerce API references
    • Shopper APIs reference
    • Admin APIs reference
    • DigitalRiver.js reference
      • Including DigitalRiver.js
      • Initializing DigitalRiver.js
      • DigitalRiver object
      • Elements
        • Amazon Pay element
        • Apple Pay elements
        • Google Pay elements
        • IBAN element
        • iDEAL element
        • Konbini elements
        • Compliance element
        • Offline refund element
        • Online Banking elements
        • Tax Identifier element
        • Delayed payment instructions element
        • PayPal elements
      • Guidelines for capturing payment details
      • Security
      • Digital River payment objects
      • Error types, codes, and objects
  • General resources
    • Global Commerce
    • Global Commerce
      • Company hierarchy
      • Categories
        • Getting a list of categories
      • Products
        • Product scenarios
        • Individual products
          • Creating an individual product
        • Base product with variants
          • Creating a base product with variants
        • Bundle offers
          • Creating a prorated bundle offer with a subscription
        • Product combination
          • Creating a product combination
        • Gifting
        • Inventory status
      • Customer service
        • Log a shopper's request to remove PII
      • Customers
        • Creating a customer
        • Digital River-maintained customer login
        • Client-maintained customer login
      • Transparent Commerce purchase flow
    • eCompass
    • eCompass documentation
    • Release notes
      • 2024
      • 2024 latest
      • 2023
      • 2022
      • 2021
      • 2020
Powered by GitBook
On this page
  • Sales catalog
  • Supported formats and data interchange modes
  • Recommended frequency
  • XML specification
  • Inventory advice
  • Supported formats and data interchange modes
  • Recommended frequency
  • XML specification
  • Fulfillment order request
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 850 specification
  • Fulfillment order response
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 855 specification
  • Cancel fulfillment order request
  • Supported formats and data interchange modes (Digital River to fulfillment partner)
  • Recommended frequency
  • XML specification
  • Cancel fulfillment order response
  • Supported formats and data interchange modes (fulfillment partner to Digital River)
  • Recommended frequency
  • XML specification
  • Ship notification
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 856 specification
  • Return notification
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 180-1 specification
  • Return notification acknowledgment
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 180-2 specification
  • Return receipt notification
  • Supported formats
  • Recommended frequency
  • XML specification
  • EDI X12 180-3 specification

Was this helpful?

  1. Shopper APIs
  2. Product discovery
  3. Fulfillment

Physical fulfillment

Learn how to integrate the commerce platform with a new fulfillment source.

PreviousDigital rights revocationNextEDI X12 832 definition data elements

Last updated 11 months ago

Was this helpful?

Physical fulfillment is critical to the eCommerce ecosystem, linking online stores with logistics partners to ensure efficient product delivery. By leveraging a network of pre-integrated distribution partners, merchants can globally fulfill orders based on customizable rules. This process streamlines order and return management and optimizes inventory handling, making it easier to meet customer demands and enhance satisfaction.

Physical fulfillment connects a commerce site to logistics partners who drop-ship products to the shopper. It also enables a commerce site to smart-source orders through one or more 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

Inbound

Inbound

Webhook

Inbound

Webhook

Inbound

Inbound

Webhook

Inbound

Inbound

Physical fulfillment

Sales catalog

The Sales Catalog plays a crucial role in the integration process by loading the fulfillment partner’s product catalog into the Digital River Physical Fulfillment system. This catalog feed includes essential product information such as SKU, manufacturer’s part number, weight, dimensions, and unit cost. The unit cost represents the price at which the fulfiller sells the product to Digital River, not the retail price charged to the shopper. The catalog can be submitted in different formats, with XML being supported.

Note that the unit cost is the amount the fulfiller/distributor sells the product to Digital River (that is, not the amount they charge the shopper).

<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.

Supported formats and data interchange modes

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

Recommended frequency

  • Full file (Weekly/On-demand)

  • Delta daily

XML specification

  • File name format: Catalog_YYYYMMDD_HHMISS.xml

Inventory advice

The Inventory Advice integration imports inventory information from a fulfillment partner's warehouse into the Digital River Physical Fulfillment system.

Supported formats and data interchange modes

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

Recommended frequency

  • Full file or delta—hourly

XML specification

  • Filename format: Inventory_YYYYMMDD_HHMISS.xml

Fulfillment order request

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, quantity, shipping, and shipping address. The following table displays the formats and data interchange modes supported by Digital River's fulfillment partner.

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

Supported formats

The following table displays the formats and data interchange modes that Digital River's fulfillment partner supports.

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

Recommended frequency

  • Real-time or Batch at a scheduled interval

XML specification

  • Filename format: ODD_HHMISS.xml

EDI X12 850 specification

  • Filename format: OrderRequest_YYYYMMDD_HHMISS.xml

  • EDI X12 850 supported version: 00401

Fulfillment order response

The fulfillment partner responds to each request indicating whether the order was accepted or rejected/cancelled due to errors. If a product is unavailable, and if the order request allows 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, quantity, shipping, and shipping address.

Supported formats

The following table displays the formats and data interchange modes that Digital River's fulfillment partner supports.

Recommended frequency

  • 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

XML specification

  • Filename format: OrderResponse_YYYYMMDD_HHMISS.xml

EDI X12 855 specification

  • Filename format: EDI855_YYYYMMDD_HHMISS.edi

  • EDI X12 855 supported version: 00401

Cancel fulfillment order request

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.

Supported formats and data interchange modes (Digital River to fulfillment partner)

Format
AS2
FTP/SFTP
Web Service Post to Fulfiller

XML

Supported

Recommended (Best Practice)

Not Supported

Recommended frequency

  • Batch at a scheduled interval

XML specification

  • Filename format: CancelRequest_YYYYMMDD_HHMISS.xml

Cancel fulfillment order response

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.

Supported formats and data interchange modes (fulfillment partner to Digital River)

Format
AS2
FTP/SFTP
Web Service Post to Fulfiller

XML

Supported

Recommended (Best Practice)

Not Supported

Recommended frequency

  • Batch at a scheduled interval

XML specification

  • Filename format: CancelResponse_YYYYMMDD_HHMISS.xml

Ship notification

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 backorder 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:

EDI 856 / shipment notification

  • You must include the shipping amount and the subtotal amount in the segment

  • The fulfiller/distributor invoices Digital River for the shipping amount charged to the customer

  • The file must include the lineItem segment

<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>     

Supported formats

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

Recommended frequency

  • Batch—Daily at scheduled one or more times planned

XML specification

  • Filename format: Shipment_YYYYMMDD_HHMISS.xml

EDI X12 856 specification

  • Filename format: EDI856_YYYYMMDD_HHMISS.edi

  • EDI X12 856 supported version: 00401

Return notification

If a customer initiates the return of products in an order, Digital River sends the return pre-advice to the fulfillment partner.

Supported formats

The following table displays the formats and data interchange modes supported by the fulfillment partner for 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

Recommended frequency

  • Batch at scheduled intervals

XML specification

  • Filename format: returnNotification_YYYYMMDD_HHMISS.xml

EDI X12 180-1 specification

  • Filename format: EDI180-1_YYYYMMDD_HHMISS.edi

  • EDI X12 832 supported version: 00401

Return notification acknowledgment

The fulfillment partner sends Digital River a response with a warehouse RMA ID and a return warehouse address optionally. The response is based on the return notification pre-advice sent to the fulfillment partner.

Supported formats

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

Recommended frequency

  • Batch at scheduled intervals

XML specification

  • Filename format: returnResponse_YYYYMMDD_HHMISS.xml

EDI X12 180-2 specification

  • Filename format: EDI180-2_YYYYMMDD_HHMISS.edi

  • EDI X12 180-2 supported version: 00401

Return receipt notification

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 the customer refuses or shipments that the fulfillment partner could not deliver to the customer.

Supported formats

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

Recommended frequency

  • Batch at scheduled intervals

XML specification

  • Filename format: returnReceipt_YYYYMMDD_HHMISS.xml

EDI X12 180-3 specification

  • Filename format: EDI180-3_YYYYMMDD_HHMISS.edi

  • EDI X12 180-3 supported version: 00401

XML schema:

XML sample:

See the for more information.

XML schema:

XML sample:

See the for more information.

XML schema:

XML sample:

See the for more information.

XML schema:

XML sample:

See the for more information.

XML schema:

XML sample:

XML schema:

XML sample:

The subtotal amount is the unit cost (same unit cost as noted in the ) multiplied by the quantity

XML schema:

XML sample:

See the for more information.

XML schema:

XML sample:

See for more information.

XML schema:

XML sample:

See for more information.

XML schema:

XML sample:

See for more information.

https://fulfillment-api.digitalriver.com/v1/fulfiller-account/catalog/product.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/catalog/product-import-request.xml
EDI X12 832 definition data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/catalog/inventory.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/catalog/inventory-import-request.xml
EDI X12 846 definition data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/order.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-request.xml
EDI X12 850 definition of data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/order.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-status-notification.xml
EDI X12 855 definition of data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-cancel.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-cancel-request.xml
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-cancel.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/fulfillment-cancel-status-notification.xml
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/shipment.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/shipment-import-request.xml
EDI X12 856 definition of data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return-fulfillment-request.xml
EDI X12 180-1 definition of data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return-fulfillment-status-notification.xml
EDI X12 180-2 definition of data elements
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return.xsd
https://fulfillment-api.digitalriver.com/v1/fulfiller-account/return-fulfillment-received.xml
EDI X12 180-3 definition of data elements
Sales Catalog
Sales Catalog
Inventory Advice
Fulfillment Order Request
Fulfillment Order Response
Cancel Fulfillment Order Request
Cancel Fulfillment Order Response
Ship Notification
Return Notification
Return Notification Acknowledgement
Notification