Magento price monitoring that respects your price scope

Adobe Commerce, still widely called Magento, connects through an integration you create and authorise inside your own admin. Products of every type come in with their SKUs, attribute sets, custom attributes and prices. Competitor prices, promotions and below-MAP listings flow back against each SKU. Anything written to the store is written at the price scope and store view it belongs to, and only for rules where you have enabled it.

What connecting Adobe Commerce does

Magento catalogues are usually the most structured of any platform and the most complicated to price. SKU is required and unique, which makes reconciliation clean. Custom attributes usually hold the identifiers matching wants. But prices can be scoped globally or per website, special prices carry date ranges, and configurable products hold their price on the children. A connection that ignores any of that will eventually write the right number to the wrong place.

What data flows in each direction

How to connect Adobe Commerce or Magento

1. 1

   Create an integration in the admin

   In your Magento admin, create a new integration and grant it access to catalogue and product data only. Leave sales and customer resources unchecked. Activate it, and the admin issues the credentials.

2. 2

   Enter the credentials and base URL

   Open Integrations in your account, choose Adobe Commerce, and paste the store base URL and credentials. The connection test reports what it can read, so a missing resource shows up before you import anything.

3. 3

   Map identifier attributes

   Tell us which custom attributes hold UPC or EAN, manufacturer part number and brand. This is the highest-value five minutes of the setup, because it decides how much of the catalogue matches without review.

4. 4

   Choose scope and store views

   Select which website and store view a monitored price belongs to. Multi-site installs monitor each context separately, so a UK store view is never compared against a US listing.

5. 5

   Import, review, and pick destinations

   Import all or part of the catalogue, confirm matches by confidence score, then decide between alerts, a review queue, CSV or API export, and write-back.

Which identifiers Magento price monitoring matches on

Matching runs at child SKU level and uses whichever identifiers your attribute set actually carries.

• UPC, EAN or GTIN attribute. Exact join first. On a well-maintained attribute set this resolves the bulk of a catalogue with no review at all.
• Manufacturer part number and brand. Both are usually attributes rather than core fields. Map them and they carry the categories where barcodes are missing, which in Magento tends to mean parts and industrial lines.
• SKU. Unique and required in Magento, which makes it the reliable key for exports, reconciliation and write-back, even though it never matches a competitor listing.
• Name, attributes and image. The scored fallback described in the product matching guide, used when nothing is shared.

Writing prices back without breaking your scopes

A rule writes either the price or the special price, at the scope you chose during setup. Writing special price is the safer option on most installs: the base price stays untouched, the change is visibly a promotion, and reverting is a matter of clearing the field. Every write is logged with the old value, the new value, the rule, the scope and the response from the store, and a rejected write is marked failed rather than counted as applied.

What this integration does not do

• It does not install an extension or run any code on your server.
• It does not read orders, customers, quotes or invoices.
• It does not create, delete or restructure products, attribute sets or categories.
• It does not touch catalogue price rules, cart price rules or tier pricing. If those own a price, keep write-back off for the affected SKUs and use a review queue.
• It does not manage stock, shipping or tax configuration.

The same connection works for Adobe Commerce and Magento Open Source, on-premise or cloud-hosted, as long as the admin is reachable from the internet. Where it is not, or where an ERP owns price rather than the storefront, take a scheduled CSV over SFTP instead. Both routes are on every plan, and both produce the same change history. For the wider picture, see ecommerce price monitoring and all integrations.