Integrations is where Bizuno connects to third-party services — payment processors, shipping carriers, e-commerce platforms, email marketing, tax automation, accounting sync. Each connector is managed here with credentials, sync settings, and a status indicator.
How to get there #
Menu: Admin → Integrations
Direct URL pattern: https://yourdomain.com/?bizRt=bizuno/admin/integrations
Integration categories #
| Category | Examples | What it does |
|---|---|---|
| Payment processors | Stripe, Authorize.Net, Square, PayPal | Charge credit cards and ACH from inside Bizuno. |
| Shipping carriers | UPS, USPS, FedEx, ShipStation, EasyPost | Real-time shipping rates and label printing. |
| E-commerce | Shopify, WooCommerce, BigCommerce | Sync orders, inventory, and customers. |
| Tax automation | Avalara, TaxJar, TaxCloud | Real-time tax calculation; auto-filing. |
| Email marketing | Mailchimp, Constant Contact, Klaviyo | Sync customer lists. |
| Accounting sync | QuickBooks, Xero (uncommon when Bizuno IS your accounting) | One-way or two-way GL sync. |
| Bank feeds | Plaid, Yodlee, direct bank OFX | Auto-import transactions for reconciliation. |
| CRM / tickets | HubSpot, Zendesk, Freshdesk | Customer data and support history. |
| Point of Sale | Square POS, Clover, Lightspeed Retail | Sync sales / inventory with register hardware. |
Anatomy of an integration #
Each connector on this screen has:
- Name and Status (Connected / Disconnected / Error).
- Credentials: API key, secret, OAuth token, webhook endpoint.
- Sync settings: direction (one-way or two-way), frequency, field mappings.
- Field mapping: how Bizuno’s fields correspond to the third-party’s fields.
- Logs: sync run history with success/failure.
- Test Connection button.
Setting up an integration #
- Open the connector’s row. Click Configure.
- Paste or generate credentials (API keys usually live in the third-party’s dashboard under Developers / API / Integrations).
- Click Test Connection. Don’t proceed until green.
- Map fields. Default mappings are usually sensible; customize only when needed.
- Pick sync settings — direction, frequency (real-time / hourly / daily), initial sync mode (all / recent / none).
- If bidirectional, pick Source of Truth for each domain (“Bizuno wins for inventory, Shopify wins for online-only fields”).
- Enable.
- Run a small initial sync; verify a few records manually in both systems.
Important: Two-way sync is powerful and dangerous. If both sides can edit the same record, you need clear source-of-truth rules or you’ll get loops, overwrites, and mystery edits. When in doubt, pick one side as authoritative and sync one-way.
E-commerce connector patterns #
Most bike shops with an online store use one of these patterns:
- Bizuno as source of truth — inventory, SKUs, prices live in Bizuno; push to Shopify/Woo. Orders pull back from online to Bizuno. Cleanest for a shop that does mostly in-person with online as a second channel.
- Shopify as source of truth — product data lives in Shopify (better product pages, variants, images); Bizuno is the back-office for accounting, purchasing, and in-store. Orders flow to Bizuno for fulfillment and financials.
- Split catalog — certain SKUs online-only, others in-store-only, shared inventory only for the overlap. Harder to manage but sometimes the right call.
Webhooks and scheduled sync #
- Webhooks — real-time push. When a Shopify order happens, Shopify pings Bizuno and the order appears within seconds. Requires your Bizuno install to be reachable over HTTPS.
- Scheduled polling — Bizuno fetches updates on a schedule. Simpler; latency equals the interval.
Credentials hygiene #
- Use API keys with the minimum scope the integration needs. Shopify’s “Private App” scopes should be exactly Products, Orders, Customers — nothing more.
- Rotate API keys annually or when the person who set it up leaves.
- Never paste credentials into support chats or screenshots.
When an integration breaks #
Status on this screen turns red. Typical causes and fixes:
- Credentials expired or rotated — re-enter API keys.
- Webhook URL changed (after a domain move) — update in the third-party’s dashboard.
- API version deprecated — the third party ended support for the old API version. Update Bizuno’s connector to the newer version.
- Rate limit exceeded — too many syncs per hour. Spread the schedule or upgrade the third-party plan.
- Field-mapping error — a new field on the third-party isn’t mapped; check the sync log for the exact field name.
Disconnecting #
- Click Disconnect.
- Bizuno stops syncing but retains all records on both sides as they are at disconnect time.
- Consider revoking the API key in the third-party’s dashboard so it can’t be re-enabled accidentally.
Tips for Ridgeline Cycles #
- Start with one integration at a time. Verify it’s behaving before adding another.
- For payment processing, reconcile processor deposits with Bizuno bank transactions weekly — integrations drift faster than monthly review catches.
- Document, per integration, the person responsible, the third-party admin account it’s tied to, and the key rotation schedule. Put the document in Document Control (Category 7).
- Test the integration after every Bizuno update. Core upgrades occasionally change API signatures.
Where to go next #
- Taxes, Shipping & Payment Methods — payment methods map to integration processors; shipping methods to carrier APIs.
- Modules & Extensions — some integrations ship as extensions with additional configuration there.
- Audit Log — sync errors and credential changes log here.