exact online woocommerce integration projects succeed when teams prioritize clear data ownership, robust mapping, and practical reconciliation rules from day one. This article expands on product, customer, order, tax, payment, and inventory boundaries; describes sync direction and duplicate prevention; and gives hands-on guidance for error handling, permissions, staging, reconciliation, and long-term maintenance.
Why Map Data Carefully Before You Integrate
Exact Online is an accounting-centric platform with ledgers, VAT codes, debtor records, and inventory items that do not always align with WooCommerce structures. Poorly planned mappings create reconciliation gaps, duplicate customers, VAT mistakes, and stock mismatches. A precise mapping eliminates guesswork and provides predictable results for finance and warehouse teams.
Primary Data Domains and Decision Criteria
- Products/Items — Determine whether WooCommerce SKUs become Exact Online Items, bundled/assembled items, or non-stock services. Include attributes: SKU, EAN/UPC, inventory tracking flag, purchase price, sales price, and default ledger accounts. Consider separate item records per warehouse only if you operate multiple physical stock locations that Exact Online must recognise.
- Customers/Contacts — Map WooCommerce billing/shipping profiles to Exact Online debtors or contacts. For B2B customers, capture VAT numbers and company-level debtor records and attach contact persons as secondary records. For B2C, consider grouping by unique email but be aware that email reuse may cause merges you do not want.
- Orders/Invoices — Decide sync direction: push WooCommerce orders to Exact Online as sales orders (for pick/pack workflows) or as finalized invoices (for immediate accounting). If you capture payment on checkout, map that to Exact Online payment postings; otherwise post only invoices and reconciliate bank settlements later.
- Taxes — Map WooCommerce tax classes and geo rules to Exact Online VAT codes. Define whether product prices are tax-inclusive in WooCommerce and translate those values into Exact Online with explicit VAT rates and rounding logic to avoid cent-level differences.
- Payments and Fees — Determine how to represent payment gateway fees and refunds. Often fees are posted as bank fees or cost-of-sales adjustments in Exact Online and refunds create negative invoice lines plus contra postings to a payment clearing account.
Inventory Boundaries and Sync Direction
Decide where inventory is mastered. Typical patterns:
- WooCommerce Master: Manage stock on the storefront and sync quantities to Exact Online for reporting only. Use when commerce platforms drive real-time sales and Exact Online is a back-office ledger.
- Exact Online Master: Manage stock across multiple sales channels in Exact Online and push stock levels to WooCommerce. Use when Exact Online handles purchasing and multi-channel inventory allocation.
- Hybrid: Keep transactional stock adjustments in the originating system and reconcile periodically. Clearly document allowed operations from each side to avoid conflicting updates.
Implementation Steps With Practical Detail
-
Inventory and Requirements Audit
Make a complete matrix listing every WooCommerce and Exact Online field you will use, noting mandatory Exact Online fields such as accounts and VAT codes. Include business rules for bundles, composite SKUs, serial-numbered items, and lot tracking if used.
-
Choose Connector or Build Custom
Evaluate commercial connectors for support of multi-currency, multi-warehouse, and custom tax mappings. If you build custom, use Exact Online API docs at https://developers.exactonline.com and the WooCommerce REST docs at https://woocommerce.com/document/. Implement OAuth with least-privilege scopes and refresh token handling. Remember APIs, plans, regions, and connector interfaces can change.
-
Design Field Mapping and Transformation
Create a canonical transformation layer: normalize SKUs, standardise customer names, calculate per-line taxes the same way Exact Online expects, and store currency and exchange rates where needed. Define rounding (per-line vs per-invoice) and record the rule so finance can reconcile differences.
-
Staging, Sandboxes, and Backups
Validate every scenario in a WordPress staging environment and an Exact Online sandbox. Keep database snapshots and CSV exports of key entities. Verify full restore workflows periodically. Staging should replicate real-world tax zones, payment methods, and high-volume event patterns.
-
Idempotent Syncs, Batching, and Webhooks
Prevent duplicates by recording Exact Online IDs in WooCommerce product and order meta. Use idempotency keys for writes and process webhooks into a reliable queue with retry logic and exponential backoff to handle transient errors and API rate limits.
-
Reconciliation and Audit Trails
Automate daily reconciliation reports comparing WooCommerce gross sales, tax, shipping, refunds and net to Exact Online invoices and bank postings. Retain API request/response logs with timestamps for the audit period required by your jurisdiction.
Duplicate Prevention and Idempotency
Key techniques to avoid duplicates:
- Store Exact Online entity IDs in WooCommerce meta and never create a new Exact Online record if that ID exists.
- Use a composite external reference (order ID + connector ID + timestamp) when writing invoices to Exact Online.
- Validate on creation whether an Exact Online invoice exists with the same external reference and amount before attempting a create call.
Error Handling, Monitoring, and Alerts
Design error flows that categorise issues as transient (rate limits, timeouts) or permanent (validation errors, permissions). Implement:
- Automated retries with exponential backoff for transient errors.
- Human-review queues for validation failures (missing VAT code, customer validation errors).
- Alerting for repeated 429/5xx responses or growing backlogs in the sync queue.
Permissions, Tokens, and Security
Grant only the scopes required by your connector. Rotate and securely store refresh tokens. Monitor for consent revocation and implement health checks that proactively refresh tokens before expiry. Capture and store customer consent where legal frameworks require explicit permission for contact and data sync.
Reconciliation Procedures and Finance Workflows
Reconciliation is ongoing, not one-off. Best practices:
- Produce per-day and per-period reconciliations that list orders, invoices, payments, refunds, and ledger postings with cross-references to external IDs.
- Flag mismatches where amounts differ beyond a configured tolerance and route them to finance or operations for investigation.
- Keep short access to raw API logs and transformation records to rebuild a particular transaction if needed.
Maintenance, Changelogs, and Governance
Maintain a proactive schedule: review Exact Online and WooCommerce release notes weekly, test connector upgrades in staging, and schedule maintenance windows. Document governance: who can change mappings, who approves connector updates, and how to handle new tax rules or business lines.
Accessibility and Responsive Admin Tools
Build admin UIs that surface sync health, detailed error messages, and reconciliation reports. Ensure keyboard navigation, high-contrast indicators, and mobile layouts for operations staff who review issues on tablets or phones. Provide CSV export and printable reports for finance teams and auditors.
Conclusion
A reliable Exact Online WooCommerce integration combines careful mapping, clear ownership of inventory boundaries, idempotent and batched syncs, robust error handling, and recurring reconciliation procedures. Test thoroughly in staging and sandboxes, log and retain audit trails, and enforce least-privilege permissions. APIs, plans, regions, and connector interfaces can change. DigitalWebTutor is independent; DominoPress is a separate entity. Use the official docs at https://developers.exactonline.com, https://www.exact.com, and https://woocommerce.com/document/ to stay current with platform updates and integration best practices.
