LogoLogo
System status
Commerce API references
Commerce API references
  • Commerce API references
  • Warnings and error codes
    • Errors
    • Error codes
      • HTTP response status codes
      • Error format for Shopper APIs
      • Error codes for Shopper APIs
        • 400 Bad Request
        • 401 Unauthorized
        • 403 Forbidden
        • 404 Not Found
        • 405 Method Not Allowed
        • 409 Conflict
        • 412 Precondition Failed
        • 413 Payload Too Large
        • 500 Internal Server Error
      • Error format for Admin APIs
        • Async error objects
        • Sync error objects
        • Deployment objects
        • Warning objects
      • Error codes for Admin APIs
        • Error patterns
        • Supported image types
        • Asynchronous response error codes
        • Deployment error codes
        • Synchronous response error codes
  • Commerce API reference guide
    • API structure
      • API keys
      • Supported OAuth and Commerce API formats
      • Mini cart widget
      • Custom attributes
      • Fields used as keys
      • Fields and expand query parameters
      • Caching responses
      • CORS support
      • JSONP support
      • Transport
      • Service profiles
      • Supported protocols and formats
      • Elements
      • Rate limiting
      • Locale and currency
      • Exchange rate
      • Product identifier
      • Product external reference identifier (ERID)
      • Customer external reference identifier ERID
      • Cancel request process
      • Failover and redundancy
      • Troubleshooting API calls
    • Shopper APIs reference
      • Carts
        • Offers
          • Offer types
          • POP offers
          • Applied offers
          • Eligible offers
      • Orders
      • Returns
      • Links
    • Admin APIs reference
      • Subscriptions
      • Sites
      • Products
      • Live changes
      • Authorized shipping and billing countries
      • Merchandising
      • Disclosures
    • Glossary
Powered by GitBook
On this page
  1. Commerce API reference guide
  2. API structure

Cancel request process

Learn how to handle various Cancel Request scenarios.

The following list describes how to handle various Cancel Request scenarios.

  • Process a Cancel Request after you process a Fulfillment Request and before you process a Shipment Notice.

  • When a Cancel Request contains incorrect product information, and you determine that the product was discontinued or inactive when matching the product information, accept the Cancel Request by sending a Fulfillment Notice with a status of Cancelled.

  • If you have already shipped an order, generated a Shipped message, and sent it to Digital River, you do not need to generate and send another message to Digital River. You can ignore the Cancel Request. You received a Cancel Request because of small timing issues when processing Fulfillment Notices and generating Cancel Requests.

  • If you cannot honor a Cancel Request, send the Fulfillment Notice to Digital River with a Shipped status, as you normally would for a shipped order. In this scenario, there is no need to deny a Cancel Request; if Digital River receives a Fulfillment Notice with a status of Shipped, we assume you could not cancel the order or part of the order.

  • When you accept the Cancel Request, you must remove the values from the prices you display on the packing slip. You can take the values in the original Fulfillment Request sent to you and add the prices on the Cancel Request. Since the Cancel Request prices are negative, the correct values will appear on the packing slip. If you don't add the prices to the Cancel Request, the prices appear as negative values.

  • Digital River could send the requests so closely together that you might process them serially in the same block. For example, Digital River could send you multiple Cancel requests for different parts of the order. If you accept one Cancel Request and not the other, the new prices in the Cancel Request will not be accurate, depending on which Cancel Request you accepted. Do not send new prices for the packing slip when you accept a Cancel Request.

PreviousCustomer external reference identifier ERIDNextFailover and redundancy

Last updated 4 months ago