// bitta apps · services
Business Central Integrations
Connect orders, inventory and finance across Shopify, CRM, EDI and custom systems, with clear ownership when a transaction needs attention.
An integration is complete when an order can reach fulfillment, a refund reaches the ledger, and your team can explain any difference between systems. We scope the full workflow: which application owns each record, how records match, when synchronization runs, and who handles exceptions. We first assess a supported standard connector or existing partner app, then scope middleware or AL extensions for the remaining gaps. Discovery establishes volumes, access, licensing and support responsibilities before a fixed-price build proposal.
What can we connect to Business Central?
Shopify & e-commerce
Evaluate Microsoft's Shopify connector for products, inventory, customers, orders, fulfillment and refunds. Define location mapping, stock calculations, taxes, shipping, discounts and payout reconciliation. Test partial shipments and returns before enabling automatic processing.
Salesforce & CRM
Accounts, contacts, opportunities, and quote-to-cash flows between Salesforce and Business Central, bi-directional with clear conflict rules.
Azure Data Services
Scope API or connector-based exports into your Azure or Fabric reporting architecture. Agree refresh frequency, historical backfill, incremental changes and financial reconciliation; real-time streaming is not assumed.
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
Trace one complete workflow
Follow order capture, customer and SKU matching, availability, shipment, invoice, payment and refund. Collect normal and exception examples from the people who run them.
- 02
Agree ownership and scope
Document sync direction, source of truth, matching keys, field mappings, expected latency and acceptance totals. List connector subscriptions, custom work and out-of-scope systems separately.
- 03
Build recovery into the flow
Implement duplicate protection, bounded retries, an exception queue and controlled replay where the platform permits. Assign an alert owner and protect application credentials.
- 04
Reconcile under realistic load
Test repeated messages, missing SKUs, API limits, partial shipments, cancellations and refunds. Compare counts and amounts in both systems and rehearse recovery from a failed run.
- 05
Cut over with an operating runbook
Agree the handoff window and opening backlog. Deliver monitoring, mapping documentation, recovery steps and support ownership so finance and operations can run the connection after launch.
Frequently asked
What does Microsoft's Shopify connector support?+
Microsoft documents synchronization for products, customers, inventory, orders and fulfillment, plus configurable refund handling and Shopify Payments payout information. Availability depends on your environment and configuration. These capabilities still need mapping, testing and a reconciliation process for your business. Microsoft's Shopify connector documentation →
Do we need a custom Shopify integration?+
Start with Microsoft's standard Business Central Shopify connector and a fit-gap review. Custom development is appropriate only for a defined requirement the connector or a suitable app cannot cover. Scope shop count, product ownership, warehouse mapping, refunds and financial reconciliation before deciding. Business Central and Shopify workflow assessment →
How much does a Business Central integration cost?+
The written quote depends on systems, entities, directions, transaction volumes, exception handling and data cleanup. Connector subscriptions, implementation and ongoing monitoring are separate cost categories. Bring sample transactions and an application list to the discovery call so we can establish whether standard configuration or a scoped build is appropriate. How scope and pricing are established →
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. 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 an owning system per entity and explicit rules for conflicting changes. Stable matching keys and duplicate protection prevent repeated messages from creating duplicate business transactions. Unresolved conflicts go to review; financial records should not be silently overwritten by whichever update arrived last.
Do you monitor integrations after go-live?+
Yes, under a separately agreed support scope covering relevant job queues, integration alerts and telemetry. The agreement defines monitoring frequency, response targets and who reviews failed or unmatched transactions. Monitoring reduces detection time but does not guarantee every failure is caught before a user notices. Support & managed services →