# Magento 2: prepare and connect your store

Connect Magento 2 by preparing an integration in Magento Admin and confirming the authentication and stock setup with Optiply Support. Choose the warehouse or non-warehouse stock route before connecting: the two routes use different stock information.

## Before you connect Magento 2

You need access to the Optiply account you want to connect and a Magento administrator who can manage integrations. [Contact Support](/support) to agree the store, stock route and authentication method before generating credentials. Have the store URL ready, but keep tokens and secrets out of ordinary messages, screenshots and correction forms.

This procedure is for Magento Open Source and Adobe Commerce installations with the Magento Admin integration screen. Adobe Commerce Cloud Services uses a different authentication arrangement; check your edition with Support before following these steps.

## Steps to connect Magento 2

1. In Magento Admin, open **System → Extensions → Integrations**. Open the integration agreed with Support, or choose **Add New Integration** for a new one.
2. For a new integration, enter a recognizable **Name** and contact **Email**. Use only the **Callback URL** and **Identity Link URL** supplied for your agreed authentication route; do not invent either address. Confirm your identity when Magento prompts you.
3. Open **API** and set the resources using [Magento 2 API resource access](/article/magento-backoffice-setting-api-permissions). Save the integration.
4. For a new inactive integration, choose **Activate**, review the requested access, then choose **Allow**. Store the displayed credentials securely and choose **Done**. Coordinate any reauthorization of an existing connection with Support first: it generates replacement tokens.
5. In Optiply, open **Settings → Integrations**. Wait for the source lists to load, then choose **Add a source** and search for **Magento 2**. If the matching source is listed, select it and choose **Next**.
6. At **Connect to system**, stop before submitting credentials. Support completes or directs the connection setup using the agreed authentication route. If **Contact us** is shown, use it. If a credentials form is shown, confirm the requested credential type with Support before entering it. Never put an OAuth consumer secret into an access-token field. If Magento 2 is missing, contact Support instead of selecting another connector.
7. After setup, return to **Settings → Integrations** and check the source name and **Connected** label. Check product, stock and order results separately with Support before using them for planning.

Adobe's [integration instructions](https://experienceleague.adobe.com/en/docs/commerce-admin/systems/integrations) explain the Magento Admin screen.

## Fields in Magento 2 connection setup

| Field or choice | Meaning |
| --- | --- |
| **Name**, **Email** | Identify the Magento integration and its contact. |
| **Callback URL**, **Identity Link URL** | OAuth exchange and account-link destinations for the agreed route; they are not your store URL. |
| **Store URL** | The Magento store address, such as `https://example.com`. |
| **Access Token** | A credential for the selected authentication route, not a Magento administrator password. |
| **Pull all sell orders?** | Off means completed orders only. Other eligible orders can be included when enabled; canceled orders are excluded. |
| **Use salable quantity?** | Selects the non-warehouse stock quantity route; confirm the intended quantity with Support. Warehouse source selection is separate. |
| **Connected** | Identifies a linked source, not confirmation that every record has arrived. |

## What you see when connecting Magento 2 worked

The linked source appears in Integrations with its name and **Connected** label. Magento authorization and Optiply linking are separate steps; authorizing Magento alone does not link your Optiply account.

## Limits of connecting Magento 2

OAuth-signed requests use **Consumer Key**, **Consumer Secret**, **Access Token** and **Access Token Secret**. A standalone bearer token is a different route and is disabled by default in current Magento versions. Do not enable standalone bearer access, anonymous API access or weaker administrator security to work around a connection error. Support must confirm the compatible route for your store.

## If connecting Magento 2 did not work

Wait if **Add a source** is disabled while lists load. For a missing source, rejected credentials or a missing linked source after setup, contact Support with the connector name and failing step, without secrets. For a Magento permission error, review the resource-access guide before requesting broader access. Reauthorization replaces credentials, so coordinate the replacement before retrying an existing connection.

## Related articles on Magento data

- [Magento 2 API resource access](/article/magento-backoffice-setting-api-permissions)
- [Magento non-warehouse data mapping](/article/integrations-data-mappings-public-magento-non-warehouse-hotglue)
- [Magento warehouse data mapping](/article/integrations-data-mappings-public-magento-warehouse-hotglue)
