Customer relationships, inventory and accounting serve different purposes. Define which system owns each type of data before connecting it to the store.
A B2B enquiry creates a CRM contact and deal. A confirmed order reaches the ERP for fulfilment, and the agreed accounting document reaches the accounting system. Stock flows back from the designated inventory source. Payment, fulfilment and document status remain distinct.
Contacts, leads, accounts and opportunities from forms and orders. Map standard and agreed custom fields, match existing records and configure API permissions. Purchase history gives sales staff context; it should not automatically create a new deal for every event.
Website forms, contacts, companies and deals with store context. Keep an existing form and send its fields to the CRM where appropriate. Before implementation, check available objects and automations in the account and agree contact-merging rules.
Sales involving a quote and follow-up: B2B enquiry → deal → sales task. Define when an order updates an existing deal and when it creates a new one so the pipeline remains meaningful.
ERP workflows for products, inventory and order fulfilment. Review installed modules, product variants and warehouses. Sync stock from the designated source; do not assume every installation has the same modules or API access.
Orders mapped to accounting documents with customers, items, payments and refunds. Distinguish QuickBooks Online from Desktop, which may need middleware. Agree tax and fee mapping and reconcile gross sales with net payments.
No. Assign an authoritative system and conflict rules for each field. Inventory may own stock, the store may own product copy, and the CRM may own the customer’s account manager.
Map them separately and reconcile results with the accounting team. Test gross amounts, processor fees and partial refunds; the technical connection does not determine accounting policy.
Tell us about your project and we'll figure out how we can help.
