Skip to main content
Use the @bijection/connectors/adobe-commerce entrypoint to declare Adobe Commerce resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Orders

pull: Carried updated_at walk, unknown-entity withdrawal and unconditional shipments

The following example matches configuration standard.

Configuration: standard

Case: adobe-commerce/orders/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: adobe-commerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: shipments

Case: adobe-commerce/orders/pull/shipments. Connection and resource configuration are declared by this exact case. Credential kind: adobe-commerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: orders
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Customers

pull: Carried updated_at walk with unknown-entity withdrawal

The following example matches configuration standard.

Configuration: standard

Case: adobe-commerce/customers/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: adobe-commerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: customers
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Products

pull: Carried updated_at walk without deletions

The following example matches configuration standard.

Configuration: standard

Case: adobe-commerce/products/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: adobe-commerce. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: products
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection dials the instance’s base URL (baseUrl setup); the store view code (storeCode setup) selects the scope in /rest/{storeCode}/V1. The adobe-commerce credential is an integration access token presented as a Bearer, which Adobe Commerce accepts only with “Allow OAuth Access Tokens to be used as standalone Bearer tokens” enabled. OAuth 1.0a request signing is not supported. Adobe Commerce names no tenant, so the connection asserts no account identity; the probe (store/storeConfigs) proves the token reaches the store view. Each collection is a searchCriteria walk on updated_at gteq sorted ASC, 100 a page, carried between passes from five minutes before the latest updated_at the previous pass read. Asking past the last page answers the last page again, so a pass ends where the page count reaches the stated total_count. Re-read rows deduplicate by updated_at, their opaque version.
  • orders.pull: GET /V1/orders. state and status are kept as stated. Money (grand_total, base_grand_total, subtotal, tax_amount, shipping_amount, discount_amount, total_paid, total_refunded) arrives as JSON numbers: kept as the received double’s text beside order_currency_code and base_currency_code, never claimed exact. An order whose point read answers Magento’s unknown-entity 404 is withdrawn; a 404 with any other message (an unmatched route, a wrong store code) is unresolved.
  • customers.pull: GET /V1/customers/search, withdrawn the same way.
  • products.pull: GET /V1/products, keyed by entity id. The REST point read addresses products by SKU, so no point read is declared and a deleted product is not withdrawn.
ship posts POST /V1/order/{id}/ship with the given body. Adobe Commerce validates the quantity left to ship, which refuses repeating a complete shipment but not a partial one, and offers no idempotency key, so it is one unconditional attempt and a lost answer stays unknown. Adobe Commerce’s webhooks module is RSA-signed and not admitted; open source Magento has none. Nothing here has run against Adobe Commerce or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.