Commerce integration guide
Square Online + UbiGrowth workflows
Square Online is the online store product in the Square ecosystem, connected to Square payments and catalogue. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Square Online part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a commerce workflow around Square Online 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 Order, Catalog Item, Customer, Location, Fulfillment, and Payment. Square Online shares the catalogue and customer directory with Square's in-person products, so an online order and a counter sale can belong to the same customer — or not, since card-present sales often carry no identity.
Square Online 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. Square Online 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 Square Online integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Square Online's.
Identity and matching
Square Online shares the catalogue and customer directory with Square's in-person products, so an online order and a counter sale can belong to the same customer — or not, since card-present sales often carry no identity.
Start here
Read online Orders with a pickup Fulfillment that has passed its ready time and alert the Location staff, since an uncollected pickup order is invisible on the point-of-sale screen the counter actually watches.
What this will not do
It will not separate online from in-person reporting cleanly. The shared catalogue is the point; segment on the fulfilment type instead.
The constraint to plan around
Catalogue changes propagate between the point of sale and the online store, so a workflow writing catalogue data affects the physical storefront too.
Build notes
What you actually have to reason about in Square Online.
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 |
|---|---|
| fulfillment type / state | pickup versus delivery, with pickup states invisible on the point-of-sale screen |
| location_id | the store the order belongs to |
| catalog object id | shared with the in-person point of sale |
| order source | distinguishes online from in-person within one order stream |
| customer_id | present online, frequently absent in person |
Authentication
Same Square OAuth and scope model as the wider platform, with online orders appearing in the shared Orders API rather than a separate one.
Events and delivery
Square webhooks cover order and payment events across both surfaces, so filtering on source is required to isolate online activity.
Workflow
How the Square Online 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 Square Online 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 Square Online workflow is allowed to write anything.
Step 01
Resolve the customer across channels
Decide how a customer in Square Online 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 Square Online workflow.
- 01
Decide which records Square Online 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 pickup alerting works, add prep-time accuracy so quoted ready times match reality and the alerts become rare.
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 Square Online 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
A pickup order is never collected and nobody noticed.
Cause
Pickup fulfilment state is not visible on the point-of-sale screen staff watch.
Fix
Alert staff on ready-time elapsed through a channel they actually monitor.
Symptom 02
A website price change appears at the counter.
Cause
The catalogue is shared between online and in-person.
Fix
Treat catalogue writes as affecting both surfaces, and confirm intent.
Symptom 03
Online and in-person reporting cannot be separated cleanly.
Cause
Both flow through the shared Orders API.
Fix
Segment on fulfilment type and order source rather than expecting separate streams.
What changes at scale
Shares Square's platform limits, with location iteration as the main multiplier. The same caching strategy applies.
Examples
What a working Square Online workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Store operations
With Square Online 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 Square Online 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.
- Catalogue changes propagate between the point of sale and the online store, so a workflow writing catalogue data affects the physical storefront too.
- Catalogue writes affect the physical storefront because the catalogue is shared. A price change intended for the website changes what the counter charges.
- When clean separation of online and in-person reporting is expected. The shared catalogue and customer directory are the point; segment on fulfilment type instead.
- Marketplace and platform policies constrain what can be automated around Square Online, 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
Square Online integration questions.
What records does a Square Online integration actually work with?
The primary records are Order, Catalog Item, Customer, Location, Fulfillment, and Payment. Square Online shares the catalogue and customer directory with Square's in-person products, so an online order and a counter sale can belong to the same customer — or not, since card-present sales often carry no identity.
What should the first Square Online workflow be?
Read online Orders with a pickup Fulfillment that has passed its ready time and alert the Location staff, since an uncollected pickup order is invisible on the point-of-sale screen the counter actually watches.
What will a Square Online integration not do?
It will not separate online from in-person reporting cleanly. The shared catalogue is the point; segment on the fulfilment type instead.
What is the main constraint to plan around?
Catalogue changes propagate between the point of sale and the online store, so a workflow writing catalogue data affects the physical storefront too.
What changes about a Square Online integration at scale?
Shares Square's platform limits, with location iteration as the main multiplier. The same caching strategy applies.
How does authentication work for Square Online?
Same Square OAuth and scope model as the wider platform, with online orders appearing in the shared Orders API rather than a separate one.
Does Square Online support webhooks, and can they be trusted?
Square webhooks cover order and payment events across both surfaces, so filtering on source is required to isolate online activity.
What is the risk of writing to Square Online?
Catalogue writes affect the physical storefront because the catalogue is shared. A price change intended for the website changes what the counter charges.
When is connecting Square Online the wrong call?
When clean separation of online and in-person reporting is expected. The shared catalogue and customer directory are the point; segment on fulfilment type instead.
What should a Square Online 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 Square Online 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 Square Online 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 Square Online, and who decides.
Connecting Square Online 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.