Commerce integration guide
Adobe Commerce + UbiGrowth workflows
Adobe Commerce is Adobe Commerce, an enterprise commerce platform owning catalogue, orders, and customer data. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Adobe Commerce part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a commerce workflow around Adobe Commerce with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Product, Order, Customer, Store View, Website, Quote, and Invoice. Adobe Commerce nests Website, Store, and Store View, and product attributes can be overridden at each level. The same SKU has different names and prices depending on the scope you query.
Adobe Commerce is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Commerce platforms generate a continuous stream of events, and most merchants use almost none of it. Adobe Commerce records what was ordered and by whom, but the follow-up, retention, and service work that should follow from that record usually happens in a different tool with a different view of the customer.
The result is that the same customer is treated as new by marketing, as an order number by fulfilment, and as an unknown by support, which is exactly the experience that erodes repeat purchase rates.
You're likely here because
- Order data and customer follow-up live in separate tools
- Support answers order questions without order context
- Lifecycle campaigns run against stale exported segments
Record model
What a Adobe Commerce integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Adobe Commerce's.
Identity and matching
Adobe Commerce nests Website, Store, and Store View, and product attributes can be overridden at each level. The same SKU has different names and prices depending on the scope you query.
Start here
Read Orders per Store View that failed payment capture and route them with the customer's prior order history, so a repeat buyer with a declined card is handled differently from a first-time failure.
What this will not do
It will not be fast to query. Adobe Commerce's data model is deep and its indexers govern read performance, so design the workflow around indexed reads rather than broad catalogue queries.
The constraint to plan around
Adobe Commerce deployments are heavily customized and frequently self-hosted with extensions that alter core behaviour, so the REST API surface differs per installation.
Build notes
What you actually have to reason about in Adobe Commerce.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| store view / website scope | attributes are overridable at each level, so the same SKU differs by scope |
| entity_id vs increment_id | internal key versus the order number customers quote |
| order state vs status | state is the system lifecycle, status is the customer-visible label mapped onto it |
| attribute set | decides which attributes a product carries |
| updated_at | the sync cursor, subject to indexer lag |
Authentication
Integration tokens or OAuth against the installation, with ACL resources per API. Self-hosted deployments carry their own version, extensions, and network posture.
Events and delivery
Message queues and observers are the extension points; webhook availability depends on the deployment. Most Magento integration logic lives inside the application.
Workflow
How the Adobe Commerce workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read order and customer state
Connected Adobe Commerce data provides the real order, customer, and fulfilment state rather than a periodic export.
Step 02
Resolve the customer
The customer is matched across order, marketing, and support systems using a defined rule, including the ambiguous case.
Step 03
Trigger from a real event
Follow-up is driven by an actual order or fulfilment event, so the message matches the customer experience.
Step 04
Run the lifecycle action
Post-purchase, exception, or repeat-purchase follow-up runs with the product and timing context attached, under review while it is being proven.
Design decisions
The commerce decisions this connection forces.
Each of these has to be settled before the Adobe Commerce workflow is allowed to write anything.
Step 01
Resolve the customer across channels
Decide how a customer in Adobe Commerce is matched to the same person in marketing, support, and any other channel, including what happens when the match is ambiguous.
Step 02
Treat order state as the trigger
Follow-up should be driven by real order and fulfilment state rather than by a periodic export, otherwise the message and the customer experience diverge.
Implementation path
How to implement the Adobe Commerce workflow.
- 01
Decide which records Adobe Commerce owns and which the workflow may act on, starting read-only.
- 02
Define the customer identity match across order, marketing, and support systems before enabling any follow-up.
- 03
Pick one lifecycle moment — post-purchase, fulfilment exception, or repeat-purchase timing — and instrument only that.
- 04
After payment-failure routing works, add customer-lifetime context so a repeat buyer with a failed card is treated differently from a first-time failure.
Governance
Controls that matter.
Control 01
Order, refund, and fulfilment changes require explicit authorization rather than automated convenience.
Control 02
Customer messaging honours consent, preference, and channel rules.
Control 03
Payment and personal data stay in the systems that already govern them, at scoped access.
Failure modes
How a Adobe Commerce integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
The same SKU reports different names and prices.
Cause
Attributes are overridden per store view and the query did not specify scope.
Fix
Always query with explicit store scope and state which scope a report covers.
Symptom 02
Queries are far slower in production than in testing.
Cause
Indexers and data volume differ, and the model is deep.
Fix
Design around indexed reads and test against production-scale data.
Symptom 03
A simple update produces unexpected side effects.
Cause
Extension observers run on save and can do anything.
Fix
Enumerate installed extensions on the target instance before writing.
What changes at scale
Self-hosted performance is the customer's infrastructure. Bulk async APIs exist for volume and should be used rather than iterating the REST endpoints.
Examples
What a working Adobe Commerce workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Commerce operations
With Adobe Commerce connected, follow-up runs against real order and customer state rather than a segment exported last month.
Post-purchase lifecycle
A specific order event in Adobe Commerce triggers follow-up with the product and timing context attached, instead of a generic scheduled campaign.
Limitations and considerations
What to validate before you depend on this.
- Adobe Commerce deployments are heavily customized and frequently self-hosted with extensions that alter core behaviour, so the REST API surface differs per installation.
- Writes trigger observers installed by extensions, which can do anything. On a heavily extended store the effects of a simple update are not knowable from the API alone.
- When query performance matters. The data model is deep and indexer-dependent, so broad queries are slow in ways that surprise teams from lighter platforms.
- Marketplace and platform policies constrain what can be automated around Adobe Commerce, particularly for customer contact; check the rules before designing the workflow.
- Order, refund, and fulfilment writes carry direct customer and financial consequences and need explicit authorization.
FAQ
Adobe Commerce integration questions.
What records does a Adobe Commerce integration actually work with?
The primary records are Product, Order, Customer, Store View, Website, Quote, and Invoice. Adobe Commerce nests Website, Store, and Store View, and product attributes can be overridden at each level. The same SKU has different names and prices depending on the scope you query.
What should the first Adobe Commerce workflow be?
Read Orders per Store View that failed payment capture and route them with the customer's prior order history, so a repeat buyer with a declined card is handled differently from a first-time failure.
What will a Adobe Commerce integration not do?
It will not be fast to query. Adobe Commerce's data model is deep and its indexers govern read performance, so design the workflow around indexed reads rather than broad catalogue queries.
What is the main constraint to plan around?
Adobe Commerce deployments are heavily customized and frequently self-hosted with extensions that alter core behaviour, so the REST API surface differs per installation.
What changes about a Adobe Commerce integration at scale?
Self-hosted performance is the customer's infrastructure. Bulk async APIs exist for volume and should be used rather than iterating the REST endpoints.
How does authentication work for Adobe Commerce?
Integration tokens or OAuth against the installation, with ACL resources per API. Self-hosted deployments carry their own version, extensions, and network posture.
Does Adobe Commerce support webhooks, and can they be trusted?
Message queues and observers are the extension points; webhook availability depends on the deployment. Most Magento integration logic lives inside the application.
What is the risk of writing to Adobe Commerce?
Writes trigger observers installed by extensions, which can do anything. On a heavily extended store the effects of a simple update are not knowable from the API alone.
When is connecting Adobe Commerce the wrong call?
When query performance matters. The data model is deep and indexer-dependent, so broad queries are slow in ways that surprise teams from lighter platforms.
What should a Adobe Commerce integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Adobe Commerce to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can follow-up be triggered by Adobe Commerce order events?
Yes, and it should be. Follow-up driven by real order and fulfilment state is materially more accurate than a periodic exported segment.
Can the workflow change orders or issue refunds?
Those actions carry direct customer and financial consequences and require explicit human authorization rather than automated convenience.
How is the same customer recognised across channels?
Through an identity match rule you define, including what happens when a match is ambiguous. Resolution is rarely perfect, so design for the ambiguous case.
How this access is governed
What ARIA is allowed to do in Adobe Commerce, and who decides.
Connecting Adobe Commerce is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.