Payments
Stripe
Include payment links on invoices so customers can pay online, with payment activity connected to Abbey’s invoice workflow.
Requires a connected Stripe account and payment-method configuration.
Integrations & extensibility
Connect the tools.
Keep the context.
Your ERP should connect the work around it. Abbey brings payments, communications, ecommerce, product content, printing, and AI assistants into the workflows your team already runs.
Built around practical workflows
Connections with a job to do.
Each connection has a defined scope. Our team can help you map the right provider, licensing, and setup to your operation.
Email & calendar
Google & Microsoft
Connect supported Google or Microsoft mailboxes and calendars. Bring email activity and meetings into the customer context, and connect shared inboxes for team workflows.
Activity Sync and mailbox workflows require provider authorization and configuration.
Ecommerce
Shopify
Publish products and inventory from Abbey to connected Shopify stores. Review store-specific product mappings and sync activity alongside the ERP product record.
Requires Shopify licensing and a connected store. Confirm field ownership and sync direction during setup.
Printing
PrintNode
Send Abbey print jobs to connected printers, bringing document and warehouse printing into the same operational workflow.
Requires PrintNode setup, a running client, and configured printers.
Order import & product content
AutoQuotes
Import AutoQuotes order documents and enrich products with descriptions and pictures through the AutoQuotes API.
Order import and API access are separate licenses. API content requires an AutoQuotes subscription key.
Catalog setup & customer exports
J&M Catalog
Configure your J&M distributor code and prepare customer and customer-location listings for catalog workflows.
Requires J&M Catalog licensing. Current scope includes setup and exports; confirm additional connectivity with our team.
Third-party services have their own accounts, terms, and fees. Available integrations vary by Abbey license and provider configuration. Provider names identify supported connections and do not imply endorsement.
The AI-native difference
Your tools share
a business foundation.
Abbey’s assistant, custom apps, and connected AI clients can work with the same authorized business capabilities.
Explore AI & voiceCompatible assistants through MCP
Connect approved AI clients, including compatible ChatGPT setups, to authorized customer lookup, order history, pricing, inventory, and order preparation. Authentication, permissions, and confirmation requirements remain in place.
APIs & custom apps
Build integrations and focused workspaces around Abbey’s business APIs. Custom apps use the viewer’s permissions; individual API capabilities and write rules are enforced by the platform.
Plan the connection, not just the connector
Start with the handoff you want to improve.
Map the workflow
Identify the records, people, and systems involved. Decide which system owns each field and where a person needs to review the result.
Confirm the scope
Review supported operations, licensing, provider permissions, field mappings, and the direction of each sync.
Validate the outcome
Test with representative records, inspect logs and results, and agree on exception handling before enabling the workflow broadly.
Let’s talk about your operation
See Abbey work through
your next order.
Bring an example from your operation. We’ll walk through order entry, purchasing, fulfillment, and billing with your team.