// bitta apps · services
Integrations
Integrations that don't drop orders on Black Friday — Business Central to Shopify, Salesforce, Azure Data Services, Power Platform, EDI, and custom APIs.
Most businesses run on more than one system. Business Central is the ledger of record, but orders come from e-commerce, customer data lives in a CRM, analytics runs in the Azure data stack, and automations run across Power Platform. We design, build, and maintain the integrations that keep those systems in sync — every one ships with idempotent processing, retry and replay paths, dead-letter handling, and reconciliation reports your finance team and auditor will accept.
What can we connect to Business Central?
Shopify & e-commerce
Orders, customers, items, fulfillment, and refunds between Shopify (or other storefronts) and Business Central, with inventory reservation patterns that actually hold up on Black Friday.
Salesforce & CRM
Accounts, contacts, opportunities, and quote-to-cash flows between Salesforce and Business Central — bi-directional with clear conflict rules.
Azure Data Services
Stream Business Central data into Azure Data Lake, Synapse, or Fabric for analytics and reporting, using Dataverse, Event Grid, or direct API exports.
Power Platform
Power Automate flows, Power Apps front-ends, and Dataverse-backed scenarios around Business Central — with governance and ALM built in.
EDI
Inbound and outbound EDI transactions (850, 810, 856, 855, 997 and industry equivalents) with trading-partner onboarding and exception handling.
Custom APIs
REST/OData integrations against bespoke internal systems, partner portals, or third-party SaaS — including AL API pages, webhooks, and service bus patterns.
How we work
- 01
Integration discovery
Map systems, data flows, volumes, and failure modes before we write a line of code.
- 02
Design & contract
Document entities, sync direction, primary system, and conflict rules — signed off before build.
- 03
Build & instrument
Implement with retries, idempotency keys, dead-letter handling, and telemetry you can actually watch.
- 04
UAT with real data
Run against production-like volumes, validate reconciliation reports, and rehearse failure recovery.
- 05
Cutover & handoff
Go-live with monitoring in place and a runbook your team can operate.
Frequently asked
Can you work with our existing integrations?+
Yes. We regularly take over middleware built by other partners, iPaaS flows (Boomi, MuleSoft, Workato), or homegrown jobs. We audit the current state, stabilize what matters, and migrate or rebuild only where the business case is clear.
Do you support Power Automate and Azure Logic Apps?+
Yes. We use both where they fit — Power Automate for business-user-owned automation, Logic Apps for higher-volume or more governed scenarios — and we're equally comfortable in AL, Functions, or Service Bus when the workload demands it.
How do you handle bi-directional sync and conflict resolution?+
We define a primary system per entity, use deterministic keys, track last-modified timestamps, and apply explicit conflict rules (last-write-wins, primary-wins, or quarantine). Every integration ships with an idempotent design and a replay path so you can always reconcile.
Do you monitor integrations after go-live?+
Optionally, yes — under an ongoing support agreement that covers integration health checks, job queue monitoring, and telemetry review, so failures are caught before users report them. Support & managed services →