- Adobe Commerce B2B
- The separately installed package, magento/extension-b2b, that adds company accounts, shared catalogs, quick order, requisition lists, negotiable quotes, and purchase-order approvals to Adobe Commerce. Adobe's documentation states it is available for Adobe Commerce; the features do not exist on Magento Open Source.
- Adobe Commerce as a Cloud Service
- Adobe's multi-tenant, versionless SaaS edition. Adobe's feature comparison states it supports out-of-process extensibility only, through APIs, events, and App Builder, and no in-process PHP customization.
- App Builder
- Adobe's platform for running code outside the Commerce process. Adobe's integration starter kit uses it, with I/O Events, to connect Commerce to ERPs, CRMs, and PIMs.
- Async bulk API
- Adobe Commerce endpoints under /async/bulk/V1/ (PaaS) or /V1/async/bulk/ (SaaS) that accept a batch of operations and return a bulk_uuid. The async.operations.all consumer processes the queued messages; if it is not running, nothing is processed and nothing errors.
- Available-to-promise
- The quantity a storefront may sell now, after allocations and reservations in the ERP. Bemeir's articles put it on the near-real-time list because staleness costs money.
- Cadence
- How often an object is synchronized, per object: every few minutes for stock and price, hourly or nightly for catalog and invoices, on event where the ERP supports it.
- Concurrency limit
- The number of simultaneous API requests an ERP account allows. Oracle's NetSuite documentation governs it at the account level, by service tier plus 10 per SuiteCloud Plus license.
- Dead-letter queue
- Where a message goes after it fails its retries, so it can be inspected and replayed rather than lost. iWeb's ERP hub states dead-letter handling; most agency pages do not mention it.
- Delta sync
- Sending only what changed since the last run, rather than the full object set. Bemeir's SAP article describes its pattern as delta-based.
- ERP
- Enterprise resource planning software: the system of record for item master, cost, price lists, stock, customers, credit, orders, and invoices. SAP, NetSuite, Dynamics 365 Business Central, Epicor Prophet 21, Prelude, BisTrack, and Infor are the products named on this site.
- iPaaS
- Integration platform as a service: a third-party middleware product that holds field maps, retries, and monitoring between the ERP and the store, at the cost of a second vendor and a per-message price.
- In-process module
- Integration code that runs inside Magento's PHP process, in app/code. It is the pattern behind most connectors built before 2024 and the one Adobe Commerce as a Cloud Service will not run.
- Lifecycle
- Adobe's published support dates per release. In 2026, 2.4.4 and 2.4.5 are out of extended support, 2.4.6 is out of regular support, and 2.4.7, 2.4.8, and 2.4.9 are in regular support until May 2027, 2028, and 2029.
- OData
- An HTTP query protocol used by SAP and by Dynamics 365 Business Central's API v2.0. Bemeir's articles name it as the interface for both.
- Ownership split
- A written statement of which system writes each object: the ERP for price, stock, credit, and post-order status; the store for cart, session, content, and the order at capture. Bemeir publishes one; scandiweb's BK-Group case shows one built.
- PIM
- Product information management software, such as Pimcore or Akeneo, that holds enriched product data between the ERP and the store. In scandiweb's BK-Group case it also holds per-customer prices as a middle layer.
- Shared catalog
- The Adobe Commerce B2B feature that assigns a catalog and prices to a company or customer group. It creates price rows per group, so the price index grows with the number of groups.
- SuiteTalk
- NetSuite's web services. Oracle's documentation states that OAuth 2.0 is available for REST web services and RESTlets only, and that SOAP web services do not support it.