Adobe Commerce provides two primary, modern web APIs for third-party system integration: REST and GraphQL. Both are fully suited for integrating an inventory management system.

The REST API provides a comprehensive set of endpoints for managing all aspects of the platform, including Multi-Source Inventory (MSI). It is a conventional and robust choice for server-to-server integrations.

The GraphQL API is a modern, flexible alternative that allows clients to request precisely the data they need, which can be highly efficient. It also has full support for inventory queries and mutations.

Official Adobe Commerce documentation provides specific examples for managing inventory using both REST and GraphQL, confirming both are appropriate for this task.

B. gRPC: Magento (Adobe Commerce) does not provide native support for the gRPC framework. Therefore, it cannot be used for this integration out-of-the-box.

D. XWL-RPC: This is a typo for XML-RPC. The XML-RPC API was available in Magento 1 but was deprecated and completely removed in Magento 2 / Adobe Commerce.

1. Adobe Commerce Developer Documentation

"Inventory Management web APIs": This official guide explicitly demonstrates how to perform inventory management tasks

such as managing stock and sources

using both REST API calls (e.g.

POST /V1/inventory/source-items) and GraphQL mutations (e.g.

mutation { updateSourceItems(...) }). This directly supports that both A and C are correct.

Source: Adobe Commerce Developer Documentation > Inventory Management > Web APIs.

2. Adobe Commerce Developer Documentation

"Introduction to Adobe Commerce web APIs": This document introduces the available web APIs

focusing on REST and GraphQL as the primary integration methods for Adobe Commerce. It positions them as the standard technologies for interacting with the platform's resources.

Source: Adobe Commerce Developer Documentation > Web APIs > Overview.

3. Adobe Commerce Developer Documentation

"Deprecated features": This page confirms the removal of the XML-RPC API

stating

"The XML-RPC API library is not supported in Magento 2. The REST and SOAP APIs provide better scalability

and are more robust." This validates that option D is incorrect for the current platform.

Source: Adobe Commerce Developer Documentation > Get Started > Magento Technology Stack > Deprecated features.

The asynchronous bulk API is the most appropriate choice for integrating an ERP system that needs to push large amounts of product and category changes. This API is specifically designed to handle a high volume of operations by queuing them for background processing. This approach avoids server timeouts and performance degradation that can occur with synchronous APIs when handling large datasets. The ERP can submit a batch of changes in a single request and receive an acknowledgment, while Magento processes the updates asynchronously, ensuring system stability and efficient data handling.

A. The GraphQL API: While capable of mutations, GraphQL is primarily optimized for complex data queries from client applications (e.g., PWAs), not for large-scale, server-to-server bulk data synchronization.

B. The synchronous REST API: Processing a large number of changes via synchronous REST API would require many individual requests, leading to significant performance overhead, potential network latency issues, and request timeouts.

D. The synchronous bulk API: This is not a distinct, officially named Magento API. While some synchronous REST endpoints can accept multiple entities, the truly scalable solution for large volumes is the asynchronous API.

1. Adobe Commerce Developer Documentation

"Asynchronous web APIs": "Use asynchronous endpoints to execute long-running operations without having to wait for the operation to complete. Asynchronous API requests are queued in a message queue and executed asynchronously. These endpoints are useful for tasks such as importing a large number of products or customers." (Adobe Commerce 2.4 Developer Guide

Web APIs

Asynchronous web APIs section).

2. Adobe Commerce Developer Documentation

"Bulk endpoints": "The bulk API provides a way to process a group of entities in a single request. The system processes bulk API requests asynchronously... The bulk API is an efficient way to handle a large number of operations against a specific resource." (Adobe Commerce 2.4 Developer Guide

Web APIs

Bulk endpoints section).

Magento Commerce provides a "Scheduled Import" feature designed specifically for this use case. It allows merchants to automate recurring data updates by configuring an import to run on a schedule (e.g., weekly on Sunday). The system is configured to monitor a specific directory on a local or remote server. The merchant team only needs to place the updated CSV file with the new product prices in that directory, and a cron job will automatically process the import at the scheduled time. This is the most efficient and scalable method to handle regular, bulk product updates, eliminating manual intervention.

A. This describes a standard, manual import. It is not automated and requires a user to log in and perform the upload every Sunday, which does not fully "speed up the process" from a workflow perspective.

B. Scheduled Updates (Content Staging) are primarily for managing campaigns and previewing site-wide changes. Manually creating a scheduled update for dozens of individual price changes is inefficient compared to a file import.

C. The "Update Attributes" mass action can only apply a single price change to all selected products. It cannot be used to assign unique, different prices to dozens of products in one operation.

1. Adobe Commerce User Guide

