Products and inventory
Identify the source of truth for SKUs, variants, prices, stock, and location information. Confirm direction, frequency, and how exceptions are handled.
CONNECT THE WORK, CAREFULLY
Make your systems work together with a clear plan.
Assess the connections between your website, booking, POS, payments, and customer tools. Each supported integration has a specific scope and data flow.
01
Define what needs to move.
A connector name alone does not explain whether it supports your operation.
Orders and payments
Check order status, cancellations, refunds, transaction references, and fulfilment. Payment settlement and order completion are different events.
Customers and permissions
Review which fields should move and why. Marketing consent, sensitive information, and staff access need explicit handling rather than automatic copying.
02
Verify before relying on it.
Integration work is quoted only after the particular platforms and requirements are reviewed.
Compatibility
Confirm platform editions, available interfaces, supported apps, required subscriptions, and provider permissions.
Test cases
Use representative records, an update, a cancellation, and an error. Decide how staff detect and correct failed synchronisation.
Ownership and support
Document account access, data ownership, maintenance responsibility, and the escalation route when one provider changes its system.
Useful answers.
Do all listed POS systems connect to my website?
No. We verify the specific combination before offering an integration.
Does Business HQ connect to my bank or POS?
No production connection is promised by the public preview. It requires a separate readiness and integration assessment.