Customer and item mapping
We match store customer and product identifiers with the intended Zoho Books contacts and items. Guest orders, variants and items without a usable SKU need named rules rather than automatic duplicate creation.
WooCommerce and Zoho Books integration
Connect WooCommerce sales with a Zoho Books workflow approved by your bookkeeper. We map customers, items and transaction records, define how corrections are represented and provide checks that make missing or repeated entries visible.
What the connection includes
We agree on the records, fields and operating rules before connecting WooCommerce and Zoho Books. The scope below defines the work to review together.
- Solution
- Integrations
- Connected systems
- WooCommerce + Zoho Books
- Data flow
- WooCommerce supplies agreed sales and refund data to Zoho Books. The bookkeeper owns accounting treatment, tax mappings and posting policy; the connection does not change store prices, issue refunds or alter inventory unless separately authorized and scoped.
Invoices, payments and corrections
The accounting owner decides which sales record to create and when. We map the approved invoice or other supported transaction route, with separate handling for payment records, cancellations and credit notes where included.
Reconciliation inputs
Order references and destination identifiers remain traceable. The scope defines how discounts, shipping, fees and currencies are supplied, and which rejected or incomplete records need review before posting.
What we need to scope the work
Approved bookkeeping rules
Your accountant or bookkeeper supplies the chart-of-accounts mapping, tax-code decisions and posting policy. Norml implements the agreed data connection; accounting and jurisdiction-specific tax advice are not included.
Organization and payment sources
Confirm the Zoho Books organization, region, currency settings and relevant payment gateways. Gateway settlement fees may need another data source and are not assumed to exist in each WooCommerce order.
A historical boundary
Agree on the first transaction to include and how existing entries will be recognized. Historical imports and changes to already-posted records require a reconciliation plan before live synchronization.
How we build and check the connection
Review representative transactions
Select an ordinary sale, a discounted order and a refund with the bookkeeping owner. Define their destination records and expected totals before choosing the connector or API route.
Implement and compare
Test contact matching, line items and supported payment or credit-note operations. Compare the resulting records against the approved examples and identify any unsupported cases.
Reconcile and hand over
Check the agreed import window and retry behavior. Document exceptions, posting ownership and the review process for later refunds or changes that arrive after the original sale.
Related services.
Integration questions
Does every order create an invoice?
Only if that is the approved accounting model. The bookkeeper determines whether and when an invoice or another supported sales record is appropriate. A paid store order is not treated as an unpaid invoice by default.
How are refunds and payment fees handled?
They need separate mappings and source data. Zoho Books supports credit-note operations, while gateway fees may require settlement information outside the order. We test the cases named in your scope.
Can it handle multiple currencies?
We check the organization’s configuration, plan and selected route before including foreign-currency transactions. The accounting owner defines the expected currency treatment and approves the test results.
Will it calculate the correct tax automatically?
The project implements an approved field and tax-code mapping. It does not establish the correct tax treatment for your business or guarantee that store tax settings match every bookkeeping requirement.
Share your website and one example of the record you need in Zoho Books. We will review the existing setup, agree on the data mapping and identify the access needed.