Scheduled Import/Export: "The Scheduled Import/Export feature allows you to set up the automatic import or export of data through a file exchange over FTP or a local server... You can set up the schedule

file source

and other operational details for each import or export." This documentation directly supports the workflow described in option D.

2. Adobe Commerce User Guide

Updating Products (Mass Actions): "The Update Attributes action applies a change to a specific attribute for all selected products." This confirms that this action cannot be used to set unique prices for multiple products

invalidating option C.

3. Adobe Commerce User Guide

Scheduled Changes: "A scheduled change is a set of content staging assets that are created to go live at a future date and time." This highlights that Scheduled Updates are for broader content campaigns

not optimized for recurring bulk data updates like price lists

making option B less suitable.

By default, requisition lists in Magento Commerce B2B are private and only visible to the user who created them. To allow users to make their lists visible to others within their company, the sharing functionality must be explicitly enabled. This is a global configuration setting found in the Magento Admin panel under the Requisition Lists configuration. If this "Enable Requisition List Sharing" option is not activated, users will not have the ability to share their lists, and they will remain hidden from their colleagues, which explains the issue described.

A. The setting to enable requisition list sharing is a global configuration, not a setting that is managed individually for each company.

B. This statement is incorrect. Requisition lists are private to the creator by default and are only shared if the sharing feature is enabled and the user chooses to share a specific list.

D. The company administrator manages company users, roles, and permissions from the storefront, but they do not control the global system configuration that enables or disables the requisition list sharing feature itself.

1. Adobe Commerce User Guide

B2B Configuration Reference: In the section for Requisition Lists configuration

it details the "Enable Requisition List Sharing" option. It states

"Determines if company users can share their requisition lists with other users in the company." This confirms that sharing is a configurable feature that must be enabled globally.

Source: Adobe Experience League

Commerce 2.4 User Guide

B2B Configuration Reference

Sales Section. (Path: Stores > Settings > Configuration > Sales > Requisition Lists).

2. Adobe Commerce User Guide

Requisition Lists (B2B): This guide explains the user-facing functionality and notes the default privacy. It states

"By default

requisition lists are private and available only to the user who created them. However

requisition lists can be shared with other users in the company." This establishes that lists are not shared by default and require an action

which is only possible if the feature is enabled as per reference #1.

Source: Adobe Experience League

Commerce 2.4 User Guide

Sales Features (B2B)

Requisition Lists.

In Adobe Commerce (Magento), tax calculation is based on the combination of three core elements: a customer tax class, a product tax class, and a tax rate. The merchant has configured each of these elements in isolation. However, for the system to apply a specific tax, a Tax Rule must be created. This rule explicitly links these three components together, telling Magento which tax rate to apply when a customer from a specific class purchases a product from a specific class. Without this connecting rule, the tax calculation engine has no instructions on how to apply the configured rates, resulting in no tax being added to orders.

A. integrate a GeoIP service so Magento can correctly identify the customer's region.

A GeoIP service is an enhancement for estimating location, but tax calculation fundamentally relies on the customer's shipping or billing address, which is required for checkout. The core logic is missing, not the location data.

B. Edit each individual product to make sure that it is assigned to the right taxable region.

Products are assigned to tax classes, not directly to taxable regions. Taxable regions (like state or country) are defined within the tax rate configuration, not at the product level.

D. Select the correct tax rates within the customer tax class configuration.

Tax rates are not assigned directly within a customer tax class. The association between a customer class, product class, and tax rate is made exclusively within a Tax Rule.

---

1. Adobe Commerce User Guide

"Tax Rules": "A tax rule is a combination of a product tax class

customer tax class

and tax rate. Each customer is assigned to a a customer tax class

and each product is assigned to a product tax class. Magento analyzes the shopping cart of each customer and calculates the appropriate tax according to the customer and product classes and the store's tax rules."

Source: Adobe Commerce Documentation

Stores > Taxes > Tax Rules.

2. Adobe Commerce User Guide

"Tax Configuration Best Practices": "The basic components of tax configuration are Tax Rates

Tax Zones

and Tax Rules. For tax to be calculated correctly

you must configure all three components." This statement emphasizes that all three parts

including the rule

are mandatory for the system to function.

Source: Adobe Commerce Documentation

Stores > Taxes > Tax Configuration Best Practices.

3. Adobe Commerce Developer Documentation

"Tax": The developer documentation outlines the database schema

showing that the taxcalculationrule table links customertaxclassid

producttaxclassid

and a code that corresponds to the taxcalculationrate. This confirms at a technical level that the rule is the linking entity.

Source: Adobe Commerce Developer Documentation

Architecture > Core Architecture > Tax.