On the other end Acumatica's own route What gets built around it
A Shopify or Shopify Plus store, including B2B and POS Acumatica's Shopify connector: orders, inventory, pricing, customer data and fulfillment, with returns and exchanges handled as ERP transactions. Retire any older app still writing stock or orders to the same store before switching the connector on. Two writers is how counts start flipping.
A BigCommerce store selling B2B Acumatica's BigCommerce connector: sales and purchase orders, inventory, customer groups, company hierarchies and payment terms. Decide whether customer groups and terms are edited in Acumatica or in BigCommerce. Editing both ends invites one to undo the other.
Amazon Seller Central, FBA or FBM Acumatica's Amazon connector: FBA orders arrive as invoices with their fees and payments, FBM orders get picked and shipped from Acumatica. Walmart, Etsy and WooCommerce run through partner integrations. A channel with no current option gets a custom build on the Acumatica API. A separate CRM such as Salesforce or HubSpot A Marketplace connector, or Acumatica's built-in CRM in place of the separate one. Field-level rules: which system owns the billing address, the credit terms, the account owner. A connector that syncs whole records can't tell.
A warehouse, shop floor or field service tool older than your Acumatica rollout Import scenarios for file feeds, or the contract-based REST API with push notifications. A file feed that skips rows it can't load. The record is missing in Acumatica, and nobody hears about it.
Retail trading partners that require EDI EDI providers listed on the Acumatica Marketplace. Each partner's own document rules. Our Acumatica Marketplace page covers how to vet those listings.