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
  • Integration with sales channels
  • Integration with fulfillment processes
  • Technical integration example
  • Key attributes
  • inventory.fulfiller_managed_updated use case
  • Manually set inventory to 0 use case

Was this helpful?

  1. Events
  2. Event types
  3. Inventory event types

Inventory fulfiller-managed updated event

Understand the inventory fulfiller-managed update event.

PreviousInventory self-managed updated eventNextPost-order Notification Integration Guide

Last updated 1 year ago

Was this helpful?

The inventory.fulfiller_managed_updated event plays a pivotal role in the seamless inventory management for merchants using third-party fulfillment services. It is designed to ensure real-time updates and accuracy of inventory levels, thereby maintaining the integrity of stock information across various sales platforms. This immediate synchronization aids in keeping product availability current, enhancing inventory accuracy and streamlining the order fulfillment process.

See for instructions on configuring the webhook events and Inventory source and management for comparing inventory self-manged updated and inventory fulfiller-managed updated events.

The inventory.fulfiller_managed_updated event monitors and tracks updates made by third-party fulfillers on inventory levels. This event is essential for merchants leveraging external fulfillment services for inventory management. It plays a key role in:

  • Keeping product availability up-to-date: Ensures inventory levels across all sales channels are immediately updated following changes by the fulfiller.

  • Enhancing inventory accuracy: Maintains precise inventory records by reflecting current stock information.

  • Streamlining order fulfillment: Assists in the smooth operation of the order fulfillment process by minimizing discrepancies in inventory data.

This event allows merchants to maintain operational efficiency, ensuring that inventory data is consistent and optimizes the sales experience.

Integrating the inventory.fulfiller_managed_updated event into an eCommerce system is crucial for maintaining real-time synchronicity between physical inventory, the eCommerce platform, and sales channels. Here's a concise overview:

Integration with sales channels

  • Real-time inventory updates: When a fulfiller manages an inventory update, it triggers the inventory.fulfiller_managed_updated event, immediately reflecting changes across all connected sales channels. This prevents overselling and ensures that the available stock is accurately represented online.

  • Enhanced customer experience: Keeping inventory levels accurate allows customers to see real-time availability, reducing the chances of ordering out-of-stock products. This transparency builds trust and enhances the buying experience.

Integration with fulfillment processes

  • Streamlined order fulfillment: With accurate inventory levels, the eCommerce system can efficiently allocate orders to the fulfillment queue, ensuring that products are in stock and ready for shipment. This minimizes delays and accelerates the fulfillment process.

  • Inventory reconciliation: The event provides a foundation for automated inventory reconciliation processes, enabling the system to identify discrepancies between reported and actual inventory levels, thus facilitating timely adjustments.

Technical integration example

For a practical integration example, consider a webhook set up within the eCommerce system that listens for the inventory.fulfiller_managed_updated event. Upon receiving this event, the system can:

  1. Update the inventory count across all listings on various sales channels.

  2. Notify the sales and fulfillment teams of inventory changes, prompting necessary actions like adjusting marketing strategies or preparing for increased order volumes.

  3. Automatically adjust order routing rules based on stock availability and fulfillment center locations, optimizing delivery times.

Integrating the inventory.fulfiller_managed_updated event into the broader eCommerce ecosystem enables businesses to synchronize their physical and digital operations, enhancing efficiency, customer satisfaction, and operational transparency.

Key attributes

When integrating the inventory.fulfiller_managed_updated event into your eCommerce platform, it's essential to understand the key attributes of the event payload. These attributes provide detailed information about the inventory change, enabling more accurate and efficient processing. Below is an overview of these attributes and their significance in managing inventory updates:

  • id: A unique identifier for the event instance allows easy tracking and reference.

  • type: Specifies the type of event, in this case, inventory.fulfiller_managed_updated, to differentiate from other inventory or system events.

  • data: Encapsulates the event-specific data, including:

    • object: Contains details about the item, such as:

      • quantity: Indicates the current inventory level. A 0 indicates an out-of-stock event.

      • timestamp: The exact time when the inventory change was recorded.

      • products: Contains an array of products affected by the inventory update. Each product has:

        • externalReferenceId: A unique external reference identifier for the product (null if not provided).

        • productId: The unique identifier of the product.

    • eventType: Identifies the specific action that triggered the inventory update event. This attribute is crucial for understanding the nature of the event, such as inventory.fulfiller_managed_updated, indicating that the inventory managed by the fulfiller has been updated. This helps in filtering and responding to various types of inventory-related events effectively.

    • partNumber: The part number related to the inventory item.

    • fulfiller: The name of the third-party fulfiller managing the inventory (DR globalTech).

    • allowBackOrder: Indicates whether backorders are allowed for the out-of-stock product (false).

    • inventoryManagement: Specifies the inventory management type, which is Fulfiller Managed.

  • previousAttributes: Contains critical product information regarding the state of inventory before the update. This is especially important for tracking and understanding the changes in inventory levels. This can include:

    • quantity: Reflects the inventory level before the update. This attribute allows systems and stakeholders to measure the change in inventory, enabling more informed decisions regarding sales strategies, fulfillment operations, and inventory management.

    Understanding the previousAttributes is essential for analyzing inventory trends over time and can be a pivotal factor in making data-driven decisions within the eCommerce ecosystem.

  • liveMode: Indicates if the event was triggered in a live operational environment or a test mode (false).

  • createdTime: Records the timestamp of when the webhook event was generated, providing a chronology.


{
    "id": "cda6bf91-96e6-463b-959b-8e82dd81addd",
    "type": "inventory.fulfiller_managed_updated",
    "data": {
        "object": {
            "quantity": 1,
            "timestamp": "2024-01-30T08:49:44.331Z",
            "products": [
                {
                    "externalReferenceId": null,
                    "productId": "15116720197"
                }
            ],
            "eventType": "inventory.fulfiller_managed_updated",
            "partNumber": "CCC",
            "fulfiller": "DR globalTech",
            "allowBackOrder": false,
            "inventoryManagement": "Fulfiller Managed"
        },
        "previousAttributes": {
            "quantity": 0
        }
    },
    "liveMode": false,
    "createdTime": "2024-01-30T14:49:45.55875Z"
}

inventory.fulfiller_managed_updated use case

If you use Global Commerce's fulfiller-managed inventory, inventory.fulfiller_managed_updated is triggered when you update inventory from 2 to 50. The following image displays the payload for this webhook event.

Manually set inventory to 0 use case

There are several reasons why you might want to set the inventory to 0 manually:

  1. Out of stock: If the item is temporarily or permanently unavailable, setting the inventory to 0 prevents customers from ordering it.

  2. Seasonal or discontinued products: For seasonal items not currently available or products that have been discontinued.

  3. Inventory reset: When doing an inventory count or audit, it might be simpler to reset the count to 0 and build it back up as you verify stock.

  4. Error correction: If there was a mistake in the inventory count, setting it to 0 can be a step in correcting the inventory level.

  5. Platform synchronization: To synchronize inventory across various sales channels, ensuring they reflect the same availability.

If you want to set the inventory to 0, use Global Commerce's self-managed inventory, inventory.self_managed_updated, or fulfiller-managed inventory, inventory.fulfiller_managed_updated.

See the section for instructions on creating the webhook.

Creating a webhook
Getting started with webhooks in Commerce API
inventory.fulfiller_managed_updated event