Adobe Commerce (Magento 2)

• Write products, categories and master dataWrite

  Writes products by SKU and assembles product, custom and extension attributes from one field table. Images are handed over as content, not as an address.

• Read dataRead

  Reads data back from Adobe Commerce, only what changed since the last run if needed. Were a response from the shop too large, ConFlowIO reads the same records in smaller pages on its own.

• Read ordersRead

  Reads orders as Commerce Bundle orders — with items, billing and shipping address and processing state, only the open ones and only those changed since the last run if needed.

• Create shipmentsWrite

  Creates shipments with tracking number and carrier, as a partial shipment if needed.

• Order actionsWrite

  Creates invoices — for the items of one record only if needed —, cancels orders, holds, releases or comments on them.

• Credit memosWrite

  Creates credit memos, offline or through the payment provider. A refund always needs an explicit statement of what is refunded, is recorded in the shop with a reference of its own and is never triggered twice.

• Read returnsRead

  Reads returns with their state and reason, in the Commerce Bundle's return model — in Adobe Commerce only, not in Magento Open Source.

• Read customersRead

  Reads customer accounts in the Commerce Bundle's customer model. Names, addresses and contact details are read only when that is explicitly switched on in the building block.

• Write customersWrite

  Creates or changes customer accounts from the Commerce Bundle's customer model.

• Read tier and customer-group pricesRead

  Reads tier and customer-group prices back.

• Write tier and customer-group pricesWrite

  Writes tier and customer-group prices to the products.

• Read price rules and coupon codesRead

  Reads cart price rules and coupon codes.

• Free API callFree request

  Reaches everything the shop's API offers — just without the groundwork and the safeguards of a ready-made building block.

Product images are written straight out of the write block — as content, because Adobe Commerce does not accept an address.

• How Adobe Commerce sees a productA product lives in three parts; you maintain one table.
  • Recognised directly by the SKU
  • Price on the product, extra fields in a separate list
  • Stock in the extension attributes
• Not coveredWhat limits the integration — mostly because Adobe Commerce sets it that way.
  • Returns in Adobe Commerce only, not in Magento Open Source — and read only
  • Images only as content: downloading by the platform is therefore off by default
  • The size per image is capped
• DurabilityApplies to this integration as to every workflow in ConFlowIO.
  • Failed steps retry themselves
  • Large reads are processed page by page, each page a step of its own
  • A failed run is continued rather than started over
  • Live logs per step, with credentials removed