BSimple connects the operational work of your business with the accounting, ecommerce, payment and signing tools around it. Use a native integration where one exists, or use the BSimple Public API when your workflow needs a custom connection.
XeroAccounting integration
MYOBAccounting workflows
WooCommerceOnline orders and stock
ShopifyStorefront operations
QuickBooks OnlineAccounting connections
eWAYPayment workflows
StripePayment workflows
PayPalPayment workflows
Choose the right connection
If your main requirement is accounting, start with the Xero integration or ask us about MYOB. If you sell online, connect your ecommerce workflow to BSimple so orders and stock stay aligned. If you need a customer portal, CRM connection, external ordering site or internal automation, the Public API gives your developers scoped access to selected BSimple data.
Xero integration
BSimple manages inventory, ordering and operational workflows while Xero remains the accounting system of record. The integration helps keep contacts, invoices, payments, inventory and purchase-order information aligned. Read the Xero integration guide for the workflow and accounting boundary.
MYOB integration
Australian businesses using MYOB can connect their customer, invoice and inventory workflows to BSimple. Confirm the current MYOB connection requirements with BSimple before implementation, because accounting-provider scopes and connection rules can change.
Ecommerce and ordering
Connect your ecommerce or external ordering workflow to BSimple when customers need accurate product and availability information. BSimple can act as the operational layer for inventory, customer records, purchasing and invoicing while your storefront remains focused on selling.
Payments and electronic signing
BSimple can work with payment and electronic-signing services as part of broader business workflows. These connections are separate from the Public API: the API does not currently provide payment processing, invoice sending or file attachments.
The Public API for custom systems
The BSimple API overview explains the business use cases. The developer documentation contains the endpoint and scope reference, while the getting-started guide shows how to create a key and make a first request.
The current public API can provide scoped access to leads, customers, inventory, suppliers, locations, PAR and reorder data, stocktakes, purchase orders, transfers and invoices. It can also create draft invoices. Read the draft invoice guide and inventory and stock guide for practical examples.
MCP for AI assistants
If your team wants to ask questions about live operations in natural language, BSimple MCP connects an MCP-compatible assistant to approved, read-only BSimple data. It is useful for questions such as “which products are below PAR?”, “what stock is at this location?” or “which purchase orders are open?”.
MCP is a controlled assistant interface, not a replacement for the REST API. It uses a separate environment-aware bearer connection, the user's scoped BSimple permissions and a fixed set of read-only tools. It cannot create orders, edit inventory, approve or send invoices, run SQL, browse arbitrary URLs or access another account. Developers who need deterministic writes, scheduled synchronisation or a customer-facing portal should use the API reference instead.
For an AI consumer, the MCP guide explains the endpoint, key handling, Dev/production separation, tool boundaries and instructions for giving grounded answers without exposing credentials.
Which path is right for you?
- Business owner or operations team: start a free trial to manage inventory, orders, customers and invoices in a real BSimple account.
- Developer or integration team: use the Public API for a portal, ordering site, CRM, ecommerce connection or automation.
- AI assistant user: use BSimple MCP for read-only operational questions through a compatible client.
Need a connection that is not listed?
Tell us which systems you already use and what data needs to move. We can help determine whether a native integration, the Public API, or a different workflow is the best fit.