MConnect supports Adobe Commerce (Magento 2) Enterprise and Community integrations. The Adobe Commerce integration allows sellers to import products from their Adobe Commerce instance to their marketplace seller account, sync stock levels and prices, and push invoices back to Adobe Commerce for fulfillment.
Steps within Adobe Commerce (Magento 2)
Before you start: MConnect for Adobe Commerce requires the access token to be used independently for token-based authentication. To update the setting, go to admin Stores > Configuration > Services > OAuth > Consumer Settings > Allow OAuth Access Tokens to be used as standalone Bearer tokens option to Yes.
You can also enable this setting from the CLI (Command Line Interface) by running the following command:
bin/magento config:set oauth/consumer/enable_integration_as_bearer 1
- Log in to your Adope Commerce store and go to System > Integrations.
- Click Add New Integration.
- Fill out only the required fields and set API Resource Access for Sales, Catalog & Stores. Your resources may look different.
- Click Save.
- To authorize the integration, click Allow on the API permissions,
- Copy the Access Token to your clipboard.
Steps within Marketplacer
You must first set up the integration in Adobe Commerce (Magento 2) before following the steps below. For detailed instructions on setting up the integration in Adobe Commerce, refer to the Steps within Adobe Commerce section above.
- Log in to your Marketplace and access MConnect.
- Click Adobe Commerce (Magento 2) > Set my account type.
- Proceed through the steps to select what you want to sync, and whether you want currency conversion.
- Enter the Magento Access Token that you copied to your clipboard and the URL of your Magento store.
- Click Submit.
- You can then either start a full import or review the integration settings. If you select Review the integration settings, you can start an import by going to Imports.
Note: If the “integration not secure” error occurs in Adobe Commerce, this would be due to problems on Adobe Commerce's side, such as the identity link URL or the callback URL fields having a URL in them when these fields should be left blank.
Related articles